[CVS] Association problem after AP restart (WITHOUT HOSTAPD)

[Michael Guntsche]

Hi I recently updated my CVS version and now I am facing problems when I restart my AP.

If I restart the computer that is acting as an AP (taking down the interface and removing
the modules is enough) I see the following messages in the clients syslog.

	Dec 27 18:02:11 roadrunner kernel: wifi0: LinkStatus=6 (Association failed)
	Dec 27 18:02:11 roadrunner kernel: wifi0: LinkStatus: BSSID=44:44:44:44:44:44


Here an example of a session:

-- client syslog --
--->Notebook boots and gets connected
	Dec 27 18:39:38 roadrunner kernel: wifi0: LinkStatus=1 (Connected)
	Dec 27 18:39:38 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
<snip>

--->Tearing down the access point
	Dec 27 18:40:13 roadrunner kernel: wifi0: LinkStatus=4 (Access point out of range)
	Dec 27 18:40:13 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
This looks normal to me

--->Starting up the AP once again
		
	Dec 27 1Dec 27 18:40:36 roadrunner kernel: wifi0: LinkStatus=5 (Access point in range)
	Dec 27 18:40:36 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
	Dec 27 18:40:36 roadrunner kernel: wifi0: LinkStatus=2 (Disconnected)
	Dec 27 18:40:36 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
	Dec 27 18:40:39 roadrunner kernel: wifi0: LinkStatus=6 (Association failed)
	Dec 27 18:40:39 roadrunner kernel: wifi0: LinkStatus: BSSID=44:44:44:44:44:44
	<.....>
Somehow he is getting the wrong BSSID

-----------------------
At the same time I get the following message on the AP

	wifi0: No more space in STA (00:09:5b:3d:1f:9e)'s PS mode buffer

The MAC-address belongs to the client
------------------------


--->Starting hostapd (JUST FOR TESTING, I NORMALLY DON'T USE IT ) 
	Dec 27 18:46:22 roadrunner kernel: wifi0: LinkStatus=1 (Connected)
	Dec 27 18:46:22 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
After starting the daemon he uses the right BSSID and connects immediately.

-- client syslog --

For me it looks like that WITHOUT hostapd running the hostap in managed mode is sending out
wrong/missing information OR  the client is not able to get it right (PS mode buffer???).

Going back in CVS I noticed that the last time this worked withouth hostapd was a checkout from
'2003-10-21 5:00'.

Using this version on the AP without hostapd:

	Dec 27 18:17:05 roadrunner kernel: wifi0: LinkStatus=4 (Access point out of range)
	Dec 27 18:17:05 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
	Dec 27 18:17:13 roadrunner kernel: wifi0: LinkStatus=5 (Access point in range)
	Dec 27 18:17:13 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
	Dec 27 18:17:16 roadrunner kernel: wifi0: LinkStatus=2 (Disconnected)
	Dec 27 18:17:16 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f
	Dec 27 18:17:17 roadrunner kernel: wifi0: LinkStatus=1 (Connected)
	Dec 27 18:17:17 roadrunner kernel: wifi0: LinkStatus: BSSID=00:09:5b:2f:13:1f


I am not sure what might be causing this behaviour,

Jouni, do you have an idea?

Kind regards,
Michael