Unable to connect to WiFi

an_origamian · 2022-01-29 20:21:24

The WiFi went down for some maintenance, and when it came back up I was unable to connect. The only change that I know of is that some addresses are now restricted. Under the assumption that my IP address was in that range, I tried to get a new lease by deleting all the leases I had (in /var/lib/dhcpcd/). I started dhcpcd.service again but I was still unable to connect.

GUI perspective:
When I connect to WiFi, I get a prompt for a password. I enter the password. The NetworkManager icon tooltip reads "Connecting", and after a while it pops up the password prompt again. I press ESC and get the message "No secrets were provided."

CLI perspective:

sudo dmesg -w

[  916.428528] iwlwifi 0000:5c:00.0: Radio type=0x2-0x1-0x0
[  916.730304] iwlwifi 0000:5c:00.0: Radio type=0x2-0x1-0x0
[  916.839436] wlo1: authenticate with <mac address>
[  916.842244] wlo1: send auth to <mac address> (try 1/3)
[  916.969426] wlo1: authenticate with <mac address>
[  916.969435] wlo1: send auth to <mac address> (try 1/3)
[  917.017627] wlo1: authenticated
[  917.021243] wlo1: associate with <mac address> (try 1/3)
[  917.026104] wlo1: RX AssocResp from <mac address> (capab=0x1511 status=40 aid=0)
[  917.026125] wlo1: <mac address> denied association (code=40)
[  927.095465] wlo1: authenticate with <mac address>
[  927.097995] wlo1: send auth to <mac address> (try 1/3)
[  927.104368] wlo1: authenticated
[  927.107982] wlo1: associate with <mac address> (try 1/3)
[  927.113497] wlo1: RX AssocResp from <mac address> (capab=0x1511 status=40 aid=0)
[  927.113509] wlo1: <mac address> denied association (code=40)
[  927.137286] wlo1: authenticate with <mac address>
[  927.140069] wlo1: send auth to <mac address> (try 1/3)
[  927.401451] wlo1: authenticate with <mac address>
[  927.401461] wlo1: send auth to <mac address> (try 1/3)
[  927.500019] wlo1: authenticated
[  927.501314] wlo1: associate with <mac address> (try 1/3)
[  927.505141] wlo1: RX AssocResp from <mac address> (capab=0x1511 status=40 aid=0)
[  927.505156] wlo1: <mac address> denied association (code=40)
[  945.558644] iwlwifi 0000:5c:00.0: Radio type=0x2-0x1-0x0
[  945.859992] iwlwifi 0000:5c:00.0: Radio type=0x2-0x1-0x0

Last edited by an_origamian (2022-01-29 20:22:00)

-thc · 2022-01-29 21:56:12

an_origamian wrote:

The WiFi went down for some maintenance, and when it came back up I was unable to connect. The only change that I know of is that some addresses are now restricted.

AFAIK restrictions of this kind are realized via hardware (MAC) address of WiFi adapters.
This is consistent with the error messages.
Your WiFi MAC address seems to be restricted from accessing this WiFi network.

seth · 2022-01-29 22:03:25

If you're using NM, https://wiki.archlinux.org/title/Networ … domization is prone to piss off restritive APs so try to disable that.
If that's not the cause, ask your IT about the MAC and if they think it should be fine, please post the tail of the system journal so we can see kernel and NM interacting.

an_origamian · 2022-01-30 00:16:29

There is no MAC filtering, so the address shouldn't be a problem.

I followed the linked instructions to disable randomization:

/etc/NetworkManager/NetworkManager.conf

[device-mac-randomization]
wifi.scan-rand-mac-address=yes

[connection-mac-randomization]
ethernet.cloned-mac-address=random
wifi.cloned-mac-address=stable

Still doesn't connect.

Here is the journal: http://ix.io/3NX4

tbg · 2022-01-30 08:49:11

It should be "no" instead of "yes" above ^^^

-thc · 2022-01-30 08:55:59

BTW: What kind of device supplies this WiFI and what was the maintenance?

fred777 · 2022-01-31 18:08:50

I had the same problem couple of days ago after an Arch system update. My X230 with iwlwifi (Centrino 6205 AGN) was not able to connect to my router (AVM Fritzbox 7590) anymore.

