bf_next not NULL!

[Adrian Chadd]

Hi,

What else is logged in dmesg when it happens? I've never had to
restart hostapd or the interface, but it's quite possible you've found
some situations with hung stations and that needs to be addressed.

Thanks!


-a


On 29 July 2016 at 13:30, Andrew Stevenson <andrew at ugh.net.au> wrote:
>
> Well after a week of running 11 (BETA1 r303134) I think sadly its worse than 10. No more bf_next errors. Still lots of "ath0: stuck beacon; resetting (bmiss count 4)”. The main thing though is the the clients drop of the network and can’t reattach.
>
> Sometimes restarting hostapd is all that is needed, though occasionally I have to “restart" the interface (/etc/rc.d/netif restart wlan0).
>
> Happens usually once or twice a day. Is there anything I can do to help debug? I tried to attach to hostapd with gdb last time but gdb had an internal error and killed the process.
>
> Thanks,
>
> Andrew