You are not logged in.

Pages: 1

#1 2025-10-06 19:36:53

xXx_meowmeow_xXx
Member
Registered: 2025-10-06
Posts: 3

Particular WiFi AP constantly says that correct password is incorrect

This only happens with my new home WiFi AP. It works fine on Windows(dualboot setup), and I haven't observed this behaviour with any other AP on Arch. It keeps asking me for a password, and even when I give a correct password, it will ask for a password again. Also sometimes it will randomly disconnect and ask for a password. This is the output of 

sudo wpa_supplicant -i wlp4s0 -c /etc/wpa_supplicant/example.conf
wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
wlp4s0: Trying to associate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
wlp4s0: Associated with ac:22:05:5b:f1:9c
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=ac:22:05:5b:f1:9c reason=15
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=1 duration=10 reason=WRONG_KEY
wlp4s0: Added BSSID ac:22:05:5b:f1:9c into ignore list, ignoring for 10 seconds
wlp4s0: BSSID ac:22:05:5b:f1:9c ignore list count incremented to 2, ignoring for 10 seconds
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=2472 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=2472 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=2472 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=2472 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="Ziggo79FE5C9"
wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
wlp4s0: Trying to associate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
wlp4s0: Associated with ac:22:05:5b:f1:9c
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=ac:22:05:5b:f1:9c reason=15
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=2 duration=29 reason=WRONG_KEY
wlp4s0: BSSID ac:22:05:5b:f1:9c ignore list count incremented to 3, ignoring for 60 seconds
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=2472 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=2472 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=2472 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=2472 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5200 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5200 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5200 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5200 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="Ziggo79FE5C9"
wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:a5 (SSID='Ziggo79FE5C9' freq=2462 MHz)
wlp4s0: Trying to associate with ac:22:05:5b:f1:a5 (SSID='Ziggo79FE5C9' freq=2462 MHz)
wlp4s0: Associated with ac:22:05:5b:f1:a5
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: WPA: Key negotiation completed with ac:22:05:5b:f1:a5 [PTK=CCMP GTK=CCMP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to ac:22:05:5b:f1:a5 completed [id=0 id_str=]

I guess it demonstrates the problem, as initially 4 way handshake failed, but then it successfully connected to an AP. I'm sure the password is correct.

Offline

#2 2025-10-06 20:57:05

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,879

Re: Particular WiFi AP constantly says that correct password is incorrect

wlp4s0: CTRL-EVENT-DISCONNECTED bssid=ac:22:05:5b:f1:9c reason=15

reason=15 "4-Way handshake timeout"

works fine on Windows(dualboot setup)

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

In doubt then also try to reboot the AP.
nb. the same SSID seems to connect to a 5GHz and a 2.4GHz AP and at the end you seem to be connecting to the 2.4GHz AP?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2025-10-07 17:58:23

xXx_meowmeow_xXx
Member
Registered: 2025-10-06
Posts: 3

Re: Particular WiFi AP constantly says that correct password is incorrect

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!)

 powercfg /H off

This didn't work.

the same SSID seems to connect to a 5GHz and a 2.4GHz AP and at the end you seem to be connecting to the 2.4GHz AP?

Sometimes it connects to 5GHz, sometimes to 2.4GHz. If I keep trying to do that with NetworkManager GUI, then, after getting a lot of incorrect password prompts, it eventually will connect me.

sudo nmcli connection delete SSID
sudo nmcli d wifi connect SSID password pass

This also will work just as the GUI method, the only way to connect to AP would be to try that multiple times. I can't really restart an AP, but it works fine with Windows and my phone.

Offline

#4 2025-10-07 19:25:34

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,879

Re: Particular WiFi AP constantly says that correct password is incorrect

This didn't work.

What didn't work? How? Where did you run that?
You're supposed to disable the fast start feature (in windows) and then reboot both OS twice (seriously) - maybe explicitly disconnect from the AP on windows first.
This is a mandatory step regardless of anything else - you cannot run two OS at the same time (what this amounts to otherwise)

Can you please post the journal covering the "random" connection successes?
Try to explicitly connect to the 2.4GHz AP via its BSSID (ac:22:05:5b:f1:a5)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 Yesterday 18:34:37

xXx_meowmeow_xXx
Member
Registered: 2025-10-06
Posts: 3

Re: Particular WiFi AP constantly says that correct password is incorrect

What didn't work? How? Where did you run that?

From Command Prompt as administrator. I think after 4 days of me using both OSes I rebooted and powered them down much more than twice.

