Re: "receive_packet failed on wlan0: Network is down", "No DHCPOFFERS received."
On Sat, Nov 11, 2006 at 18:17:01 +0100, juanjavier wrote:
> >Did you set the ESSID with iwconfig?
>
> Hi, Florian! Yes, I did. I typed iwconfig wlan0 essid "Juanja". Doesn't get
> an ip.
>
> >The output of "iwlist wlan0 scan"
> >in your first message showed that your access point hides its ESSID.
>
> Yes, it does. `Invalid' is the right word.
>
> >I
> >think this means that it will only accept connections from clients which
> >know the secret ESSID before they connect.
>
> Yes, it seems so. I do `iwconfig wlan0 essid "Juanja" and then
> `dhclient wlan0'. The subject message appears :-(
>
> >Also, check the output of "iwconfig wlan0": Is the ESSID set correctly,
> >does it display the MAC address of the right access point?
>
> debian:~# iwconfig wlan0
> wlan0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4310"
> Mode:Managed Frequency=2.484 Ghz Access Point: Invalid
> Bit Rate=11 Mb/s Tx-Power=19 dBm
> RTS thr:off Fragment thr:off
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalidmisc:0 Missed beacon:0
That looks to me like there is a problem with the driver. No matter what
the access point does or does not do, you should be able to change the
ESSID from "off/any" to "Juanja". Check "dmesg | grep bcm43xx" for clues
about the problem. I do not have Broadcom wireless cards myself, but
from following this list and debian-user I get the impression that they
can be touchy sometimes. You might want to try different versions of the
firmware or it might be easier to get the card working with ndiswrapper
and the windows driver.
> >If the above is all OK then it might be a problem with dhclient. There
> >are two DHCP client packages in Debian, "dhcp-client" and
> >"dhcp3-client". Make sure to try it with both of them.
>
> I apt-get installed dhcp3-client. How do I invoke it?
dhcp3-client replaces dhcp-client when you install it. The command is
exactly the same, "dhclient wlan0". However, I don't think it can work
unless we solve the "Access Point: Invalid" problem first.
--
Regards,
Florian
Reply to: