Re: ath(4) driver problems with WEP...

2003-10-12 Thread Sam Leffler
On Tuesday 16 September 2003 08:12 pm, Kenneth D. Merry wrote: > I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114 > wireless router. > > I've been trying to get the card and the router talking under FreeBSD. > (Both 802.11a and 802.11g work fine under Windows on the same ma

Re: ath(4) driver problems with WEP...

2003-09-19 Thread Kenneth D. Merry
On Fri, Sep 19, 2003 at 08:22:13 -0700, Sam Leffler wrote: > > 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

Re: ath(4) driver problems with WEP...

2003-09-19 Thread Sam Leffler
> 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.

Re: ath(4) driver problems with WEP...

2003-09-18 Thread Kenneth D. Merry
On Wed, Sep 17, 2003 at 12:43:08 -0700, Sam Leffler wrote: > > I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114 > > wireless router. > > > > I've been trying to get the card and the router talking under FreeBSD. > > (Both 802.11a and 802.11g work fine under Windows on the

Re: ath(4) driver problems with WEP...

2003-09-17 Thread Sam Leffler
> I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114 > wireless router. > > I've been trying to get the card and the router talking under FreeBSD. > (Both 802.11a and 802.11g work fine under Windows on the same machine.) > > I'm using -current from September 15th. > > Anyw