[gentoo-user] Connecting to a WEP Airport router

[gentoo-user] Connecting to a WEP Airport router

[Grant]

Hello, my housing complex just switched to an Airport router and I
can't seem to connect.  They are supposedly using WEP.  There was a
5-character psk at first and wpa_supplicant told me it was an invalid
key and it had to be at least 8 characters.  They switched it to a
13-character psk and I still can't connect, although I don't get the
invalid key error now.  Does anyone know how to connect to a WEP
Airport router with Gentoo?  Everyone else is using Windows and Mac
and they are connecting just fine.  I've tried lots of different
configurations in wpa_supplicant.conf to no avail and all of my
software is up to date.

- Grant

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Connecting to a WEP Airport router

[John Jolet]

On Feb 7, 2006, at 2:40 PM, Grant wrote:

> Hello, my housing complex just switched to an Airport router and I
> can't seem to connect.  They are supposedly using WEP.  There was a
> 5-character psk at first and wpa_supplicant told me it was an invalid
> key and it had to be at least 8 characters.  They switched it to a
> 13-character psk and I still can't connect, although I don't get the
> invalid key error now.  Does anyone know how to connect to a WEP
> Airport router with Gentoo?  Everyone else is using Windows and Mac
> and they are connecting just fine.  I've tried lots of different
> configurations in wpa_supplicant.conf to no avail and all of my
> software is up to date.
>
well, you DON'T use wpa_supplicant.  you put the key in /etc/conf.d/ 
wireless, unless it's open, you can say "any" and get connected.
> - Grant
>
> -- 
> gentoo-user@gentoo.org mailing list
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Connecting to a WEP Airport router

[Eric Bliss]

On Tuesday 07 February 2006 12:40 pm, Grant wrote:
> Hello, my housing complex just switched to an Airport router and I
> can't seem to connect.  They are supposedly using WEP.  There was a
> 5-character psk at first and wpa_supplicant told me it was an invalid
> key and it had to be at least 8 characters.  They switched it to a
> 13-character psk and I still can't connect, although I don't get the
> invalid key error now.  Does anyone know how to connect to a WEP
> Airport router with Gentoo?  Everyone else is using Windows and Mac
> and they are connecting just fine.  I've tried lots of different
> configurations in wpa_supplicant.conf to no avail and all of my
> software is up to date.
> 
> - Grant
> 

Well, this is, if not the right way, at least A way to do it...

iwconfig eth1 essid "whatevertheairportnetworknameis"
iwconfig eth1 key xxxx-xxxx-xx
ifconfig eth1 up
dchpcd eth1

That's the script I hacked out to connect to our local WEP encrypted Airport.  
Your milage may vary.

-- 
Eric Bliss
systems design and integration,
CreativeCow.Net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Connecting to a WEP Airport router

[Grant]

> > Hello, my housing complex just switched to an Airport router and I
> > can't seem to connect.  They are supposedly using WEP.  There was a
> > 5-character psk at first and wpa_supplicant told me it was an invalid
> > key and it had to be at least 8 characters.  They switched it to a
> > 13-character psk and I still can't connect, although I don't get the
> > invalid key error now.  Does anyone know how to connect to a WEP
> > Airport router with Gentoo?  Everyone else is using Windows and Mac
> > and they are connecting just fine.  I've tried lots of different
> > configurations in wpa_supplicant.conf to no avail and all of my
> > software is up to date.
> >
> well, you DON'T use wpa_supplicant.  you put the key in /etc/conf.d/
> wireless, unless it's open, you can say "any" and get connected.

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.

- Grant

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Connecting to a WEP Airport router

[Iain Buchanan]

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

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Connecting to a WEP Airport router

[Grant]

> > 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.

Hi Ian,

I'm just getting this:

Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00

Running that command doesn't make the LEDs on my wireless card blink
at all.  Usually when they blink out of sync it is searching and when
they blink together I'm connected.  Using iwconfig via
/etc/init.d/net.ath0 does make them blink together like it's
connected, but then they stop and I get the failed message.

Any ideas?  I'll try anything.

- Grant

-- 
gentoo-user@gentoo.org mailing list