Date: Tue, 16 Sep 2003 21:12:02 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: current@FreeBSD.org Cc: sam@errno.com Subject: ath(4) driver problems with WEP... Message-ID: <20030917031202.GA35362@panzer.kdm.org>
next in thread | raw e-mail | index | archive | help
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.
Anyway, whenever I try to get the card talking to the router, which is
running WEP (128 bit keys) on both the a and b/g sides, I get:
ath0: authentication failed (reason 13) for [ base station MAC address ]
ath0: authentication failed (reason 13) for [ base station MAC address ]
ath0: authentication failed (reason 13) for [ base station MAC address ]
ath0: authentication failed (reason 13) for [ base station MAC address ]
ath0: authentication failed (reason 13) for [ base station MAC address ]
Here's what the ifconfig looks like:
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether [ card mac address ]
media: IEEE 802.11 Wireless Ethernet autoselect mode 11a (OFDM/6Mbps)
status: no carrier
ssid [my ssid] 1:[my ssid]
channel -1 authmode OPEN powersavemode OFF powersavesleep 100
wepmode MIXED weptxkey 1
wepkey 1:128-bit wepkey 2:128-bit wepkey 3:128-bit wepkey 4:128-bit
I've verified and re-verified, via cut-and-paste from the router setup
screen, that the WEP key is correct.
Anyway, I can't get the ath(4) driver to talk to the router when it is
running WEP. I have been able to get it to talk 802.11g to the router
without WEP enabled, though.
I tried setting the authmode to shared via ifconfig, but from looking at
ieee80211_ioctl.c:
#if 0
case IEEE80211_IOC_AUTHMODE:
sc->wi_authmode = ireq->i_val;
break;
#endif
i.e. I get EINVAL back.
Is WEP supposed to work in -current?
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?
Thanks,
Ken
--
Kenneth Merry
ken@kdm.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030917031202.GA35362>