New hardware, old problem: stuck beacon when here is WiFi traffic

[Adrian Chadd]

On 27 April 2013 01:33, Lev Serebryakov <lev at freebsd.org> wrote:
> Hello, Adrian.
> You wrote 27 апреля 2013 г., 1:34:24:
>
> AC> You're not doing something like leaving bgscan enabled, or not
> AC> defining a channel up front?
>  Here is my config:
>
> ifconfig_wlan0="inet 192.168.135.1 netmask 255.255.255.0 mode 11ng channel 3:ht/40 -bgscan ssid home.serebryakov.spb.ru country DE regdomain row txpower 30"

Is it a bridge? If so, put an IP address on the bridge, not wlan0.

By putting inet <x> there early on, it's bringing the interface up
very early. It's a side effect of hte network stack - if you assign an
IP address, the VAP comes up immediately.

thus i do the inet line after _all_ other things are done, and on a
separate line.

Anyway, leave it how it is for now. Just update to the latest -HEAD
ath code and redo the testing. It will now log the whole TX queue
contents, not just the completed frames. Hopefully it'll be more
obvious.

Thanks,


adrian