[Solved] Netctl - Cannot connect to wireless network

diiis · 2013-05-16 23:23:46

Hi,

since I replaced netcfg with netctl a week ago, it worked just fine. Today, however, i wanted to connect to a different wireless network and i couldn't make it work.

Here's some information about how i connected to my home network (which worked fine):

I changed the netcfg config files to match netctl syntax (as described in the wiki)
I activated netctl-auto@wlan0
The connection to the network was established almost immediately after (re)boot or resume after suspend

First off: I double-checked the config file for the second network. Both syntax and SSID/passphrase are correct. Also, I don't have special characters in my network/profile names, the names in brackets are placeholders.

Here's what happens after a fresh reboot (only the second network is in range of my pc, so it doesn't connect to my first - working - network):

Netctl-auto is active and running, but seems to repeatedly lose connection to the second network:

# systemctl status netctl-auto@wlan0
netctl-auto@wlan0.service - Automatic wireless network connection using netctl profiles
   Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled)
   Active: active (running) since Fri 2013-05-17 00:28:03 CEST; 13min ago
     Docs: man:netctl.special(7)
  Process: 453 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
   CGroup: name=systemd:/system/netctl-auto@.service/netctl-auto@wlan0.service
           ├─480 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa_supplicant_wlan0.conf -W
           └─483 wpa_actiond -p /run/wpa_supplicant -i wlan0 -P /run/network/wpa_actiond_wlan0.pid -a /usr/lib/network/auto.action

May 17 00:41:40 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:41 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:48 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:48 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:51 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:51 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:54 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:54 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:58 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:58 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'

# journalctl -xn
-- Logs begin at Sat 2012-12-08 23:44:06 CET, end at Fri 2013-05-17 00:47:43 CEST. --
May 17 00:47:33 <hostname> kernel: cfg80211: Calling CRDA to update world regulatory domain
May 17 00:47:36 <hostname> kernel: wlan0: authenticate with <network_2 mac address>
May 17 00:47:36 <hostname> kernel: wlan0: send auth to <network_2 mac address> (try 1/3)
May 17 00:47:36 <hostname> kernel: wlan0: authenticated
May 17 00:47:36 <hostname> kernel: wlan0: associate with <network_2 mac address> (try 1/3)
May 17 00:47:36 <hostname> kernel: wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
May 17 00:47:36 <hostname> kernel: wlan0: associated
May 17 00:47:36 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'

More interestingly, dmesg seems to provide a reason for this behaviour:

# dmesg
[ 1438.732242] wlan0: authenticate with <network_2 mac address>
[ 1438.737594] wlan0: send auth to <network_2 mac address> (try 1/3)
[ 1438.740384] wlan0: authenticated
[ 1438.743113] wlan0: associate with <network_2 mac address> (try 1/3)
[ 1438.747226] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
[ 1438.767629] wlan0: associated
[ 1438.837011] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[ 1438.837024] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
[ 1438.896427] cfg80211: Calling CRDA to update world regulatory domain
[ 1442.140427] wlan0: authenticate with <network_2 mac address>
[ 1442.145282] wlan0: send auth to <network_2 mac address> (try 1/3)
[ 1442.148090] wlan0: authenticated
[ 1442.151674] wlan0: associate with <network_2 mac address> (try 1/3)
[ 1442.155712] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
[ 1442.175911] wlan0: associated
[ 1442.214954] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[ 1442.214967] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
[ 1442.258359] cfg80211: Calling CRDA to update world regulatory domain

I'm pretty sure everything should theoretically work fine, because it worked before the netctl update. I was even connected to this network today until i had to reboot!

Now here's what happens if I try to connect manually:

# netctl start <network_2>
Job for netctl@<network_2>.service failed. See 'systemctl status netctl@<network_2>.service' and 'journalctl -xn' for details.

# systemctl status netctl@<network_2>.service
netctl@<network_2>.service - Networking for netctl profile <network_2>
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Fri 2013-05-17 00:58:40 CEST; 2min 36s ago
     Docs: man:netctl.profile(5)
  Process: 7368 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)

May 17 00:58:40 <hostname> network[7368]: Starting network profile '<network_2>'...
May 17 00:58:40 <hostname> network[7368]: The interface of network profile '<network_2>' is already up
May 17 00:58:40 <hostname> systemd[1]: netctl@<network_2>.service: main process exited, code=exited, status=1/FAILURE
May 17 00:58:40 <hostname> systemd[1]: Failed to start Networking for netctl profile <network_2>.
May 17 00:58:40 <hostname> systemd[1]: Unit netctl@<network_2>.service entered failed state.

