New hardware, old problem: stuck beacon when here is WiFi traffic
Lev Serebryakov
lev at FreeBSD.org
Sun Apr 28 08:11:35 UTC 2013
Hello, Adrian.
You wrote 27 апреля 2013 г., 22:56:30:
>> 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"
AC> Is it a bridge? If so, put an IP address on the bridge, not wlan0.
I don't have bridge, it is true router, to have strong separation
between WiFi and wired network.
AC> thus i do the inet line after _all_ other things are done, and on a
AC> separate line.
Two lines for one interface? Or just move "inet" part to end of this
line?
AC> Anyway, leave it how it is for now. Just update to the latest -HEAD
AC> ath code and redo the testing. It will now log the whole TX queue
AC> contents, not just the completed frames. Hopefully it'll be more
AC> obvious.
Ok, today later.
--
// Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>
More information about the freebsd-wireless
mailing list