I can't stay associated to Y!Guest with wpa_supplicant (11n). Connecting without wpa_supplicant works out very very well.
So, maybe wpa_supplicant is bitching. It has 'locally_generated=1' which I believe says "wpa_supplicant made the decision!" Can you check your wpa_supplicant logs and see if the reason(s) it gives is locally generated? Would you also try connecting to Y!Guest without wpa_supplicant? Thanks! -adrian On 7 November 2013 10:08, Sean Bruno <[email protected]> wrote: > On Tue, 2013-11-05 at 17:15 -0800, Adrian Chadd wrote: >> Hi, >> >> So: >> >> http://people.freebsd.org/~adrian/iwn/20131105-iwn-update-works-full-5100-5.diff >> >> This is my attempt at merging in all of Cedric's work to date, _minus_ >> the PAN stuff. Ie, it's only the hardware addons. It turns out that >> it's not that big a change - a large part of the diff is just the >> config options. >> >> The biggest annoyance here is the calibration stuff. If the wrong >> calibration commands are sent up (ie, not all of them, in the right >> order!) then the firmware just panics after association. >> >> So, all I've done thus far is test it on my Intel 5100. Next is >> testing it on the 4965. After that, I'll try the 6xxx, 2xxx and 1xxx / >> 100 series stuff. >> >> I'd appreciate some testing of this. It's against -HEAD, so yes, >> you'll have to run -HEAD. >> >> Thanks, >> >> >> >> -adrian >> _______________________________________________ >> [email protected] mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "[email protected]" > > > Initial test looks good. I've enabled bluetooth to make sure that it > doesn't break iwn(4) and I see no issues running on wireless. > > I reverted my hack to disable 11N support and iwn(4) still has serious > issues negotiating with my $DAYJOB wireless APs. So, I'm still running > with 11N disabled for now. > > sean _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[email protected]"
