New ath code works well as AP

[Slawa Olhovchenkov]

On Mon, Aug 20, 2012 at 08:38:56AM -0700, Adrian Chadd wrote:

> On 20 August 2012 05:55, Slawa Olhovchenkov <slw at zxy.spb.ru> wrote:
> 
> > wlan0: link state changed to DOWN/UP -- because AP don't implement
> > 802.11R and don't transmit WLAN_EID_TIMEOUT_INTERVAL.
> 
> So you mean that's to be expected? There are situations where an AP
> will time a station out. May leave a background ping going and see if
> it stays associated?

This is time for rekeing (WPA2 enterprise).
AP configured for rekeing clients at 3600 seconds.
But AP don't send information about rekeing interval in EAPOL packets.

[277795] wlan0: link state changed to DOWN
[277797] wlan0: link state changed to UP
[281406] wlan0: link state changed to DOWN
[281408] wlan0: link state changed to UP
[292231] wlan0: link state changed to DOWN
[292233] wlan0: link state changed to UP
[302376] ath0: device timeout

281406-277797 = 3609
292231-281408 = 10823 = 3600*3+23


> >> > [155821] ath0: bb hang detected (0x4), resetting
> >> > [194052] ath0: device timeout
> >> > [202568] ath0: device timeout
> >> > [214975] ath0: bb hang detected (0x4), resetting
> >
> > And time to time I need to
> >
> > kldunload if_ath_pci.ko
> > kldload if_ath_pci.ko
> >
> > for re-enable card.
> 
> This is a bit more worrying. An ifconfig wlanX destroy ; ifconfig
> wlanX create isn't sufficient?

I am not clearly remember, may be isn't sufficient.
This is from old time, before introduction wlan0 (when all work on
ath0 and D-Link DWL-G650).

A am try at next time.