Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jun 2005 20:59:32 +0200
From:      Wilko Bulte <wb@freebie.xs4all.nl>
To:        Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>
Cc:        freebsd-current@freebsd.org, James Snow <snow+freebsd-current@teardrop.org>
Subject:   Re: Getting WPA to work on ath(4)
Message-ID:  <20050624185932.GB70929@freebie.xs4all.nl>
In-Reply-To: <0506241058502.41439@www.mmlab.cse.yzu.edu.tw>
References:  <20050621205048.GA61951@freebie.xs4all.nl> <050622074135F.25017@www.mmlab.cse.yzu.edu.tw> <20050623202416.GA64730@freebie.xs4all.nl> <20050623204325.GA72574@teardrop.org> <20050623211620.GA65274@freebie.xs4all.nl> <20050623213139.GA73882@teardrop.org> <20050623214717.GA65438@freebie.xs4all.nl> <0506241058502.41439@www.mmlab.cse.yzu.edu.tw>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 24, 2005 at 12:10:51PM +0800, Tai-hwa Liang wrote..
> On Thu, 23 Jun 2005, Wilko Bulte wrote:
> >On Thu, Jun 23, 2005 at 05:31:39PM -0400, James Snow wrote..
> >>On Thu, Jun 23, 2005 at 11:16:20PM +0200, Wilko Bulte wrote:
> >>>
> >>>How do you disable WME?  [ I feel stranded in a maze of acronyms, all
> >>>different :-) ]
> >>
> >>ifconfig <if> -wme
> >>
> >>I think it's in the ifconfig man page, but I reserve the right to be
> >>wrong. If it's not, it clearly should be.
> >
> >It is indeed in the ifconfig man page.
> >
> >>My understanding is that we do something wrong with WME right now, and
> >>this in turn makes APs unhappy with us.
> >
> >Smells like WME should default to 'off'?
> 
>   It is. See src/sys/net80211/ieee80211.c:1.16.

Hm, that would make James' suggestion to ifconfig -wme a no-op.

>   AFAIK, the problem is that there are some interoperability problems
> when you have both WME + WPA enabled. Disable one of them should be a
> possible workaround.  I believe that Sam has some fixes in his queue;
> however, those fixes were not yet ready for the forthcoming 6-RELEASE.

OK.

> >>>I noticed today that wpa_supplicant renegotiated multiple times even with
> >>>SSID broadcasting enabled.  So it was most definitely not the full
> >>>fix to enable broadcasting.
> 
>   That's what I observed around here: sometimes it takes wpa_supplicant
> looping multiple times before negotiated to the AP(w/ or w/o hidden SSID).

And sometimes it appears not to get things sorted at all (at least not
before I get impatient ;), kill wpa_supplicant and remove/re-insert my
ath(4) card.

>   Apart from multiple regotiation sometimes, scan_ssid=1 works for me.
> Have you tried to set the IP manually(no dhclient) after ath0 was
> associated with the AP?

Yes, I tried a couple of times.  It did not make a whole lot of difference,
in the sense I did not think it worked better with a manual set IP address.

Interesting exercise, this :)

-- 
Wilko Bulte				wilko@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050624185932.GB70929>