On Thu, 2006-02-09 at 16:41 -0800, Grant wrote:
> I still can't get this to work. I have the essid and key defined in
> '/etc/conf.d/net'. I've tried defining the key like "s:key" and
> "s:key enc open" and "open s:key". I've tried other little things but
> to no avail. I can connect to a non-Airport WEP router via
> wpa_supplicant just fine, and an unencrypted non-Airport router via
> iwconfig just fine as well. What else could be the problem connecting
> to this WEP Airport router via iwconfig?
>
> I've also tried Eric's suggestion of running each command manually
> with the same results.
I've noticed that wireless can be sensitive to the order and timing of
running iwconfig commands.
Run these two lines from bash (substitute DEV=wlan0 for your device, and
the key and essid):
function iw { sleep 5; iwconfig 2>/dev/null | grep "Access Point"; }
DEV=wlan0 iw; sudo iwconfig $DEV essid youressid; iw; sudo iwconfig $DEV key
00001111222233334444555566; iw; sudo iwconfig $DEV key open; iw
then tell me if the output you see is like this:
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
or if you see something other than "Not-Associated". You could also try
playing with the order of the commands, but usually I find it goes
essid, key, enc.
HTH,
--
Iain Buchanan <iain at netspace dot net dot au>
Nezvannyi gost'--khuzhe tatarina.
[An uninvited guest is worse than the Mongol invasion]
-- Russian proverb
--
[email protected] mailing list