After an # ip link set wlan0 down netctl still claims that its job failed:

# netctl start <network_2>
Job for netctl@<network_2>.service failed. See 'systemctl status netctl@<network_2>.service' and 'journalctl -xn' for details.

This time, the DHCP lease attempt seems to be failing:

# systemctl status netctl@<network_2>.service
netctl@<network_2>.service - Networking for netctl profile <network_2>
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Fri 2013-05-17 01:04:42 CEST; 1min 33s ago
     Docs: man:netctl.profile(5)
  Process: 8423 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)

May 17 01:04:23 <hostname> systemd[1]: Starting Networking for netctl profile <network_2>...
May 17 01:04:23 <hostname> network[8423]: Starting network profile '<network_2>'...
May 17 01:04:31 <hostname> dhcpcd[8656]: version 5.6.8 starting
May 17 01:04:31 <hostname> dhcpcd[8656]: wlan0: carrier lost
May 17 01:04:31 <hostname> dhcpcd[8656]: wlan0: waiting for carrier
May 17 01:04:41 <hostname> dhcpcd[8656]: timed out
May 17 01:04:41 <hostname> network[8423]: DHCP IP lease attempt failed on interface 'wlan0'
May 17 01:04:42 <hostname> systemd[1]: netctl@<network_2>.service: main process exited, code=exited, status=1/FAILURE
May 17 01:04:42 <hostname> systemd[1]: Failed to start Networking for netctl profile <network_2>.
May 17 01:04:42 <hostname> systemd[1]: Unit netctl@<network_2>.service entered failed state.

I wasn't able to find out whether netctl needs a running dhcpcd or not, but after running a systemctl start dhcpcd.service, dmesg seems to give a little more information:

# dmesg
[ 2500.090650] wlan0: authenticate with <network_2 mac address>
[ 2500.109377] wlan0: send auth to <network_2 mac address> (try 1/3)
[ 2500.114053] wlan0: authenticated
[ 2500.115817] wlan0: associate with <network_2 mac address> (try 1/3)
[ 2500.121336] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
[ 2500.147262] wlan0: associated
[ 2500.303529] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[ 2500.303542] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
[ 2500.327471] cfg80211: Calling CRDA to update world regulatory domain
[ 2769.285673] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 2769.285908] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 2769.488380] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Any pointers and solutions are greatly appreciated.

Thanks,
diiis

Last edited by diiis (2013-05-23 16:45:47)

silverzhao · 2013-05-17 06:03:11

What if you do not use netctl? Can you connect to wireless network by just using dhcpcd/wpa_supplicant?

hendry · 2013-05-20 09:18:09

@silverzhao I use a manual dhcpcd/wpa_supplicant way of setting up my wlan0 using http://git.r-36.net/conn and I have the same problem.

I have to kill my wireless and restart after seeing a message like:

May 20 10:12:33 x220 kernel: wlan0: AP a4:b1:e9:55:25:2f changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz)

Old user, new ID · 2013-05-20 18:47:13

The bug is in the kernel. I had it with 3.9.2 and 3.10-rc1.

Reverting to 3.8.x fixed it for me. Your milage might vary.

hendry · 2013-05-20 19:18:36

Has someone bothered to report the bug? I just did:

https://bugzilla.kernel.org/show_bug.cgi?id=58561

Last edited by hendry (2013-05-20 21:08:20)

diiis · 2013-05-23 16:45:15

Okay, now it is working without me doing anything about it since my post. Must have been a router issue or something like that.

Thanks anyway!

hendry · 2013-05-23 19:30:16

My router is a Technicolor TG582n. Still have the problem.

Arch Linux

#1 2013-05-16 23:23:46

[Solved] Netctl - Cannot connect to wireless network

#2 2013-05-17 06:03:11

Re: [Solved] Netctl - Cannot connect to wireless network

#3 2013-05-20 09:18:09

Re: [Solved] Netctl - Cannot connect to wireless network

#4 2013-05-20 18:47:13

Re: [Solved] Netctl - Cannot connect to wireless network

#5 2013-05-20 19:18:36

Re: [Solved] Netctl - Cannot connect to wireless network

#6 2013-05-23 16:45:15

Re: [Solved] Netctl - Cannot connect to wireless network

#7 2013-05-23 19:30:16

Re: [Solved] Netctl - Cannot connect to wireless network

Board footer