I believe this journal(reverse) will cover two 5 GHz connection tries, with only one successful one

Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0096] device (wlp4s0): Activation: successful, device activated.
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0092] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0089] device (wlp4s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0087] device (wlp4s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Oct 11 19:05:53 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 19:05:52 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9830] device (wlp4s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set DNS server list to: 213.46.228.196, 62.179.104.196
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set default route setting: yes
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set search domain list to: home
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9771] policy: set 'Ziggo79FE5C9' (wlp4s0) as default for IPv4 routing and DNS
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9715] dhcp4 (wlp4s0): state changed new lease, address=192.168.178.179
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.8157] dhcp4 (wlp4s0): state changed new lease, address=192.168.178.179, acd pending
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6234] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6231] device (wlp4s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6217] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> completed
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6217] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to >
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6216] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to ac:22:05:5b:f1:9c completed [id=0 id_str=]
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: WPA: Key negotiation completed with ac:22:05:5b:f1:9c [PTK=CCMP GTK=CCMP]
Oct 11 19:05:52 archlinux kernel: wlp4s0: Limiting TX power to 14 (17 - 3) dBm as advertised by ac:22:05:5b:f1:9c
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.5561] device (p2p-dev-wlp4s0): supplicant management interface state: associating -> 4way_handshake
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.5561] device (wlp4s0): supplicant interface state: associating -> 4way_handshake
Oct 11 19:05:52 archlinux kernel: wlp4s0: associated
Oct 11 19:06:04 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 19:05:58 archlinux ntpd[974]: new interface(s) found: waking up resolver
Oct 11 19:05:58 archlinux ntpd[974]: Listen normally on 6 wlp4s0 [fe80::9c3f:54c8:ecdf:4035%3]:123
Oct 11 19:05:58 archlinux ntpd[974]: Listen normally on 5 wlp4s0 [2001:1c00:8a00:1b00:af94:800b:6a3b:1e93]:123
Oct 11 19:05:58 archlinux ntpd[974]: Listen normally on 4 wlp4s0 192.168.178.179:123
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=585000
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:54 archlinux NetworkManager[886]: <info>  [1760202354.1647] dhcp6 (wlp4s0): state changed new lease
Oct 11 19:05:54 archlinux systemd-resolved[880]: wlp4s0: Bus client set DNS server list to: 213.46.228.196, 62.179.104.196, 2001:b88:1002::10, 2001:b88:1202::10, 2001>
Oct 11 19:05:54 archlinux NetworkManager[886]: <info>  [1760202354.1458] policy: set 'Ziggo79FE5C9' (wlp4s0) as default for IPv6 routing and DNS
Oct 11 19:05:54 archlinux NetworkManager[886]: <info>  [1760202354.1445] dhcp6 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 19:05:53 archlinux kdeconnectd[2171]: Failed to send mDNS query: Cannot assign requested address
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.2971] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 19:05:53 archlinux kded6[1844]: Failed to notify "Created too many similar notifications in quick succession"
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0096] device (wlp4s0): Activation: successful, device activated.
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0092] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0089] device (wlp4s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0087] device (wlp4s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Oct 11 19:05:53 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 19:05:52 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9830] device (wlp4s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set DNS server list to: 213.46.228.196, 62.179.104.196
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set default route setting: yes
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set search domain list to: home
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9771] policy: set 'Ziggo79FE5C9' (wlp4s0) as default for IPv4 routing and DNS
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9715] dhcp4 (wlp4s0): state changed new lease, address=192.168.178.179
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.8157] dhcp4 (wlp4s0): state changed new lease, address=192.168.178.179, acd pending
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6234] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6231] device (wlp4s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6217] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> completed
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6217] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to >
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6216] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to ac:22:05:5b:f1:9c completed [id=0 id_str=]
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: WPA: Key negotiation completed with ac:22:05:5b:f1:9c [PTK=CCMP GTK=CCMP]
Oct 11 19:05:52 archlinux kernel: wlp4s0: Limiting TX power to 14 (17 - 3) dBm as advertised by ac:22:05:5b:f1:9c
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.5561] device (p2p-dev-wlp4s0): supplicant management interface state: associating -> 4way_handshake
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.5561] device (wlp4s0): supplicant interface state: associating -> 4way_handshake
Oct 11 19:05:52 archlinux kernel: wlp4s0: associated
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Associated with ac:22:05:5b:f1:9c
Oct 11 19:05:52 archlinux kernel: wlp4s0: RX AssocResp from ac:22:05:5b:f1:9c (capab=0x511 status=0 aid=4)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:52 archlinux kernel: wlp4s0: associate with ac:22:05:5b:f1:9c (try 1/3)
Oct 11 19:05:52 archlinux kernel: wlp4s0: authenticated
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4570] device (p2p-dev-wlp4s0): supplicant management interface state: authenticating -> associating
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4570] device (wlp4s0): supplicant interface state: authenticating -> associating
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Trying to associate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4547] device (p2p-dev-wlp4s0): supplicant management interface state: inactive -> authenticating
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4547] device (wlp4s0): supplicant interface state: inactive -> authenticating
Oct 11 19:05:52 archlinux kernel: wlp4s0: send auth to ac:22:05:5b:f1:9c (try 1/3)
Oct 11 19:05:52 archlinux kernel: wlp4s0: authenticate with ac:22:05:5b:f1:9c (local address=e8:65:38:eb:3c:89)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Removed BSSID ac:22:05:5b:f1:9c from ignore list (clear)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'psk' value '<hidden>'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'auth_alg' value 'OPEN'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'scan_ssid' value '1'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'ssid' value 'Ziggo79FE5C9'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] device (wlp4s0): Activation: (wifi) connection 'Ziggo79FE5C9' has security, and secrets exist>
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3846] device (wlp4s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3845] device (wlp4s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Oct 11 19:05:51 archlinux NetworkManager[886]: <info>  [1760202351.0031] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> inactive
Oct 11 19:05:51 archlinux NetworkManager[886]: <info>  [1760202351.0031] device (wlp4s0): supplicant interface state: disconnected -> inactive
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9374] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> disconnected
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9372] device (wlp4s0): state change: config -> need-auth (reason 'supplicant-disconnect', managed-t>
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9372] device (wlp4s0): Activation: (wifi) disconnected during association, asking for new key
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9371] device (wlp4s0): supplicant interface state: 4way_handshake -> disconnected
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=2 duration=20 reason=CONN_FAILED
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: BSSID ac:22:05:5b:f1:9c ignore list count incremented to 2, ignoring for 10 seconds
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: Added BSSID ac:22:05:5b:f1:9c into ignore list, ignoring for 10 seconds
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=1 duration=10 reason=WRONG_KEY
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=ac:22:05:5b:f1:9c reason=15
Oct 11 19:06:04 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 19:05:58 archlinux ntpd[974]: new interface(s) found: waking up resolver
Oct 11 19:05:58 archlinux ntpd[974]: Listen normally on 6 wlp4s0 [fe80::9c3f:54c8:ecdf:4035%3]:123
Oct 11 19:05:58 archlinux ntpd[974]: Listen normally on 5 wlp4s0 [2001:1c00:8a00:1b00:af94:800b:6a3b:1e93]:123
Oct 11 19:05:58 archlinux ntpd[974]: Listen normally on 4 wlp4s0 192.168.178.179:123
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=585000
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
Oct 11 19:05:55 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:54 archlinux NetworkManager[886]: <info>  [1760202354.1647] dhcp6 (wlp4s0): state changed new lease
Oct 11 19:05:54 archlinux systemd-resolved[880]: wlp4s0: Bus client set DNS server list to: 213.46.228.196, 62.179.104.196, 2001:b88:1002::10, 2001:b88:1202::10, 2001>
Oct 11 19:05:54 archlinux NetworkManager[886]: <info>  [1760202354.1458] policy: set 'Ziggo79FE5C9' (wlp4s0) as default for IPv6 routing and DNS
Oct 11 19:05:54 archlinux NetworkManager[886]: <info>  [1760202354.1445] dhcp6 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 19:05:53 archlinux kdeconnectd[2171]: Failed to send mDNS query: Cannot assign requested address
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.2971] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 19:05:53 archlinux kded6[1844]: Failed to notify "Created too many similar notifications in quick succession"
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0096] device (wlp4s0): Activation: successful, device activated.
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0092] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0089] device (wlp4s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Oct 11 19:05:53 archlinux NetworkManager[886]: <info>  [1760202353.0087] device (wlp4s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Oct 11 19:05:53 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 19:05:52 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9830] device (wlp4s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set DNS server list to: 213.46.228.196, 62.179.104.196
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set default route setting: yes
Oct 11 19:05:52 archlinux systemd-resolved[880]: wlp4s0: Bus client set search domain list to: home
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9771] policy: set 'Ziggo79FE5C9' (wlp4s0) as default for IPv4 routing and DNS
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.9715] dhcp4 (wlp4s0): state changed new lease, address=192.168.178.179
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.8157] dhcp4 (wlp4s0): state changed new lease, address=192.168.178.179, acd pending
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6234] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6231] device (wlp4s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6217] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> completed
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6217] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to >
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.6216] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to ac:22:05:5b:f1:9c completed [id=0 id_str=]
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: WPA: Key negotiation completed with ac:22:05:5b:f1:9c [PTK=CCMP GTK=CCMP]
Oct 11 19:05:52 archlinux kernel: wlp4s0: Limiting TX power to 14 (17 - 3) dBm as advertised by ac:22:05:5b:f1:9c
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.5561] device (p2p-dev-wlp4s0): supplicant management interface state: associating -> 4way_handshake
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.5561] device (wlp4s0): supplicant interface state: associating -> 4way_handshake
Oct 11 19:05:52 archlinux kernel: wlp4s0: associated
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Associated with ac:22:05:5b:f1:9c
Oct 11 19:05:52 archlinux kernel: wlp4s0: RX AssocResp from ac:22:05:5b:f1:9c (capab=0x511 status=0 aid=4)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 11 19:05:52 archlinux kernel: wlp4s0: associate with ac:22:05:5b:f1:9c (try 1/3)
Oct 11 19:05:52 archlinux kernel: wlp4s0: authenticated
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4570] device (p2p-dev-wlp4s0): supplicant management interface state: authenticating -> associating
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4570] device (wlp4s0): supplicant interface state: authenticating -> associating
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Trying to associate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4547] device (p2p-dev-wlp4s0): supplicant management interface state: inactive -> authenticating
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.4547] device (wlp4s0): supplicant interface state: inactive -> authenticating
Oct 11 19:05:52 archlinux kernel: wlp4s0: send auth to ac:22:05:5b:f1:9c (try 1/3)
Oct 11 19:05:52 archlinux kernel: wlp4s0: authenticate with ac:22:05:5b:f1:9c (local address=e8:65:38:eb:3c:89)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Removed BSSID ac:22:05:5b:f1:9c from ignore list (clear)
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'psk' value '<hidden>'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'auth_alg' value 'OPEN'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'scan_ssid' value '1'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] Config: added 'ssid' value 'Ziggo79FE5C9'
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3848] device (wlp4s0): Activation: (wifi) connection 'Ziggo79FE5C9' has security, and secrets exist>
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3846] device (wlp4s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 11 19:05:52 archlinux NetworkManager[886]: <info>  [1760202352.3845] device (wlp4s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Oct 11 19:05:51 archlinux NetworkManager[886]: <info>  [1760202351.0031] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> inactive
Oct 11 19:05:51 archlinux NetworkManager[886]: <info>  [1760202351.0031] device (wlp4s0): supplicant interface state: disconnected -> inactive
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9374] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> disconnected
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9372] device (wlp4s0): state change: config -> need-auth (reason 'supplicant-disconnect', managed-t>
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9372] device (wlp4s0): Activation: (wifi) disconnected during association, asking for new key
Oct 11 19:05:50 archlinux NetworkManager[886]: <info>  [1760202350.9371] device (wlp4s0): supplicant interface state: 4way_handshake -> disconnected

