Re: I lost ath0 support on current sometime between Sept 20 and Sept 26.

आशीष शुक्ल Ashish Shukla wrote:
> In <20080929173223.183035ohkgl7jk3b_at_econet.encontacto.net>, eculp wrote:
>
> [snip]
>
>> # ifconfig
>>
>> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
>> 2290
>> ether 00:1d:d9:27:5c:e5
>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
>> status: associated
>> pflog0: flags=0<> metric 0 mtu 33204
>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
>> inet6 ::1 prefixlen 128
>> inet 127.0.0.1 netmask 0xff000000
>> pfsync0: flags=0<> metric 0 mtu 1460
>> syncpeer: 224.0.0.240 maxupd: 128
>> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 
>> mtu 1500
>> ether 00:1d:d9:27:5c:e5
>> inet 172.16.0.7 netmask 0xffffff00 broadcast 172.16.0.255
>> media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11g
>> status: associated
>> ssid virus channel 6 (2437 Mhz 11g) bssid 00:1d:7e:51:e1:4d
>> regdomain 101 indoor ecm authmode OPEN privacy ON deftxkey 1
>> wepkey 1:40-bit txpower 16 bmiss 7 scanvalid 60 bgscan bgscanintvl 300
>> bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst
>
> I'm also experiencing the same issue, i.e. ifconfig output says 
> associated, but neither I can ping{,6} (or simply communicate with) 
> any of the nodes of my network, and I'm using static IP addresses. BtW 
> I've not tried 'ath' with previously available HAL 0.10.5.6.
Is this only w/ static key wep? Yesterday I re-tested open and wpa and 
both worked fine. I haven't had time to setup wep. I also see no stats 
or debug output that might explain what's wrong.

Sam