[SOLVED] Can't connect to a certain wifi network: No secrets provided

PBS · 2015-09-03 11:31:30

I am having a wi-fi problem which I know is the result of some simple misconfiguration, but cannot for the life of me figure out what it is.

When I try to connect to a certain wi-fi network within kde 5, well... what happens next is best described in pseudecode:

- Select wi-fi network from graphical menu.
- A passphrase is requested, which I enter correctly.

start:
- There is a pause of about 10 seconds, while the wi-fi indicator is stuck at "configuring interface".
- The indicator changes to "waiting for authorisation", and a dialog appears with the following message:
"For accessing the wireless network $SSID you need to provide a password below".
Note: the password I just typed is not already in the box.
- Enter same passphrase again. Press either OK or Cancel.

- if (pressed OK) goto start:

- Kde pops up a notification: "Connection $SSID deactivated".
- Immediately another notification: "No secrets were provided".

Some important points:

The problem only occurs with this router, since I can connect to two others without problem.
The problem only occurs on Arch, since Xubuntu (14.04, on a different machine though) connects to the same router instantly. As does Windows on that laptop and another one, as well as three android phones. The router itself is not at fault.
The router is a BT Home Hub 4, and the laptop has an Intel Centrino Wireless-N 2230.
Looking in KWalletManager, the passphrase has been stored with all the other wi-fi passwords under Network Management > Maps.
Though I usually run ufw, the results are the same with ufw disabled.

I have also tried connecting using nmcli. Following the Wiki,

$ nmcli dev wifi connect $SSID

This however results in exactly the same loop as above. After exiting the loop, nmcli also prints

Error: Connection activation failed: (7) Secrets were required, but not provided.

After this, the journal is full of interesting things. I have snipped what I think is most relevant:

NetworkManager[19805]: <info> (wlp2s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
NetworkManager[19805]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[19805]: <info> (wlp2s0): Activation: (wifi) connection '$SSID' has security, and secrets exist. No new secrets needed.
...
NetworkManager[19805]: <warn> (wlp2s0): Activation: (wifi) association took too long
NetworkManager[19805]: <info> (wlp2s0): device state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[19805]: <warn> (wlp2s0): Activation: (wifi) asking for new secrets
kernel: wlp2s0: deauthenticating from 34:8a:ae:e4:d6:2e by local choice (Reason: 3=DEAUTH_LEAVING)
...
wpa_supplicant[527]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="$SSID" auth_failures=1 duration=10 reason=CONN_FAILED
wpa_supplicant[527]: wlp2s0: SME: Trying to authenticate with 34:8a:ae:e4:d6:2e (SSID='$SSID' freq=2437 MHz)
wpa_supplicant[527]: wlp2s0: Trying to associate with 34:8a:ae:e4:d6:2e (SSID='$SSID' freq=2437 MHz)
wpa_supplicant[527]: wlp2s0: Associated with 34:8a:ae:e4:d6:2e
wpa_supplicant[527]: wlp2s0: Authentication with 34:8a:ae:e4:d6:2e timed out.
wpa_supplicant[527]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=34:8a:ae:e4:d6:2e reason=3 locally_generated=1
wpa_supplicant[527]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="$SSID" auth_failures=1 duration=10 reason=CONN_FAILED
wpa_supplicant[527]: wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="$SSID"
wpa_supplicant[527]: wlp2s0: SME: Trying to authenticate with 34:8a:ae:e4:d6:2e (SSID='$SSID' freq=2437 MHz)
...
kernel: wlp2s0: deauthenticating from 34:8a:ae:e4:d6:2e by local choice (Reason: 3=DEAUTH_LEAVING)
kernel: cfg80211: Calling CRDA to update world regulatory domain

Notice the apparent contradiction between the parts in bold.

Any ideas?

Last edited by PBS (2015-09-23 14:39:30)

PBS · 2015-09-23 14:55:32

After observing

cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA to update world regulatory domain
...

in dmesg on each resume from suspend, I installed crda and edited its config file,

pacman -S crda
nano /etc/conf.d/wireless-regdom
...
WIRELESS_REGDOM="GB"

This fixed the dmesg errors, and my original problem was also fixed as a side effect. So it seems that BT Home Hubs reject connections coming from devices using the wrong regulatory domain, and the messages from NetworkManager were not relevant.
Hope this helps someone else.

cuteclown · 2018-01-20 14:08:56

Thank you, was struggling with the same problem!

circleface · 2018-01-20 20:05:07

Please do not necrobump old threads, especially solved ones. https://wiki.archlinux.org/index.php/Co … bumping.22

jasonwryan · 2018-01-20 20:11:45

...or with empty posts: https://wiki.archlinux.org/index.php/Co … mpty_posts

Closing

Arch Linux

#1 2015-09-03 11:31:30

[SOLVED] Can't connect to a certain wifi network: No secrets provided

#2 2015-09-23 14:55:32

Re: [SOLVED] Can't connect to a certain wifi network: No secrets provided

#3 2018-01-20 14:08:56

Re: [SOLVED] Can't connect to a certain wifi network: No secrets provided

#4 2018-01-20 20:05:07

Re: [SOLVED] Can't connect to a certain wifi network: No secrets provided

#5 2018-01-20 20:11:45

Re: [SOLVED] Can't connect to a certain wifi network: No secrets provided

Board footer