On Wed, Jul 22, 2009 at 11:43 PM, Holger Schurig<[email protected]> wrote: >> RTM_NEWLINK: operstate=1 ifi_flags=0x1043 ([UP][RUNNING]) >> Wireless event: cmd=0x8b15 len=20 >> Wireless event: new AP: 00:00:00:00:00:00 > > The interesting bit here is not the RTM_NEWLINK, but the > SIOCGIWAP call. The next line says "New AP 00:00:00:00:00:00". > That means, that there is NO new access-point, as > 00:00:00:00:00:00 is an invalid MAC address. > > Basically mac80211 told user-space that it lost connection to an > access-point. > > The "my connection drops for a few seconds" now happens because > wpa_supplicant scans and selects a new access-point. That takes > some time, as scanning and roaming is currently very untuned in > mac80211/wpa_supplicant.
That's quite possible. It seems to happen fairly regularly--once ever 600 seconds, or so (hostapd also? has a periodic 600 sec. event). That said, shouldn't wpa_supplicant say something about scanning for a new AP in its own log? I only have one AP in the config file, and I specified a BSSID, so there's nothing to search for, but that wouldn't keep the code from scanning, anyway. _______________________________________________ ath5k-users mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-users
