Secured wireless networks timeout trying to connect

hydroxide · 2012-05-09 06:03:29

I should note that I previously had problems getting wireless to work at all. Crunchbang statler didn't even show any wireless networking capabilities were available (even blacklisting acer-wmi), and I tried linux mint debian which insisted that a hardware switch was turned on, fixed this by blacklisting acer-wmi module (don't know why it worked now).
Crunchbang waldorf fortunately solved these problems, but I have a new problem. I also had this problem once I got the wifi working on linux mint debian. I can connected to unsecured open wireless networks perfectly. However when I try to connect to a secured wireless network (wpa2), it spends about 30 seconds trying to authenticate/connect before it times out and disconnects. Searched the web but couldn't find any solutions.

Thanks! smile

xaos52 · 2012-05-09 09:11:02

Post output of

lspci -n

The ath5k kernel module had this bug. I do not know if it has been solved by now.

hydroxide · 2012-05-10 03:28:09

Hi, thanks for the reply. Here is the output:

00:00.0 0600: 8086:0104 (rev 09)
00:02.0 0300: 8086:0116 (rev 09)
00:16.0 0780: 8086:1c3a (rev 04)
00:1a.0 0c03: 8086:1c2d (rev 05)
00:1b.0 0403: 8086:1c20 (rev 05)
00:1c.0 0604: 8086:1c10 (rev b5)
00:1c.1 0604: 8086:1c12 (rev b5)
00:1c.3 0604: 8086:1c16 (rev b5)
00:1d.0 0c03: 8086:1c26 (rev 05)
00:1f.0 0601: 8086:1c49 (rev 05)
00:1f.2 0106: 8086:1c03 (rev 05)
00:1f.3 0c05: 8086:1c22 (rev 05)
02:00.0 0280: 8086:0886 (rev 67)
03:00.0 0200: 10ec:8168 (rev 06)
00:00.0 0600: 8086:0104 (rev 09)
00:02.0 0300: 8086:0116 (rev 09)
00:16.0 0780: 8086:1c3a (rev 04)
00:1a.0 0c03: 8086:1c2d (rev 05)
00:1b.0 0403: 8086:1c20 (rev 05)
00:1c.0 0604: 8086:1c10 (rev b5)
00:1c.1 0604: 8086:1c12 (rev b5)
00:1c.3 0604: 8086:1c16 (rev b5)
00:1d.0 0c03: 8086:1c26 (rev 05)
00:1f.0 0601: 8086:1c49 (rev 05)
00:1f.2 0106: 8086:1c03 (rev 05)
00:1f.3 0c05: 8086:1c22 (rev 05)
02:00.0 0280: 8086:0886 (rev 67)
03:00.0 0200: 10ec:8168 (rev 06)

xaos52 · 2012-05-10 10:03:18

I guess you are using network-manager to manage your network.
Lets eliminate network-manager from the equation:
(1) stop network-manager:

sudo invoke-rc.d network-manager stop

(2) stop nm-applet

pkill nm-applet

(3) disable network-manager

sudo update-rc.d network-manager disable

(4) run the following commands in a root terminal window:

pkill wpa
pkill dhclient
wpa_passphrase sssssssss pppppppp >/tmp/wpa.conf

replace sssssssss by your ssid and ppppppppp by your wpa passkey

wpa_supplicant -Dwext -iwlan0 -c /tmp/wpa.conf -dd &
sleep 1                                         
dhclient wlan0 &

Try to connect.
If you can not connect, enable network-manager again:

sudo update-rc.d network-manager enable

and reboot

Post output of

sudo cat /var/log/syslog | grep -Ei 'wpa|dhc'

Last edited by xaos52 (2012-05-10 10:22:32)

tedbell · 2012-05-10 11:15:48

I had all sorts of wireless problems until I ditched N.M. and installed wicd. big_smile

sudo apt-get install wicd

hydroxide · 2012-05-11 04:45:06

Hi xaos52. I tried what you suggested, however it hangs trying to connect. I re-enabled network-manager and here is the output you asked for:

May 10 21:34:53 tom-lenovo dbus[1333]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
May 10 21:34:54 tom-lenovo dbus[1333]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
May 10 21:34:54 tom-lenovo NetworkManager[1445]: <info> wpa_supplicant started
May 10 21:34:56 tom-lenovo wpa_supplicant[1496]: Trying to authenticate with 00:14:d1:42:d6:ec (SSID='Unit5' freq=2447 MHz)
May 10 21:34:56 tom-lenovo wpa_supplicant[1496]: Trying to associate with 00:14:d1:42:d6:ec (SSID='Unit5' freq=2447 MHz)
May 10 21:34:56 tom-lenovo wpa_supplicant[1496]: Associated with 00:14:d1:42:d6:ec
May 10 21:34:56 tom-lenovo wpa_supplicant[1496]: CTRL-EVENT-CONNECTED - Connection to 00:14:d1:42:d6:ec completed (auth) [id=0 id_str=]
May 10 21:34:56 tom-lenovo NetworkManager[1445]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 10 21:34:56 tom-lenovo NetworkManager[1445]: <info> dhclient started with pid 1547
May 10 21:34:56 tom-lenovo dhclient: Internet Systems Consortium DHCP Client 4.2.2
May 10 21:34:56 tom-lenovo dhclient: Copyright 2004-2011 Internet Systems Consortium.
May 10 21:34:56 tom-lenovo dhclient: All rights reserved.
May 10 21:34:56 tom-lenovo dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 10 21:34:56 tom-lenovo dhclient: 
May 10 21:34:56 tom-lenovo NetworkManager[1445]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
May 10 21:34:56 tom-lenovo dhclient: Listening on LPF/wlan0/40:25:c2:38:2e:08
May 10 21:34:56 tom-lenovo dhclient: Sending on   LPF/wlan0/40:25:c2:38:2e:08
May 10 21:34:56 tom-lenovo dhclient: Sending on   Socket/fallback
May 10 21:34:56 tom-lenovo dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
May 10 21:34:56 tom-lenovo dhclient: DHCPACK from 192.168.1.1
May 10 21:34:56 tom-lenovo NetworkManager[1445]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
May 10 21:34:56 tom-lenovo dhclient: bound to 192.168.1.104 -- renewal in 229586 seconds.
May 10 21:36:05 tom-lenovo NetworkManager[1445]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1547
May 10 21:36:05 tom-lenovo wpa_supplicant[1496]: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
May 10 21:37:45 tom-lenovo dhclient: can't create /var/lib/dhcp/dhclient.leases: Permission denied
May 10 21:37:45 tom-lenovo dhclient: Open a socket for LPF: Operation not permitted
May 10 21:39:27 tom-lenovo dbus[1321]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
May 10 21:39:27 tom-lenovo dbus[1321]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
May 10 21:39:28 tom-lenovo NetworkManager[1433]: <info> wpa_supplicant started
May 10 21:39:30 tom-lenovo wpa_supplicant[1485]: Trying to authenticate with 00:14:d1:42:d6:ec (SSID='Unit5' freq=2447 MHz)
May 10 21:39:30 tom-lenovo wpa_supplicant[1485]: Trying to associate with 00:14:d1:42:d6:ec (SSID='Unit5' freq=2447 MHz)
May 10 21:39:30 tom-lenovo wpa_supplicant[1485]: Associated with 00:14:d1:42:d6:ec
May 10 21:39:30 tom-lenovo wpa_supplicant[1485]: CTRL-EVENT-CONNECTED - Connection to 00:14:d1:42:d6:ec completed (auth) [id=0 id_str=]
May 10 21:39:30 tom-lenovo NetworkManager[1433]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 10 21:39:30 tom-lenovo NetworkManager[1433]: <info> dhclient started with pid 1535
May 10 21:39:30 tom-lenovo dhclient: Internet Systems Consortium DHCP Client 4.2.2
May 10 21:39:30 tom-lenovo dhclient: Copyright 2004-2011 Internet Systems Consortium.
May 10 21:39:30 tom-lenovo dhclient: All rights reserved.
May 10 21:39:30 tom-lenovo dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 10 21:39:30 tom-lenovo dhclient: 
May 10 21:39:30 tom-lenovo NetworkManager[1433]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
May 10 21:39:30 tom-lenovo dhclient: Listening on LPF/wlan0/40:25:c2:38:2e:08
May 10 21:39:30 tom-lenovo dhclient: Sending on   LPF/wlan0/40:25:c2:38:2e:08
May 10 21:39:30 tom-lenovo dhclient: Sending on   Socket/fallback
May 10 21:39:30 tom-lenovo dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
May 10 21:39:30 tom-lenovo dhclient: DHCPACK from 192.168.1.1
May 10 21:39:30 tom-lenovo dhclient: bound to 192.168.1.104 -- renewal in 244823 seconds.
May 10 21:39:30 tom-lenovo NetworkManager[1433]: <info> (wlan0): DHCPv4 state changed preinit -> reboot

xaos52 · 2012-05-11 06:25:59

Hmm... the info you posted is no help: it contains only messages after the reboot. Perhaps you clean your log files at reboot?

There is another way to collect the info though:

Install the bsdutils package if you have not got it installed already

sudo apt-get install bsdutils

(1) stop network-manager:

sudo invoke-rc.d network-manager stop

(2) stop nm-applet

pkill nm-applet

(3) disable network-manager

sudo update-rc.d network-manager disable

(4) run the following commands in a root terminal window:
We will be logging the output using script

script