Jan 31 13:26:40 x230 wpa_supplicant[921]: wlp3s0: SME: Trying to authenticate with my:ro:ut:er:sm:ac (SSID='myssid' freq=5180 MHz)
Jan 31 13:26:40 x230 kernel: wlp3s0: authenticate with my:ro:ut:er:sm:ac
Jan 31 13:26:40 x230 kernel: wlp3s0: send auth to my:ro:ut:er:sm:ac (try 1/3)
Jan 31 13:26:40 x230 NetworkManager[629]: <info> [1643632000.7649] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jan 31 13:26:40 x230 wpa_supplicant[921]: wlp3s0: Trying to associate with my:ro:ut:er:sm:ac (SSID='myssid' freq=5180 MHz)
Jan 31 13:26:40 x230 NetworkManager[629]: <info> [1643632000.8613] device (wlp3s0): supplicant interface state: authenticating -> associating
Jan 31 13:26:40 x230 kernel: wlp3s0: authenticated
Jan 31 13:26:40 x230 kernel: wlp3s0: associate with my:ro:ut:er:sm:ac (try 1/3)
Jan 31 13:26:40 x230 kernel: wlp3s0: RX AssocResp from my:ro:ut:er:sm:ac (capab=0x1511 status=40 aid=0)
Jan 31 13:26:40 x230 kernel: wlp3s0: my:ro:ut:er:sm:ac denied association (code=40)

Simular issue on 2.4GHz:

Jan 31 18:35:17 x230 wpa_supplicant[921]: wlp3s0: Trying to associate with my:ro:ut:er:sm:ac (SSID='myssid' freq=2462 MHz)
Jan 31 18:35:17 x230 NetworkManager[44085]: <info> [1643650517.3063] device (wlp3s0): supplicant interface state: authenticating -> associating
Jan 31 18:35:17 x230 kernel: wlp3s0: authenticated
Jan 31 18:35:17 x230 kernel: wlp3s0: associate with my:ro:ut:er:sm:ac (try 1/3)
Jan 31 18:35:17 x230 kernel: wlp3s0: RX AssocResp from my:ro:ut:er:sm:ac (capab=0x1431 status=0 aid=2)
Jan 31 18:35:17 x230 kernel: wlp3s0: associated
Jan 31 18:35:17 x230 wpa_supplicant[921]: wlp3s0: Associated with my:ro:ut:er:sm:ac
Jan 31 18:35:17 x230 wpa_supplicant[921]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 31 18:35:17 x230 wpa_supplicant[921]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Jan 31 18:35:17 x230 NetworkManager[44085]: <info> [1643650517.3413] device (wlp3s0): supplicant interface state: associating -> 4way_handshake
Jan 31 18:35:17 x230 wpa_supplicant[921]: nl80211: kernel reports: key setting validation failed
Jan 31 18:35:17 x230 wpa_supplicant[921]: wlp3s0: WPA: Failed to configure IGTK to the driver
Jan 31 18:35:17 x230 wpa_supplicant[921]: wlp3s0: RSN: Failed to configure IGTK
Jan 31 18:35:17 x230 kernel: wlp3s0: deauthenticating from my:ro:ut:er:sm:ac by local choice (Reason: 1=UNSPECIFIED)

Strangely, the other wifi network spanned by my router was working fine:

Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: SME: Trying to authenticate with my:ro:ut:er:sm:ac (SSID='myssid_gast' freq=5180 MHz)
Jan 31 13:26:57 x230 kernel: wlp3s0: authenticate with my:ro:ut:er:sm:ac
Jan 31 13:26:57 x230 kernel: wlp3s0: send auth to my:ro:ut:er:sm:ac (try 1/3)
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.5793] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jan 31 13:26:57 x230 kernel: wlp3s0: authenticated
Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: Trying to associate with my:ro:ut:er:sm:ac (SSID='myssid_gast' freq=5180 MHz)
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.6090] device (wlp3s0): supplicant interface state: authenticating -> associating
Jan 31 13:26:57 x230 kernel: wlp3s0: associate with my:ro:ut:er:sm:ac (try 1/3)
Jan 31 13:26:57 x230 kernel: wlp3s0: RX AssocResp from my:ro:ut:er:sm:ac (capab=0x1511 status=0 aid=1)
Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: Associated with my:ro:ut:er:sm:ac
Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Jan 31 13:26:57 x230 kernel: wlp3s0: associated
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.6408] device (wlp3s0): supplicant interface state: associating -> 4way_handshake
Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: WPA: Key negotiation completed with my:ro:ut:er:sm:ac [PTK=CCMP GTK=CCMP]
Jan 31 13:26:57 x230 wpa_supplicant[921]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to my:ro:ut:er:sm:ac completed [id=0 id_str=]
Jan 31 13:26:57 x230 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.6879] device (wlp3s0): supplicant interface state: 4way_handshake -> completed
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.6879] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "myssid_gast"
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.6882] device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.6886] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 31 13:26:57 x230 kernel: wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by my:ro:ut:er:sm:ac
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.7110] dhcp4 (wlp3s0): state changed unknown -> bound, address=192.168.179.30
Jan 31 13:26:57 x230 avahi-daemon[626]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.179.30.
Jan 31 13:26:57 x230 avahi-daemon[626]: New relevant interface wlp3s0.IPv4 for mDNS.
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.7136] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 31 13:26:57 x230 avahi-daemon[626]: Registering new address record for 192.168.179.30 on wlp3s0.IPv4.
Jan 31 13:26:57 x230 NetworkManager[629]: <info> [1643632017.7148] policy: set 'myssid_gast' (wlp3s0) as default for IPv4 routing and DNS

