Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))

On Sun, May 30, 2010 at 07:48:38PM +0200, Lars Engels wrote:
> On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote:
> > 
> > On 29 May 2010, at 05:39, b. f. wrote:
> > 
> > > On 5/28/10, Doug Barton <dougb_at_freebsd.org> wrote:
> > >> On 5/28/2010 4:50 PM, b. f. wrote:
> > >>> 
> > >>> I can't see any problems when using WPA2 with AES on r208606 i386 with
> > >>> uath(4).  I'm updating this machine to r208630 tonight, and if I
> > >>> encounter problems with the later revision, I'll let you know.
> > >> 
> > >> Ok, thanks.
> > >> 
> > >>> Are
> > >>> you saying that you experienced problems when trying to use a r207134
> > >>> base with a r208626 kernel?  If that's the case, I would recommend
> > >>> updating the base to the same revision as the kernel, and then
> > >>> retesting.
> > >> 
> > >> Yes, that's what I'm doing I actually tried running the newly built
> > >> wpa_supplicant but that didn't work. I'm kind of hesitant to do the full
> > >> upgrade since I'm having kernel problems with the nvidia driver, but if
> > >> I'm sure wpa_supplicant will work then I suppose I can bite the bullet.
> > >> 
> > > 
> > > It appears that something is wrong.  My wireless stick no longer
> > > associates with the network with r208630.  I'll do some tinkering.
> > 
> > That's odd. The only way for that to happen would be caused bug in the
> > taskqueue stuff that zml committed, I think, but that's a long shot.
> 
> Correction: Wireless actually works if you set the channel manually and
> start wpa_supplicant afterwards. So wpa_supplicant no longer seems to be
> able to change the channel itself.


The issue is still present in r209168.