This will get you into a subshell, while the original shell process you were in logs all input and output to a file 'typescript':

pkill wpa
pkill dhclient
ps aux|grep -Ei 'wpa|dhc'
wpa_passphrase sssssssss pppppppp >/tmp/wpa.conf

replace sssssssss by your ssid and ppppppppp by your wpa passkey

wpa_supplicant -Dwext -iwlan0 -c /tmp/wpa.conf -dd &
sleep 1                                         
dhclient wlan0 &

Try to connect.

whether it works or not: go back to the terminal window you had open and type
Ctrl+D
This will get you out of the script subshell.
There will be a file 'typescript' in your current directory.
Post the content of that file please.
Use PASTEBIN please.

If you can not connect, enable network-manager again:

sudo update-rc.d network-manager enable

and reboot

Last edited by xaos52 (2012-05-11 06:36:20)

hydroxide · 2012-05-11 08:59:53

Hi xaos52. Thanks for the help. As I said, the terminal hangs trying to connect. The contents of the typescript file are here: http://crunchbanglinux.org/pastebin/1646 (unaltered, except for where I enter the network password into the prompt)

xaos52 · 2012-05-11 09:22:10

OK. I am having a look at it now.
Is that the complete file? It seems to terminate rather abrupt.
Good move to edit it for confidential info. smile

EDIT: You did leave the terminal window open when you tested your connection? If you closed the terminal window, that would have killed the registering process.

Sorry for not thinking about that earlier.

Last edited by xaos52 (2012-05-11 09:25:46)

xaos52 · 2012-05-11 09:40:27

Well...
What I am seeing is all normal.
Connection with the AP enters 4-WAY-HANDSHAKE protocol.
Then the output stops at step 2/4.

xaos52 · 2012-05-11 09:52:02

Can you try the solution proposed here https://bugs.launchpad.net/ubuntu/+sour … bug/922630 in post # 3

Run

lsmod|grep -Ei 'iwlagn|iwlwifi'

to determine which solution to use.

If that works, you will have to make it persist by adding a config file in /etc/modprobe.d.

Last edited by xaos52 (2012-05-11 09:52:44)

hydroxide · 2012-05-11 11:17:51

Sorry, I was under the impression that running wpa_supplicant in the terminal as you described is what you meant by try to connect? Or is some other action needed. If I was ambiguous earlier, the terminal hangs halfway through the process. That is the reason that the file ends abruptly - I have to close the terminal manually after a few minutes or it would sit there forever trying to connect. Using network manager, it decides to just disconnect after about 30 seconds rather than sitting there forever.

The new solution you posted does not work either sad
Thanks for your patience.

xaos52 · 2012-05-11 11:29:34

wpa_supplicant and dhclient are two processes that must be running before any network connection can be made.

The terminal should stay open long enough for you to try and make a network connection - for example use wireless to access this forum with your browser.

After the connection in your browser has timed out, 30 seconds is not an eternity, no? smile go back to the terminal and enter
CTRL+C
This will stop the 'script' session and drop you in the parent process's shell.
Then you can close the terminal window, or enter
CTRL+D
to close the window.

hope this helps.

PS: Now I know what you mean: the terminal seems to hang forever. If you press the 'enter' key a couple of times, you wil get your prompt back and you can enter the rest of the commands.

PS2: Never mind PS. You are right.
wpa_supplicant runs in the foreground and prevents you from entering the dhclient command.
You will have to open another terminal window and enter the dhclient command in the second window.
No need to run 'script' in the 2nd window, just the dhclient command, that runs in the background.

Last edited by xaos52 (2012-05-11 11:39:49)

CrunchBang Linux

SEARCH

#1 2012-05-09 06:03:29

Secured wireless networks timeout trying to connect

#2 2012-05-09 09:11:02

Re: Secured wireless networks timeout trying to connect

#3 2012-05-10 03:28:09

Re: Secured wireless networks timeout trying to connect

#4 2012-05-10 10:03:18

Re: Secured wireless networks timeout trying to connect

#5 2012-05-10 11:15:48

Re: Secured wireless networks timeout trying to connect

#6 2012-05-11 04:45:06

Re: Secured wireless networks timeout trying to connect

#7 2012-05-11 06:25:59

Re: Secured wireless networks timeout trying to connect

#8 2012-05-11 08:59:53

Re: Secured wireless networks timeout trying to connect

#9 2012-05-11 09:22:10

Re: Secured wireless networks timeout trying to connect

#10 2012-05-11 09:40:27

Re: Secured wireless networks timeout trying to connect

#11 2012-05-11 09:52:02

Re: Secured wireless networks timeout trying to connect

#12 2012-05-11 11:17:51

Re: Secured wireless networks timeout trying to connect

#13 2012-05-11 11:29:34

Re: Secured wireless networks timeout trying to connect

Board footer