Date: Sat, 27 Apr 2013 11:56:30 -0700 From: Adrian Chadd <adrian@freebsd.org> To: lev@freebsd.org Cc: freebsd-wireless@freebsd.org Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic Message-ID: <CAJ-Vmonpc6rMKfT3qHme4Yzwkcj0zij8dYzXktpbz3bbSmT0=Q@mail.gmail.com> In-Reply-To: <777510536.20130427123352@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <CAJ-Vmom4UDoz7EgdnVeQ%2BALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com> <1813905823.20130423184528@serebryakov.spb.ru> <CAJ-VmomhRaKODxis09MjAhUbAUOw%2B6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com> <184105677.20130424002002@serebryakov.spb.ru> <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com> <1936997795.20130424003555@serebryakov.spb.ru> <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com> <886711115.20130424004702@serebryakov.spb.ru> <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com> <6010292503.20130426001447@serebryakov.spb.ru> <CAJ-VmomUsPgHTVGaKHZ_YE%2Bu1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com> <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com> <99510815.20130426122508@serebryakov.spb.ru> <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com> <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com> <CAJ-Vmonxz3spCYeM5b3ijBgnM6wfjTa%2Bv5j8pbnX%2B-_Sg4hSGw@mail.gmail.com> <777510536.20130427123352@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 April 2013 01:33, Lev Serebryakov <lev@freebsd.org> wrote: > Hello, Adrian. > You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 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=3D"inet 192.168.135.1 netmask 255.255.255.0 mode 11ng chan= nel 3:ht/40 -bgscan ssid home.serebryakov.spb.ru country DE regdomain row t= xpower 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmonpc6rMKfT3qHme4Yzwkcj0zij8dYzXktpbz3bbSmT0=Q>