Pavel Roskin <[EMAIL PROTECTED]> wrote: > On Sat, 2008-06-07 at 13:09 -0700, Bill Wohler wrote: > > > 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.
I use the identical stanza with madwifi so the key is right. > > 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. It's not the first two as I as I use the same stanza with madwifi. > > 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. I've been using madwifi on this box for years (as you noted about the age of the hardware :-). And I'm using it now since ath5k isn't working. Dropping WEP is a good idea. I'll try that when I have some time to see if we make any progress. Thanks! -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD _______________________________________________ ath5k-users mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-users
