On Sat, 2008-06-07 at 13:09 -0700, Bill Wohler wrote: > And I've got this: > > $ lspci -nn |grep Ath > 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5211 > 802.11ab NIC [168c:0012] (rev 01)
Wow, that's some old piece of hardware! I used to have one, but I don't have it anymore, so I cannot check its ath5k compatibility. > After I say "ifup ath0", iwconfig reveals that ath0 is associated to my > AP and ifconfig looks right (as it should with a static config). dmesg > looks great too: ... > ath0: Initial auth_alg=0 > ath0: authenticate with AP 02:1e:58:07:5d:f2 > ath0: RX authentication from 02:1e:58:07:5d:f2 (alg=0 transaction=2 > status=0) > ath0: authenticated That's open system authentication. It can happen with a wrong WEP key, so you may want to check if the key is correct. > However, I can't ping my access point. Either the key is wrong, or the IP address, or ath5k has issues with WEP on your hardware. > Do I need some extra magic in /etc/network/interfaces? Any other hints > or advice appreciated! I suggest that you run ifconfig and iwconfig to check the actual settings. Try scanning. Try connecting to an AP without WEP. Try using dhcp if it's supported by the AP. Try MadWifi to see if it's the driver issue or something else. -- Regards, Pavel Roskin _______________________________________________ ath5k-users mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-users
