Date: Fri, 19 Sep 2003 08:22:13 -0700 From: Sam Leffler <sam@errno.com> To: "Kenneth D. Merry" <ken@kdm.org> Cc: current@FreeBSD.org Subject: Re: ath(4) driver problems with WEP... Message-ID: <578671145.1063959731@melange.errno.com> In-Reply-To: <20030919052657.GA524@panzer.kdm.org> References: <20030917031202.GA35362@panzer.kdm.org> <421524069.1063802588@melange.errno.com> <20030919052657.GA524@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hmm. One other thing I'm seeing is that when I configure a 128 bit key > with ifconfig or wicontrol (wicontrol shows all 28 characters -- 0x plus > 26 hex characters), ifconfig still thinks it is a 104 bit key. This is > because ireq.i_len is 13. > You must not have the up to date ifconfig. This was the behaviour from before. I believe the mechanism that wicontrol uses to fetch keys does not handle >104-bit keys so you see the zero-padded key string. >> > In a separate issue, the ath(4) driver can't see the 802.11a side of >> > the wireless router at all when it is running in 108Mbps "turbo" mode. >> > If I drop it down to 54Mbps, it sees it. (Works fine in Windows.) >> > >> > Is the ath(4) driver supposed to support the 108Mbps turbo mode? >> >> I was able to associate with an Atheros AP with turbo mode enabled but >> didn't get any higher throughput. I'm investigating this. >> >> FWIW I enabled turbo mode with: >> >> ifconfig ath0 mediaopt turbo > > I had to also set the mode to 11a before it wanted to accept the turbo > option. Otherwise I got: > > ifconfig: SIOCSIFMEDIA (mediaopt): Device not configured > Ah, yes. Turbo mode is orthogonal to 11a/b/g. You can use it with 11g too so you need to specifiy 11a or 11g. I was already locked in 11a mode. (But note that 11g+turbo is not yet supported by the driver.) > Then I typed: > ># ifconfig ath0 mode 11a mediaopt turbo > atalk 0.0 range 0-0 phase 2 > > Does it think I'm doing appletalk or something? Hmm, didn't see this, will have to check. > > It seems to see the base station in turbo mode now, but I'm still getting > the "authentication failed (reason 13)" errors. Are you using WEP? As I explained WEP doesn't work right now. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?578671145.1063959731>