Wireless connection doesn't work, Error, Eth0: timed out

Perre · 2008-01-22 20:47:21

Hi!

I've been searching this forum and reading the wiki, but I can't figure out how to fix my wireless connection.
When I boot up (or restart network) I get this message:

Starting network [Busy]

and then

Error, Eth0: Timed out
Warning, eth0: Using IPV4LL adress 169.254.###.###

At first I got error messages about fatal error: module doesn't work (or something) but I fixed it by installing
madwifi. After that I get the message above.

I connected my computer to the router through lan cable and the connection worked fine. I was able to update
the system and all. But when I disconnected the cable and tried the wireless connection it still says the same thing.

My rc.conf looks like this:

HOSTNAME="Per"

lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

etc/conf.d/wireless:

# wlan_eth0="eth0 mode manages essid default"
# WLAN:INTERFACES=(eth0)

I tried to change this to

wlan_eth0="eth0 essid #### key ########"
WLAN_INTERFACES=(eth0)

but it didn't work. I reall don't know what the problem is
but the router is password protected so I guess I'm supposed
to put in the password somewhere (I'm just guessing here )

Anyway, I hope somebody can help me.
Thanks!

Misfit138 · 2008-01-22 21:06:08

First problem I see is; if you are using DHCP, then the gateway= line should be commented out.

Perre · 2008-01-22 21:14:49

Tried to # gateway, but I still get the timed out reply...

tomk · 2008-01-22 21:23:58

madwifi creates an 'ath0' interface - use that instead of eth0.

Misfit - his syntax is correct. 'gateway' is defined, but disabled in the ROUTES array.

Perre · 2008-01-22 21:30:18

Does that mean just changing eth0 in rc.conf and /etc/conf.d/wireless to ath0 or do I have to change it somewhere else also?

blu3ness · 2008-01-22 23:29:58

hmm.. to bring up an interface, u don't really need to edit any configuration files...

try iwconfig to see if you have a wireless interface up and running

for example

wlan0     IEEE 802.11b  ESSID:"ualbertawireless"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:01:E6:FF:A4:FB
          Bit Rate=11 Mb/s   Tx-Power:32 dBm
          RTS thr:2347 B   Fragment thr:2346 B
          Power Management:off
          Link Quality:26/100  Signal level:-79 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If you do see that interface, then just do the following

su
iwconfig <interface_name> essid <essid in text without quotes>
dhcpcd <interface_name>

If you don't see any wireless interface, that means you havn't setup your drivers properly, try to do that first

Last edited by blu3ness (2008-01-22 23:30:37)

Perre · 2008-01-23 13:09:29

Thanks for the replies guys!

I'm still trying to get it to work, but I think I'm getting closer. Did the driver setup on the madwifi.org web page.
Managed to connect to one of the networks here in the area so the wireless connection is up and running. The problem now
is connecting to the right router. It's also WAP-protected so it's a bit of a hassle.

Anyway, by doing as instructed in the madwifi userdocs I've created a new /etc/wpa_supplicant.conf file. I'm having a hard time
understanding how to set it up, but this is what I've done so far (the router is configured with WPA-PSK as I can see here on my
girlfriends windows computer).

wpa_supplicant.conf:

network={
ssid="3Com"
psk="######a bunch of numbers and letters####"
priority=1

When I then try to see if it works by:
# wpa_supplicant -w -Dwext -iath0 -c/etc/wpa_supplicant.conf

I get the following:

Line 3: Invalid passphrase length 64 (expected: 8..63) '######the same numbers and letters as in .conf file"'.
Line 3: failed to parse psk '"####the numbers and letters again####"'.
Line 4: network block was not terminated properly.
Line 4: WPA-PSK accepted for key management, but no PSK configured.
Line 4: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.

I got the psk by doing:
wpa_passphrase 3Com ###the password we use###

I've doublechecked the psk to see if I might have written it down incorrectly, but it's fine. Hmm... sems like I'm getting closer though.

Perre · 2008-01-23 14:12:06

Ok, I erased the long line of letters and numbers and replaced it with the original password.

I now get this message:

Network block was not terminated properly.
failed to parse network block.
failed to read or parse configuration '/etc/wpa_supplicant.conf'.

Seems the password is getting accepted now, but something is still wrong.
The search continues.

renners1 · 2008-01-23 14:30:27

I get the same timeout error message you got at first BUT network starts up ok! Have you actually tested the network or are your assuming it's failed because of the message?

Perre · 2008-01-23 14:54:01

I always try
# ping bbc.co.uk

after I change stuff so I'm not connected. Managed to connect to another router so the wireless card is working.
I'm writing this on a windows computer connected to my router so it's also working.

When I type # wpa_supplicant -w -Dwext -iath0 -c/etc/wpa_supplicant.conf I now get:

Trying to associate with 00:12:a9:d1:22:46 (SSID='3Com' freq=2462 MHz)
Authentication with 00:12:a9:d1:22:46 timed out.

It seems the problem is getting through the authentication. I'm a bit confused with what's supposed to be used in
etc/wpa_supplicant.conf' after psk. When I use (Ascii I think, numbers and letters) I get "Invalid passphrase length
64 (expected: 8..63) and when I just type in the password after psk I get authentication... timed out (as above).

What am I supposed to use?

loosec · 2008-01-23 21:26:49

I learned alot from using wicd and its autogenerated wpa_supplicant-configfiles. They will be located in /usr/lib/wicd/encryption/[MAC-Adress-of-Basestation] when you have tried connecting atleast once.

su
pacman -S wicd --noconfirm
/etc/rc.d/wicd start
/usr/lib/wicd/gui.py

check settings
find network, add key in advanced -> encryption [WPA 1/2]
klick connect

http://wiki.archlinux.org/index.php/Wicd

Last edited by loosec (2008-01-23 21:28:34)

MoonSwan · 2008-01-23 22:45:07

I use WPA as well & a similar chip to what you use. Ignore this guys stuff about making a menu choice and the bit about "fwcutter". Otherwise, follow his instructions & your wifi should work properly.

http://wiki.archlinux.org/index.php/Ndi … supplicant

Arch Linux

#1 2008-01-22 20:47:21

Wireless connection doesn't work, Error, Eth0: timed out

#2 2008-01-22 21:06:08

Re: Wireless connection doesn't work, Error, Eth0: timed out

#3 2008-01-22 21:14:49

Re: Wireless connection doesn't work, Error, Eth0: timed out

#4 2008-01-22 21:23:58

Re: Wireless connection doesn't work, Error, Eth0: timed out

#5 2008-01-22 21:30:18

Re: Wireless connection doesn't work, Error, Eth0: timed out

#6 2008-01-22 23:29:58

Re: Wireless connection doesn't work, Error, Eth0: timed out

#7 2008-01-23 13:09:29

Re: Wireless connection doesn't work, Error, Eth0: timed out

#8 2008-01-23 14:12:06

Re: Wireless connection doesn't work, Error, Eth0: timed out

#9 2008-01-23 14:30:27

Re: Wireless connection doesn't work, Error, Eth0: timed out

#10 2008-01-23 14:54:01

Re: Wireless connection doesn't work, Error, Eth0: timed out

#11 2008-01-23 21:26:49

Re: Wireless connection doesn't work, Error, Eth0: timed out

#12 2008-01-23 22:45:07

Re: Wireless connection doesn't work, Error, Eth0: timed out

Board footer