hostapd, hostap, prism2 and WPA

Michael Smith msmith at cbnco.com
Wed Jun 29 10:29:58 EDT 2005


On Mon, 27 Jun 2005, Michael Smith wrote:

> Now when I try to replicate it using a PCMCIA prism2 card, I run into 
> problems. If the master reboots, the station doesn't seem to notice. 
> Forcing a reassociation (wpa_cli reassoc) usually fixes it. I've seen some 
> cases where it didn't, but I'm having trouble duplicating that now.

With no WPA, the station logs this when the master disappears:

Jun 29 13:30:27 wi-client kernel: wifi0: LinkStatus=4 (Access point out of range)
Jun 29 13:30:27 wi-client kernel: wifi0: LinkStatus: BSSID=00:02:6f:xx:xx:98
Jun 29 13:30:47 wi-client kernel: wifi0: LinkStatus=5 (Access point in range)
Jun 29 13:30:47 wi-client kernel: wifi0: LinkStatus: BSSID=00:02:6f:xx:xx:98
Jun 29 13:30:47 wi-client kernel: wifi0: LinkStatus=2 (Disconnected)
Jun 29 13:30:47 wi-client kernel: wifi0: LinkStatus: BSSID=00:02:6f:xx:xx:98
Jun 29 13:30:49 wi-client kernel: wifi0: LinkStatus=1 (Connected)
Jun 29 13:30:49 wi-client kernel: wifi0: LinkStatus: BSSID=00:02:6f:xx:xx:98

With WPA turned on, the station doesn't seem to get those notifications 
from the firmware (?).

I've tried STA 1.7.4, 1.8.0 and 1.8.4 and none of them report that the 
access point is out of range when using WPA. Additionally, the link status 
shows up as 0 when the client is connected:

          Link Quality=0/70  Signal level=-55 dBm  Noise level=-10 dBm

The signal level and noise level don't seem to be updated on the station 
side. They are properly updated on the master in
/proc/net/hostap/wlan0/00:xxxxx.

Mike



More information about the HostAP mailing list