Re: WEP does not work?

Pawel Worach wrote:
> Sam Leffler wrote:
> 
>> I'll try to look tomorrow.  I have a patch for fixing wep with ndis 
>> that I need to review and this is probably the same thing.
> 
> 
> I have the same problem on a ThinkPad T41.

What problem?  Are you saying that wep does not work with the ath 
driver?  I communicated with a couple of people that have setup static 
key'd wep fine so I'm not sure what to think.  I've still had no time to 
try it myself (it was tested a while back but not immediatel before the 
commit).  One thing I found from talking to folks is I did not make it 
clear you must have the wlan_wep module configured in the kernel or 
available for loading by the wlan layer when you configure a wep key. 
But if that happens then ifconfig will complain; things won't silently fail.

> 
> Device is:
> ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
> ath0: <Atheros 5212> mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on pci2
> ath0: Ethernet address: 00:05:4e:4b:76:13
> ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3
> 
> Sysctls:
> dev.ath.0.countrycode: 0
> dev.ath.0.regdomain: 97
> 
> I tried setting hw.ath.countrycode to 752 (sweden) but the driver
> complained on boot that it was invalid. It was zero with the old
> kernel too.

Regdomain 97 is incompatible with the country code you requested.  What 
were you trying to accomplish by setting the country code?

> 
> The card works fine in ad-hoc mode without wep, if I enable wep it breaks.

"breaks" how?  Please provide the exact steps you take to demonstrate 
the problem.

> The funny thing is that on the other end I can see ARP requests but no
> replies are sent when wep is on (other end is a ~3 weeks old current with
> a cisco aironet 350 card). "status" claims "associated", everything looks
> the way it should be.
> 
> # ifconfig ath0 list chan
> Channel   1 : 2412  Mhz 11g          Channel  48 : 5240* Mhz 11a
> Channel   2 : 2417  Mhz 11g          Channel  52 : 5260* Mhz 11a
> Channel   3 : 2422  Mhz 11g          Channel  56 : 5280* Mhz 11a
> Channel   4 : 2427  Mhz 11g          Channel  60 : 5300* Mhz 11a
> Channel   5 : 2432  Mhz 11g          Channel  64 : 5320* Mhz 11a
> Channel   6 : 2437  Mhz 11g          Channel 100 : 5500* Mhz 11a
> Channel   7 : 2442  Mhz 11g          Channel 104 : 5520* Mhz 11a
> Channel   8 : 2447  Mhz 11g          Channel 108 : 5540* Mhz 11a
> Channel   9 : 2452  Mhz 11g          Channel 112 : 5560* Mhz 11a
> Channel  10 : 2457  Mhz 11g          Channel 116 : 5580* Mhz 11a
> Channel  11 : 2462  Mhz 11g          Channel 120 : 5600* Mhz 11a
> Channel  12 : 2467* Mhz 11g          Channel 124 : 5620* Mhz 11a
> Channel  13 : 2472* Mhz 11g          Channel 128 : 5640* Mhz 11a
> Channel  14 : 2484* Mhz 11b          Channel 132 : 5660* Mhz 11a
> Channel  34 : 5170* Mhz 11a          Channel 136 : 5680* Mhz 11a
> Channel  36 : 5180* Mhz 11a          Channel 140 : 5700* Mhz 11a
> Channel  38 : 5190* Mhz 11a          Channel 149 : 5745* Mhz 11a
> Channel  40 : 5200* Mhz 11a          Channel 153 : 5765* Mhz 11a
> Channel  42 : 5210* Mhz 11a          Channel 157 : 5785* Mhz 11a
> Channel  44 : 5220* Mhz 11a          Channel 161 : 5805* Mhz 11a
> Channel  46 : 5230* Mhz 11a          Channel 165 : 5825* Mhz 11a
> 
> Ad-Hoc mode without wep:
> # ifconfig -v ath0
> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255
>         inet6 fe80::205:4eff:fe4b:7613%ath0 prefixlen 64 scopeid 0x2
>         ether 00:05:4e:4b:76:13
>         media: IEEE 802.11 Wireless Ethernet autoselect <adhoc> 
> (autoselect <adhoc>)
>         status: associated
>         ssid cookie channel 7 (2442) bssid da:00:a4:01:3b:02
>         authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF
>         powersavesleep 100 txpowmax 34 txpower 60 rtsthreshold 2312 
> protmode CTS
>         wme roaming AUTO bintval 100
>         AC_BE cwmin  4 cwmax 10 aifs  3 txopLimit   0 -acm ack
>               cwmin  4 cwmax 10 aifs  3 txopLimit   0 -acm
>         AC_BK cwmin  4 cwmax 10 aifs  7 txopLimit   0 -acm ack
>               cwmin  4 cwmax 10 aifs  7 txopLimit   0 -acm
>         AC_VI cwmin  3 cwmax  4 aifs  2 txopLimit  94 -acm ack
>               cwmin  3 cwmax  4 aifs  2 txopLimit  94 -acm
>         AC_VO cwmin  2 cwmax  3 aifs  2 txopLimit  47 -acm ack
>               cwmin  2 cwmax  3 aifs  2 txopLimit  47 -acm

How about showing ifconfig when wep is configured?  And btw, the -v 
option is NOT needed; ifconfig should show all useful info w/o -v.

> 
> I also get a couple of these from time to time, could be related to
> reconfiguration.
> ath0: device timeout
> ath0: device timeout
> ath0: device timeout
> 

You should not get these.  Please go to /usr/src/tools/tools/ath and 
build athstats.  Run it w/o arguments and provide the output.  Please 
identify what your configuration was when these occurred (e.g. adhoc 
mode w/ wep?).

> Another minor thing I noted, when you play around with 'ifconfig ath0 
> wepmode'
> it looks like the wepkeys are displayed sometimes and sometimes not 
> afterwards, it seems very random. It it required to set wepkey and 
> wepmode in the same
> command?
> 

Never seen it.  You can enable debugging in the 802.11 layer and/or ath 
driver to observe crypto operations.  In the tools/ath directory you'll 
find athdebug and 80211debug apps; use them to enable debugging with 
something like

80211debug +crypto

to see 802.11 layer operations and/or

athdebug +crypto

to see stuff happen in the driver.

	Sam