ath + wep issue

Sam Leffler sam at errno.com
Wed Aug 3 02:53:47 GMT 2005


Robert C. Noland III wrote:
> I am having an issue with static wep on my ath card, -current sources as
> of this morning EST.  It is a Linksys WPC55ag card.  I also have an old
> Netgear wi card that works shown at the bottom.
> 
> ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
> ...
> ath0: <Atheros 5212> mem 0xf4010000-0xf401ffff irq 11 at device 0.0 on
> cardbus0
> ath0: Ethernet address: 00:12:17:6e:fc:18
> ath0: mac 5.9 phy 4.3 radio 3.6
> 
> laptop# ifconfig ath0 ssid "test001" wepmode on weptxkey 1 wepkey "xxxx"
> laptop# ifconfig ath0 up
> 
> Tue Aug  2 17:27:19 RTM_IFINFO: if# 3, link: down,
> flags:<UP,BROADCAST,SIMPLEX,MULTICAST>
> Tue Aug  2 17:27:25 RTM_IEEE80211: scan complete
> Tue Aug  2 17:27:25 RTM_IEEE80211: associate with 00:0d:93:e9:cf:d4
> Tue Aug  2 17:27:25 RTM_IFINFO: if# 3, link: up,
> flags:<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> Tue Aug  2 17:27:25 RTM_IEEE80211: disassociate
> Tue Aug  2 17:27:25 RTM_IFINFO: if# 3, link: down,
> flags:<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>

You associated with the ap then fell off either because the ap dropped 
you or your station initiated it.  The easiest way to see which is to 
enabling debugging; I prefer to use 80211debug from tools/tools/ath; e.g.

80211debug state+assoc

or probably

ifconfig ath0 debug

will give you enough info.  The output of 80211stats should also tell 
you what happened.

> 
> The disassociate message concerns me, but it should work...
> 
> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet6 fe80::212:17ff:fe6e:fc18%ath0 prefixlen 64 scopeid 0x3 
>         ether 00:12:17:6e:fc:18
>         media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps)
>         status: no carrier
>         ssid test001 channel 1
>         authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 46
>         protmode CTS roaming DEVICE bintval 100
> 
> At this point, the card is no longer scanning and the lights on the card
> continue blinking as if it is associated (slowly in sync, as opposed to
> alternately blinking like mad when it is scanning) yet status shows no
> carrier.  dhclient will not work when the interface is in this state.
> It seems to just broadcast and eventually die.
> 
> wi0: <NETGEAR MA401 Wireless PC Card> at port 0xe000-0xe03f irq 11
> function 0 config 1 on pccard0
> wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163-SST-flash
> wi0: Intersil Firmware: Primary (0.3.0), Station (1.3.4)
> wi0: Ethernet address: 00:30:ab:07:e4:7b
> 
> laptop# ifconfig wi0 ssid "test001" wepmode on weptxkey 1 wepkey "xxxx"
> laptop# ifconfig wi0 up
> 
> Tue Aug  2 17:35:57 RTM_IFANNOUNCE: if# 3, what: arrival
> Tue Aug  2 17:39:06 RTM_IFINFO: if# 3, link: unknown,
> flags:<UP,BROADCAST,SIMPLEX,MULTICAST>
> Tue Aug  2 17:39:06 RTM_IEEE80211: disassociate
> Tue Aug  2 17:39:06 RTM_IFINFO: if# 3, link: down,
> flags:<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> 
> again with the disassociate message.  This seems to force wpa_supplicant
> to start scanning again, so I can't currently use wpa_supplicant on this
> network.  Actually, wpa_supplicant doesn't ever seem to be able to
> associate on the wi card, but static configuration works.
> wpa_supplicant on the ath card seems to associate, then catches the
> disassociate and starts scanning again.  lather, rinse, repeat...
> 
> wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet6 fe80::230:abff:fe07:e47b%wi0 prefixlen 64 scopeid 0x3 
>         ether 00:30:ab:07:e4:7b
>         media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
>         status: associated
>         ssid test001 channel 1 bssid 00:0d:93:e9:cf:d4
>         stationname "FreeBSD WaveLAN/IEEE node"
>         authmode OPEN privacy MIXED deftxkey 1 wepkey 1:104-bit txpowmax
> 100
>         bintval 100
> 
> dhclient does work here, and then I can start the vpn and roam about the
> office...

I've been testing ath w/ static key wep today and seen no problems. 
Please get some more info.

	Sam


More information about the freebsd-current mailing list