ath "stops working" in hostap mode
adrian.chadd at gmail.com
Sun Jan 1 01:19:14 UTC 2012
On 31 December 2011 17:15, Lay, Nathan <nsl03 at my.fsu.edu> wrote:
> Thanks for the prompt response. Bumping the interface up and down does not fix it. Destroying and recreating the interface does not fix it either. The interface is completely unresponsive when this problem arises. As far as I can tell, it does not transmit (it vanishes from view from all other devices).
> I do not have ATH_ENABLE_11N compiled in. Would this improve stability? The interface shows that it is using 11g mode with background scanning turned off. Here is exactly how it is configured and used:
Please don't compile in ATH_ENABLE_11N. But do add:
> create_args_wlan0="wlanmode hostap -bgscan"
> autobridge_bridge0="wlan0 lan0"
> It also sits behind pf (I saw pf mentioned in a similar message about ath).
> I've installed athstats. Attached is the output.
Ok. Can you please do this:
* recompile with the above options;
* try running 'athstats -i ath0 -o bexmit,bmiss 1'
* (athstats -l will list what you can track, statistics-wise)
* Make sure it's sending those beacons, or at least queuing to send
Once that's done, wait until it fails and then try it again. It should
still be trying to send the beacons, but we'll see what else shows up.
Finally, do you have any FreeBSD stations? That we could use to see
what's going on in the air?
More information about the freebsd-wireless