wpa drops out

James Snow snow+freebsd-current at teardrop.org
Thu Aug 18 03:21:13 GMT 2005


On Tue, Aug 16, 2005 at 08:58:04AM -1000, Randy Bush wrote:
> >> fwiw, i have been seeing the following:
> >>   o system fine with wpa managing ath0, associated, no wep ...
> >>   o lose association
> >>   o does not regain it
> >>   o kill wpa and restart it
> >>   o it associates and things take off again
> 
> as of a cvsup of 2005.08.13 23:30, this is not occurring any more.

Unfortunately for me, as of 2005.08.16, it still is. This time, however,
I was lucky enough to have wpa_supplicant running in debug mode when it
happened.

wpa_supplicant scans for nearby networks:

Scan results: 3
Selecting BSS from priority group 0
0: 00:12:17:00:c6:3e ssid='mulligan' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
1: 00:0a:95:f4:50:c5 ssid='lbnetwork' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:04:5a:fd:0c:ed ssid='1broad4' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE

It picks 1broad4 and associates with it:

Association event - clear replay counter
Associated to a new BSS: BSSID=00:04:5a:fd:0c:ed
Associated with 00:04:5a:fd:0c:ed
Cancelling authentication timeout

And then out of the blue drops it, and doesn't find any more APs to
associate with:

Added BSSID 00:04:5a:fd:0c:ed into blacklist
Disconnect event - remove keys
...
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
No APs found - clear blacklist and try again
Removed BSSID 00:04:5a:fd:0c:ed from blacklist (clear)
Selecting BSS from priority group 0
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
No suitable AP found.
Setting scan request: 5 sec 0 usec

If they're of any use, here's 80211stats:

57404 rx from wrong bssid
186 rx discard 'cuz dup
78 rx discard 'cuz mcast echo
2 rx w/o wep and privacy on
5064 rx discard mgt frames
147198 rx beacon frames
60 rx element unknown
150 rx frame chan mismatch
116 nodes timed out inactivity

... and athstats:

1 beacon miss interrupts
726 mib overflow interrupts
1226 tx management frames
3732 tx frames discarded prior to association
2 tx linearized to cluster
373 long on-chip tx retries
1220 tx frames with no ack marked
1 tx frames with an alternate rate
14399 rx failed 'cuz of bad CRC
7 rx failed 'cuz decryption
735 rx failed 'cuz of PHY err
    735 CCK restart
509 periodic calibrations
2 rfgain value change
33428 rate control checks
rssi of last ack: 27
avg recv rssi: 26
19754 switched default/rx antenna
Antenna profile:
[1] tx    16446 rx   116015
[2] tx    13047 rx   122538

I'd never had this problem prior to wpa_supplicant, and I don't have it
if I setup my wireless entirely via ifconfig. Again, let me know what
other debugging information I can supply.


-Snow



More information about the freebsd-current mailing list