kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work

[Sam Leffler]

Matthias Apitz wrote:
> I went today evening with my EeePC and CURRENT on USB key
> to that Greek restaurant; DHCP does not get IP in CURRENT either;
> this is somehow good news, isn't it :-)
>
> below are some information concerning the AP, ifconfig ...
> the output of the tcpdump is on my server as
> http://www.unixarea.de/ath-current.txt
> let me know if you need more information;
>
> HIH
>
> 	matthias
>
>
> info about AP:
>     Siemens Gigaset SE 505 dsl/cable
>     S30853-S1006-R107-3
>     (handwritten label says: "this is no DSL router; IP 192.168.2.1")
>     as DSL-modem some Fritz!Box is connected to this box
>     http://reviews.cnet.com/routers/siemens-gigaset-se505-dsl/1707-3319_7-30799508.html
>
>
> # uname -a
> FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009     root at rebelion.Sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC  i386
>
> # ifconfig -a
> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
> 	ether 00:15:af:b2:ae:e6
> 	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
> 	status: associated
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> 	options=3<RXCSUM,TXCSUM>
> 	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
> 	inet6 ::1 prefixlen 128 
> 	inet 127.0.0.1 netmask 0xff000000 
> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 	ether 00:15:af:b2:ae:e6
> 	inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> 	media: IEEE 802.11 Wireless Ethernet DS/5.5Mbps mode 11g
> 	status: associated
> 	ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99
> 	regdomain 96 indoor ecm authmode OPEN privacy ON deftxkey 1
> 	wepkey 1:104-bit txpower 20 bmiss 7 scanvalid 450 bgscan
> 	bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS
> 	wme burst roaming MANUAL
>
>
>
> # tcpdump -n -i ath0 -y IEEE802_11_RADIO
> 17:56:24.647835 436598375373us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x00000012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11]
> 17:56:24.750225 436598477774us tsft 1.0 Mb/s -81dB signal -96dB noise antenna 1 [0x00000012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11]
> 17:56:24.852621 436598580174us tsft 1.0 Mb/s -79dB signal -96dB noise antenna 1 [0x00000012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11]
> 17:56:24.955019 436598682572us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x00000012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11]
> ...
>
> full log see: http://www.unixarea.de/ath-current.txt
>
>
>   
If you have the raw pcap capture please provide a url to it.

 From the log it appears you're sending+receiving wep-encrypted frames.  
They keyid is the same and since you're receiving frames I have to 
assume the key matter is correct as otherwise the h/w would drop the 
frame.  You can verify this by feeding the key into wireshark to check 
if the frame contents make sense.

I'm out of ideas.  About the only thing I can suggest is you setup a 
different ap w/ the same wep key and see if things work.  If so then you 
know it's something this ap is doing.  I can't recall when I last tested 
wep on HEAD but I'm pretty sure it works.  I will re-test that when I 
get a chance.

    Sam