Try to explicitly connect to the 2.4GHz AP via its BSSID (ac:22:05:5b:f1:a5)

How should I do that?

Offline

#6 Yesterday 21:03:34

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,879

Re: Particular WiFi AP constantly says that correct password is incorrect

How should I do that?

Either edit the conneciton profile and replace the SSID w/ the BSSID or remove the connection profile and create a new one for the BSSID instead of the BSSID.
nmcli accepts either and in your GUI you'll have to look around (or in doubt assume that it likewise will treat them as equal)

Please don't use -r and under no circumstances copy and paste out of the pager - not only does it truncate lines, but also it seems some lines are duplicated in your post and I cannot tell whether that's actually a glitch in the journal or courtesy of your mouse selection.
But I'd say 

Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Trying to associate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: SME: Trying to authenticate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)
Oct 11 19:05:52 archlinux wpa_supplicant[951]: wlp4s0: Trying to associate with ac:22:05:5b:f1:9c (SSID='Ziggo79FE5C9' freq=5220 MHz)

are probably the same event and it also was successful after

Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=1 duration=10 reason=WRONG_KEY

and the only possible context to that is 

Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=ac:22:05:5b:f1:9c reason=15
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=1 duration=10 reason=WRONG_KEY
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: Added BSSID ac:22:05:5b:f1:9c into ignore list, ignoring for 10 seconds
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: BSSID ac:22:05:5b:f1:9c ignore list count incremented to 2, ignoring for 10 seconds
Oct 11 19:05:50 archlinux wpa_supplicant[951]: wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Ziggo79FE5C9" auth_failures=2 duration=20 reason=CONN_FAILED

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB