Date: Sat, 30 May 2009 13:40:41 -0500 From: "Sam Fourman Jr." <sfourman@gmail.com> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: freebsd-current@freebsd.org Subject: Re: 802.11 monitor mode changes coming Message-ID: <11167f520905301140q41799907ob14ce5edc5571b7b@mail.gmail.com> In-Reply-To: <20090521204752.43aa3adc@fabiankeil.de> References: <4A11A08B.6090309@errno.com> <20090521170637.73619418@fabiankeil.de> <20090521204752.43aa3adc@fabiankeil.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 21, 2009 at 1:47 PM, Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > >> With r192468 I can no longer get iwi to associate to the AP. >> "ifconfig wlan0 list scan" shows the AP, but S:N is listed >> as -95:-95 (IIRC). > > Fixed in r192541. > No I don't think it is Fixed, I have a kernel built today 5-30-2009 and I have the same trouble with not being able to associate to AP's that I could before. Except it sounds WEIRD but, certian AP's I can associate to, Eg a OpenBSD 4.5 AP and a ubiquiti NS2 work fine every time, but certain linksys wrt54G's I cant associate with, and I have a Enginius device that I cant associate with. I also noticed that I cant see the Beacons from these AP's with tcpdump -i wlan0 -y IEEE802_11_RADIO I have tried this with ath, uath, urtw a Kernel from May 12th fixes all these issues Just a Observation I am willing to help but I do not know what exactly to do. Sam Fourman Jr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11167f520905301140q41799907ob14ce5edc5571b7b>