New hardware, old problem: stuck beacon when here is WiFi traffic
Adrian Chadd
adrian at freebsd.org
Fri Apr 26 21:34:25 UTC 2013
You're not doing something like leaving bgscan enabled, or not
defining a channel up front?
There's a lot of resets hre.
adrian
On 26 April 2013 14:28, Lev Serebryakov <lev at freebsd.org> wrote:
> Hello, Adrian.
> You wrote 26 апреля 2013 г., 12:51:17:
>
>>> Wait. sysctl dev.ath.0.forcebstuck=1 didn't fix it?
> Ok, several such commands helps without down/up of interface.
> Log attached: a lot of traffic, several BAR retransmits, interface
> hangs, several "forcebstuck=1", client could associate again and
> interface passes traffic.
>
> Maybe, there were too many "forcebstuck=1", but one ro two doesn't
> fix situation for sure, client was not able to assotate after first
> two of them.
>
> --
> // Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>
More information about the freebsd-wireless
mailing list