Date: Sun, 22 Jul 2012 12:52:08 -0400 From: Kim Culhan <w8hdkim@gmail.com> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current Message-ID: <CAKZxVQVY=y2-XqNRfAYZ69y0WhqCuaBbemf0NqnYcnrZVj%2Br7w@mail.gmail.com> In-Reply-To: <CAJ-Vmom9rtw4fwr2FYcVTey6TfrbPDsHLsbRmHyDAOfb6niVrQ@mail.gmail.com> References: <CAKZxVQWJ76dCVY0OHULFAXXm2hHA3GfdCQLFJ1F5J5DMNMjKoQ@mail.gmail.com> <CAJ-Vmo=eXrcEQ8eBRA1qbpZ=_XZiKK793LCSfE-mYQFnCBGfMQ@mail.gmail.com> <CAKZxVQV7v_i=AWeg4aLA7AA01q7MwehtDy98Kn__Ob5BBSNa1Q@mail.gmail.com> <CAJ-Vmom9rtw4fwr2FYcVTey6TfrbPDsHLsbRmHyDAOfb6niVrQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 22, 2012 at 11:22 AM, Adrian Chadd <adrian.chadd@gmail.com> wrote: > Hm, ok. > > So I'd start diagnosing this by setting up another FreeBSD device in > monitor mode on that channel and capturing some beacons. > Then take a look in wireshark and make sure you're seeing beacons consistently. > > I bet the beacon timer and beacon slot configuration is all subtly > messed up, leading to this mess. Ah ok.. I'll work on setting up another FreeBSD machine. thanks -kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKZxVQVY=y2-XqNRfAYZ69y0WhqCuaBbemf0NqnYcnrZVj%2Br7w>