On Wed, 2008-06-04 at 15:49 -0400, David Ellingsworth wrote: > For a while now, I've been experiencing connection stability issues which from > what I can tell seem to stem from the use of dhclient. > > After upgrading to the latest wireless-testing kernel, I noticed the output > from > wpa_supplicant and iwconfig regarding association status differed as well as > an > inability to use dhclient to receive an ip address. In an attempt to resolve > the > issue, I first eliminated the use of dhclient by issuing a static ip address > for > the interface after it was associated with the AP. Doing so resulted in a very > stable and reliable connection. This led me to believe the issues were a > result > of using dhclient. To verify, I tried dhcpcd in place of dhclient, which once > again resulted in a stable and reliable connection. Thus confirming my > suspicion.
The problem with dhclient is that it brings the interface down temporarily, thus breaking the WPA connection. You can see hostap archives for a recent discussion about it: http://lists.shmoo.com/pipermail/hostap/ It's a complicated problem, involving a lot of software, including distribution specific scripts. It's entirely possible that simply different timing can break the behavior. Jouni Malinen mentioned that the driver is supposed to tell wpa_supplicant to renegotiate the connection after the interface goes down and up. It's possible that the kernel is not doing it right, but the code is not in b43legacy, it's in mac80211. My solution is either to use static addresses with WPA or use a dhclient script that brings the interface up and tell wpa_supplicant to renegotiate the connection. In any case, I'm quite sure that discussing the problem here is not going to be useful because it's not specific to the particular driver. -- Regards, Pavel Roskin _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
