manual roaming in client mode

Randy Wilkinson rwilkinson at digitalpath.net
Fri Dec 5 15:17:02 EST 2003


I am using hostap version 0.4 with the host_roaming 2 option in managed
mode. I also wrote a script that scans and reassociates when
connectivity is lost using:
	iwconfig wlan1 essid test
	iwconfig wlan1 ap [mac of ap] //to reassociate

As long as the channel is the same this seems to work most of the time.
But this manual roaming mode seems somewhat unstable. One of my devices
seems to authenticate and associate properly but then immediately
disconnects with a link status of 2. Has anyone else ran into this
problem?

dmesg of ap shows association:

wlan0: 00:60:b3:79:44:d0 auth_cb - STA authenticated //wlan1 of client
wlan0: 00:60:b3:79:44:d0 assoc_cb - STA associated

dmesg of client shows:

prism2: wlan1: operating mode changed 3 -> 2
wlan1: LinkStatus=2 (Disconnected)
wlan1: LinkStatus: BSSID=44:44:44:44:44:44
wlan1: LinkStatus=2 (Disconnected)
wlan1: LinkStatus: BSSID=44:44:44:44:44:44
wlan1: Trying to join BSSID 00:60:b3:8a:6b:31 //wlan0 of ap
wlan1: LinkStatus=1 (Connected)
wlan1: LinkStatus: BSSID=00:60:b3:8a:6b:31
wlan1: LinkStatus=2 (Disconnected)
wlan1: LinkStatus: BSSID=00:60:b3:8a:6b:31
wlan1: TXEXC - status=0x0004 ([Discon]) tx_control=002c
   retry_count=0 tx_rate=110 fc=0x0308 (Data::0 ToDS FromDS)
   A1=00:60:b3:8a:6b:31 A2=00:60:b3:79:44:d0 A3=00:00:24:c1:1e:39
A4=00:26:54:13:bb:9b
	.
	.
	.
	.






More information about the HostAP mailing list