Deleting NetworkManager settings didn't help. LTS kernel also had the same problem.

Following the trouble shooting guide on https://wiki.archlinux.org/title/Networ … leshooting I finally got it working by reconfiguring my router from WPA+WPA2 to WPA2-only. WPA2+WPA3 doesn't work either.

Hope that helps.

an_origamian · 2022-02-01 05:33:53

It should be "no" instead of "yes" above ^^^

wifi.scan-rand-mac-address=no

Thank you. Still having the problem though.

BTW: What kind of device supplies this WiFI and what was the maintenance?

I have tried two. The one I want to connect to is a normal WiFi access point. I also created a hotspot with my phone and was unable to connect to that.
I believe the maintenance was setting up a PDU and restricting the allowed IP addresses to below 200. I do not believe my machine had an address above that limit, but to be sure I deleted my WiFi leases and connections.

My X230 with iwlwifi (Centrino 6205 AGN) was not able to connect to my router (AVM Fritzbox 7590) anymore.

Mine is similar. The third digit is a 3, not a 0.

5c:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
        DeviceName: WLAN
        Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

-thc · 2022-02-01 10:22:48

You could try a kernel downgrade (5.16.3 or below). If the iwlwifi driver is the culprit, the problem should vanish.

seth · 2022-02-01 12:20:26

OP wrote:

The WiFi went down for some maintenance, and when it came back up I was unable to connect. The only change that I know of is that some addresses are now restricted.

If they maintained wpa3 into it, see https://wiki.archlinux.org/title/wpa_su … ess_points and/or consider https://wiki.archlinux.org/title/Networ … Fi_backend

go2sh · 2022-02-17 20:00:33

@fred777

I have the same problem and I found the following post on the wpa_supplicant mailing list:
http://lists.infradead.org/pipermail/ho … 40216.html

Try to downgrade to 2.9

loqs · 2022-02-17 20:43:11

See https://lists.infradead.org/pipermail/h … 40209.html upstream contends the routers are out of spec and waiting to see if the router vendors fix it.

noonian · 2022-02-18 20:32:38

Same problem with Centrino Advanced-N 6235 and Fritz!box 7530. Weirdly enough, the same APs guest wifi still worked.

Downgrading to wpa_supplicant 2.9 helped, thanks.

Arch Linux

#1 2022-01-29 20:21:24

Unable to connect to WiFi

#2 2022-01-29 21:56:12

Re: Unable to connect to WiFi

#3 2022-01-29 22:03:25

Re: Unable to connect to WiFi

#4 2022-01-30 00:16:29

Re: Unable to connect to WiFi

#5 2022-01-30 08:49:11

Re: Unable to connect to WiFi

#6 2022-01-30 08:55:59

Re: Unable to connect to WiFi

#7 2022-01-31 18:08:50

Re: Unable to connect to WiFi

#8 2022-02-01 05:33:53

Re: Unable to connect to WiFi

#9 2022-02-01 10:22:48

Re: Unable to connect to WiFi

#10 2022-02-01 12:20:26

Re: Unable to connect to WiFi

#11 2022-02-17 20:00:33

Re: Unable to connect to WiFi

#12 2022-02-17 20:43:11

Re: Unable to connect to WiFi

#13 2022-02-18 20:32:38

Re: Unable to connect to WiFi

Board footer