Arch Linux

Ink-Jet

Member

From: London

Registered: 2008-03-27

Posts: 64

Website

WEP encrypted network - can't connect

I'm trying to use netcfg2.0.6 to connect to a WEP-encrypted network, but it doesn't work, with the error message:

:: father up  - Wireless association failed.                             [FAIL]

I can correctly connect to a different wpa-encrypted network, so I'm assuming it's a problem with my configuration, not my hardware.

ifconfig -a (just relevant wlan0 part) gives:

wlan0     Link encap:Ethernet  HWaddr 00:15:AF:3B:64:A9  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

iwconfig before attempting to connect (however, I have tried to connect earlier today, which is probably why the ESSID is set):

wlan0     IEEE 802.11g  ESSID:"02wireless314821"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The profile I'm using for this connection is:

CONNECTION="wireless"
INTERFACE=wlan0
SCAN=no
SECURITY="wep"
ESSID="02wireless314821"
KEY="xxxxxxxxxx"
IP="dhcp"
TIMEOUT=20

I'm using the stock kernel from testing, with the rtl8187 driver.

Does anyone have any idea what's wrong, and how to fix it?

sniffles

Member

Registered: 2008-01-23

Posts: 275

Re: WEP encrypted network - can't connect

Are you 100% sure the value of KEY is correct? (I.e. not suffering from typing mistakes or bad memory on your side). Try playing with the TIMEOUT option.

bangkok_manouel

Member

From: indicates a starting point

Registered: 2005-02-07

Posts: 1,556

Re: WEP encrypted network - can't connect

you can try scan=yes also.

JaQoB

Member

Registered: 2007-04-04

Posts: 60

Re: WEP encrypted network - can't connect

I having some problems as well, with intel iw3945.
Wep is working, but i need to try to connect 5-10 times for it to work. It worked fine some month ago (no idea when it broke, havent tried wep in a while).
WPA is till working like a charm.

Ink-Jet

Member

From: London

Registered: 2008-03-27

Posts: 64

Website

Re: WEP encrypted network - can't connect

Are you 100% sure the value of KEY is correct? (I.e. not suffering from typing mistakes or bad memory on your side). Try playing with the TIMEOUT option.

Absolutely, it's the one I used on my EEE, and that connects.

you can try scan=yes also.

With scan=yes, I get this output:

:: father up  - Network unavailable                                      [FAIL]

Is that important?

sniffles

Member

Registered: 2008-01-23

Posts: 275

Re: WEP encrypted network - can't connect

It means you should switch back to scan=no. http://wiki.archlinux.org/index.php/Net … leshooting

I'm guessing you have set-up more than one connection. Try to set the 'father' connection as default (i.e. to be activated on boot); reboot.. see if that works. (I've found that bringing down my wireless connection and then trying to reactivate it does not work, I'm too lazy to figure out why.)

Last edited by sniffles (2008-06-14 11:22:42)

dante4d

Member

From: Czech Republic

Registered: 2007-04-14

Posts: 176

Re: WEP encrypted network - can't connect

I have the exactly same issue. I have to do 'netcfg2 wifi' about 3-5 times to connect. I also have iwl3945. More here (my thread about this issue). I quickly wrote this script:

#!/bin/bash
ifconfig wlan0 up
iwconfig wlan0 essid linksys key `grep KEY /etc/network.d/wifi | cut -d'"' -f2`
sleep 1
ifconfig wlan0 192.168.1.101
echo "nameserver 192.168.1.1" > /etc/resolv.conf
route add default gw 192.168.1.1
sleep 1
ping www.seznam.cz

When run for the firs time, it freezes and I have to do ^C (C-c or Ctrl-c) to kill it and run it again. Second time it goes like:

SIOCADDRT: File exists
PING www.seznam.cz (77.75.76.3) 56(84) bytes of data.
64 bytes from www.seznam.cz (77.75.76.3): icmp_seq=1 ttl=56 time=14.1 ms
64 bytes from www.seznam.cz (77.75.76.3): icmp_seq=2 ttl=56 time=13.6 ms
^C
--- www.seznam.cz ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 13.680/13.938/14.197/0.284 ms

I haven't tested it more yet, because it works ten times faster than netcfg2 for me, which makes me happy for now. I have no idea whats going on behind if/iw commands.

Last edited by dante4d (2008-06-15 10:02:32)

Ink-Jet

Member

From: London

Registered: 2008-03-27

Posts: 64

Website

Re: WEP encrypted network - can't connect

It means you should switch back to scan=no. http://wiki.archlinux.org/index.php/Net … leshooting

I'm guessing you have set-up more than one connection. Try to set the 'father' connection as default (i.e. to be activated on boot); reboot.. see if that works. (I've found that bringing down my wireless connection and then trying to reactivate it does not work, I'm too lazy to figure out why.)

Yeah, I switched scan to no, like the wiki suggested, but it only changed the error message, lol.

Also, making this connection the only connection to connect at boot doesn't seem to help it.

dante4d, I don't think we have the same issue - while you can connect after a few tries, I can't, and you're using a completely different driver than I am.