Re: Network Manager Times Out During DHCP Handshake





On 8/15/06, Adam Pavelec <adam pavelec net> wrote:
<Disclaimer>Many apologies in advance if this has already been addressed
-- it appears that the archive search indexes aren't yet
rebuilt.</Disclaimer>

My environment is as follows:

Wireless Card: Broadcom Corporation BCM4309 802.11a/b/g (rev 02)
nndiswrapper: driver bcmwl5 (Broadcom,06/13/2003, 3.20.23.0) loaded

Network Manager seems to work as designed until it attempts to obtain an
IP address.  Here are some log snippets:

-----BEGIN LOG SNIPPET-----
(all OK's reported up to this point...)
NetworkManager: <information>   Activation (wlan0) Stage 2 of 5 (Device
Configure) complete.
NetworkManager: <information>   Activation (wlan0/wireless): association
took too long (>60s), failing activation.
NetworkManager: <information>   Activation (wlan0) failure scheduled...
-----END LOG SNIPPET-----

Issuing an "iwconfig wlan0 essid %AP-Name%" and "dhclient" works perfectly.

Is there anything I can do to prevent the association failure from
occurring, or am I
simply SOL because I'm in the Broadcom/ndiswrapper boat?

-Adam
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list gnome org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


I see the same behavior on a  Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) with ndiswrapper on ubuntu dapper (see https://launchpad.net/distros/ubuntu/+source/wpasupplicant/+bug/42504 )...  It seems like the association happens correctly, but wpasupplicant get notified properly.  I'm not sure how to debug this at all; maybe a network manager dev has some ideas on debugging it?

-Joe




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]