Date: Thu, 5 Nov 2009 14:01:39 -0500 From: "Alexandre \"Sunny\" Kovalenko" <gaijin.k@gmail.com> To: Paul B Mahol <onemda@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP Message-ID: <d7bab18e0911051101q35a3f79evcc58e70d5e097631@mail.gmail.com> In-Reply-To: <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> References: <1257426023.1436.18.camel@RabbitsDen> <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 5, 2009 at 9:24 AM, Paul B Mahol <onemda@gmail.com> wrote:
> On 11/5/09, Alexandre "Sunny" Kovalenko <gaijin.k@gmail.com> wrote:
> > It seems that 8.0 discussion is still going on on @current... if I
> > should have posted this on @stable, please, feel free to chastise me as
> > appropriate.
> >
> > After updating to r198831 my laptop no longer associates with either of
> > two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the
> > problem.
> >
> > Working system:
> > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0
> > r198443M: Sat Oct 24 14:03:30 EDT 2009
> > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386
> >
> > Non-working system:
> > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0
> > r198931: Wed Nov 4 20:56:16 EST 2009
> > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386
> >
> > APs are is:
> > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS
> > AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS
> > WME
> > AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA
> > ATH
> >
> > Relevant piece of wpa_supplicant.conf is:
> >
> > ctrl_interface=/var/run/wpa_supplicant
> > ctrl_interface_group=wheel
> > eapol_version=2
> >
> > network={
> > ssid="AP_SSID"
> > scan_ssid=1
> > priority=1
> > proto=WPA
> > key_mgmt=WPA-PSK
> > psk="Really secure something"
> > }
> >
> > APs are set not to broadcast SSID, but enabling broadcast does not
> > change much.
> >
> > Running wpa_supplicant with -d shows that it could not match AP_SSID.
> >
> > If there is anything else I can provide, please, let me know.
>
> What driver are you using?
> Looking into net80211 svn log for that time period I only see mesh hacks
> ...
>
I am using ath (I am away from my laptop ATM -- I could provide part number
later today).
I have seen mesh changes in there and that's when I gave up and posted -- I
am not
nearly enough qualified to figure out which ones could or could not impact
normal operation.
--
Alexandre "Sunny" Kovalenko.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7bab18e0911051101q35a3f79evcc58e70d5e097631>