netctl: unexpected authentication state: alg 57980 (expected 0) tra...

cfr · 2026-10-05 01:10:31

I use (or have been using) `netctl` to manage internet connections. Sometimes I have problems with name resolution, but usually that's all.

I was lazy and did not update Arch for a while, so I got a lot of updates last night. After rebooting, I can't get an internet connection (at least wifi) with `netctl`, though I can connect manually with `ip`, `wpa_supplicant` and `dhcpd`. I have not touched the `netctl` configuration files and I'm trying to connect to a wifi LAN I control, so I know that hasn't changed either. Since I can bring up a connection manually, it doesn't look like hardware, so I'm guessing the problem is something to do with `netctl` itself.

I had some difficulty stopping `netctl` to setup the manual connection, because `systemd` `.slice`s remained even after `stop`ping the services. I don't remember seeing these before, but perhaps I just failed to look. In the journal these appear early

Hyd 04 21:01:52 mycomputer systemd[1]: Created slice Slice /system/netctl-auto.
Hyd 04 21:01:52 mycomputer systemd[1]: Created slice Slice /system/netctl-ifplugd.

But I doubt that is relevant. The most relevant line in the journal may be

Hyd 04 21:46:40 mycomputer kernel: wlan0: 04:95:e6:63:96:91 unexpected authentication state: alg 57980 (expected 0) transact 2 (expected 2)

but I am not really sure I even understand the sequence since I seem to authenticate OK during startup, but with name resolution failing. Then later when I try to restart `netctl`, authentication fails. So, rather than guess what is relevant, I posted the journal to https://paste.c-net.org/WelcomeApproval.

Non-working `netctl` config in `/etc/netctl/networkdienw`:

Description='networkdienw'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='networkdienw'
Key=\"XXX

Working `wpa_supplicant.conf`:

network={
        ssid="networkdienw"
        #psk="pppp"
        psk=XXX
}

PS Despite having just logged in, when I try to submit, I'm told I'm not logged in ...

seth · 2026-10-05 07:30:55

Hyd 04 21:01:59 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:8c (local address=f4:96:34:dc:aa:f5)
Hyd 04 21:02:01 mycomputer dhcpcd[1141]: wlan0: rebinding lease of 192.168.5.248
Hyd 04 21:02:09 mycomputer dhcpcd[1141]: wlan0: leased 192.168.5.248 for 86400 seconds
Hyd 04 21:02:13 mycomputer login[956]: LOGIN ON tty1 BY dienw
…
Hyd 04 21:37:45 mycomputer kernel: wlan0: disassociated from 04:95:e6:63:96:8c (Reason: 1=UNSPECIFIED)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Hyd 04 21:37:47 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:81 (local address=f4:96:34:dc:aa:f5)
Hyd 04 21:37:47 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:81 (try 1/3)
Hyd 04 21:37:47 mycomputer kernel: wlan0: 04:95:e6:63:96:81 unexpected authentication state: alg 1 (expected 0) transact 2 (expected 2)
Hyd 04 21:37:47 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:81 (try 2/3)
Hyd 04 21:37:47 mycomputer kernel: wlan0: 04:95:e6:63:96:81 unexpected authentication state: alg 49920 (expected 0) transact 2 (expected 2)
Hyd 04 21:37:47 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:81 (try 3/3)
Hyd 04 21:37:47 mycomputer kernel: wlan0: authentication with 04:95:e6:63:96:81 timed out

You get a lease but then disasociated after ~35 minutes, then shit hits the fan

Hyd 04 21:46:35 mycomputer sudo[3874]:   dienw : TTY=pts/0 ; PWD=/home/dienw ; USER=root ; COMMAND=/usr/bin/systemctl restart netctl-auto@wlan0.service
Hyd 04 21:46:40 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:91 (local address=f4:96:34:dc:aa:f5)
Hyd 04 21:46:40 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 1/3)
Hyd 04 21:46:40 mycomputer kernel: wlan0: 04:95:e6:63:96:91 unexpected authentication state: alg 57980 (expected 0) transact 2 (expected 2)
Hyd 04 21:46:40 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 2/3)
Hyd 04 21:46:40 mycomputer kernel: wlan0: 04:95:e6:63:96:91 denied authentication (status 17)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You could utilize "Security=wpa-configsection", https://man.archlinux.org/man/netctl.profile.5.en but I assume the router is WPA2/WPA3 ?
Can you restrict that to WPA2 for a test?

-thc · 2026-10-05 07:39:42

Why are there 3 different BSSID-MACs involved?

Associated and disassociated from "...:8c"
Timed out with "...:81"
Denied by "...:91"

2,4/5/6 GHz issue?

Last edited by -thc (2026-10-05 07:41:00)

seth · 2026-10-05 07:55:05

Hyd 04 21:01:59 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:8c (local address=f4:96:34:dc:aa:f5)
Hyd 04 21:01:59 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:8c (try 1/3)
Hyd 04 21:01:59 mycomputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 04 21:01:59 mycomputer kernel: wlan0: RX AssocResp from 04:95:e6:63:96:8c (capab=0x411 status=0 aid=3)
Hyd 04 21:01:59 mycomputer kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 04:95:e6:63:96:8c
Hyd 04 21:37:45 mycomputer kernel: wlan0: disassociated from 04:95:e6:63:96:8c (Reason: 1=UNSPECIFIED)
Hyd 04 21:37:47 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:81 (local address=f4:96:34:dc:aa:f5)
Hyd 04 21:37:47 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:81 (try 1/3)
Hyd 04 21:37:47 mycomputer kernel: wlan0: 04:95:e6:63:96:81 unexpected authentication state: alg 1 (expected 0) transact 2 (expected 2)
Hyd 04 21:37:47 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:81 (try 2/3)
Hyd 04 21:37:47 mycomputer kernel: wlan0: 04:95:e6:63:96:81 unexpected authentication state: alg 49920 (expected 0) transact 2 (expected 2)
Hyd 04 21:37:47 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:81 (try 3/3)
Hyd 04 21:37:47 mycomputer kernel: wlan0: authentication with 04:95:e6:63:96:81 timed out
Hyd 04 21:46:40 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:91 (local address=f4:96:34:dc:aa:f5)
Hyd 04 21:46:40 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 1/3)
Hyd 04 21:46:40 mycomputer kernel: wlan0: 04:95:e6:63:96:91 unexpected authentication state: alg 57980 (expected 0) transact 2 (expected 2)
Hyd 04 21:46:40 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 2/3)
Hyd 04 21:46:40 mycomputer kernel: wlan0: 04:95:e6:63:96:91 denied authentication (status 17)
Hyd 04 22:30:05 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:91 (local address=f4:96:34:dc:aa:f5)
Hyd 04 22:30:05 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 1/3)
Hyd 04 22:30:05 mycomputer kernel: wlan0: 04:95:e6:63:96:91 unexpected authentication state: alg 34396 (expected 0) transact 2 (expected 2)
Hyd 04 22:30:05 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 2/3)
Hyd 04 22:30:05 mycomputer kernel: wlan0: 04:95:e6:63:96:91 unexpected authentication state: alg 40656 (expected 0) transact 2 (expected 2)
Hyd 04 22:30:05 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 3/3)
Hyd 04 22:30:05 mycomputer kernel: wlan0: 04:95:e6:63:96:91 unexpected authentication state: alg 62076 (expected 0) transact 2 (expected 2)
Hyd 04 22:30:05 mycomputer kernel: wlan0: authentication with 04:95:e6:63:96:91 timed out
Hyd 04 23:47:51 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:8c (local address=f4:96:34:dc:aa:f5)
Hyd 04 23:47:51 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:8c (try 1/3)
Hyd 04 23:47:51 mycomputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 04 23:47:51 mycomputer kernel: wlan0: RX AssocResp from 04:95:e6:63:96:8c (capab=0x411 status=0 aid=3)
Hyd 04 23:47:51 mycomputer kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 04:95:e6:63:96:8c
Hyd 04 23:51:47 mycomputer kernel: wlan0: deauthenticating from 04:95:e6:63:96:8c by local choice (Reason: 3=DEAUTH_LEAVING)
Hyd 04 23:53:10 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:89 (local address=f4:96:34:dc:aa:f5)
Hyd 04 23:53:10 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 1/3)
Hyd 04 23:53:10 mycomputer kernel: wlan0: 04:95:e6:63:96:89 unexpected authentication state: alg 436 (expected 0) transact 2 (expected 2)
Hyd 04 23:53:10 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 2/3)
Hyd 04 23:53:10 mycomputer kernel: wlan0: 04:95:e6:63:96:89 unexpected authentication state: alg 1548 (expected 0) transact 2 (expected 2)
Hyd 04 23:53:10 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 3/3)
Hyd 04 23:53:10 mycomputer kernel: wlan0: 04:95:e6:63:96:89 unexpected authentication state: alg 55676 (expected 0) transact 2 (expected 2)
Hyd 04 23:53:10 mycomputer kernel: wlan0: authentication with 04:95:e6:63:96:89 timed out
Hyd 05 00:01:17 mycomputer kernel: wlan0: authenticate with 04:95:e6:63:96:8c (local address=f4:96:34:dc:aa:f5)
Hyd 05 00:01:17 mycomputer kernel: wlan0: send auth to 04:95:e6:63:96:8c (try 1/3)
Hyd 05 00:01:17 mycomputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 05 00:01:17 mycomputer kernel: wlan0: RX AssocResp from 04:95:e6:63:96:8c (capab=0x411 status=0 aid=3)
Hyd 05 00:01:17 mycomputer kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 04:95:e6:63:96:8c

Indeed and only 04:95:e6:63:96:8c seems to succeed no matter what.
=> Configure the BSSID?

cfr · 2026-10-05 23:20:53

Thanks very much for helping.

seth wrote:

You could utilize "Security=wpa-configsection", https://man.archlinux.org/man/netctl.profile.5.en but I assume the router is WPA2/WPA3 ?
Can you restrict that to WPA2 for a test?

Do you mean in netctl? I don't think there's anything I can set on the router side.

-thc wrote:

Why are there 3 different BSSID-MACs involved?
Associated and disassociated from "...:8c"
Timed out with "...:81"
Denied by "...:91"
2,4/5/6 GHz issue?

There are 3 access points creating the LAN b/c otherwise the connections are patchy.

8c is the 5G wifi address (not a MAC address? The settings show other values for that?) for the AP closest to the laptop.

91 is the 2.4G wifi address for the next closest.
81 is the 2.4G addr for the third (actually the first, since it is connected to the broadband router).

Each of the 3 has multiple addresses, including 2.4G and 5G.

So I assume it always prefers the closest AP, since that's the best signal (when the laptop is on my desk, at least) and it makes sense to prefer 5G, though I'm not sure why it tries 2.4G for the others and 5G for only this one.

Seth wrote:

=> Configure the BSSID?

All 3 are configured to provide a single network and the laptop is configured to connect to the configured ESSID. At least, I am on epistemically thin ground here, but that was my understanding of how the devices were meant to work?

I don't understand why authentication fails for the others, even if it makes more sense to connect to the closest?

Last edited by cfr (2026-10-05 23:22:46)

-thc · 2026-10-06 05:34:28

cfr wrote:

There are 3 access points creating the LAN b/c otherwise the connections are patchy.

That a "wireless LAN" or WiFi actually. I always cringe at that.

cfr wrote:

8c is the 5G wifi address (not a MAC address? The settings show other values for that?) for the AP closest to the laptop.

You're right - it's "BSSID" only - "MAC" is misleading here. The BSSID is created by the AP and unrelated to any MAC address.
Since the SSID "networkdienw" is configured on multiple APs the BSSID shows which one the PC has chosen.

cfr wrote:

So I assume it always prefers the closest AP, since that's the best signal (when the laptop is on my desk, at least) and it makes sense to prefer 5G, though I'm not sure why it tries 2.4G for the others and 5G for only this one.

That's part of your problem - since you let your device "choose" the AP and the frequency it may fail for several reasons.

cfr wrote:

All 3 are configured to provide a single network and the laptop is configured to connect to the configured ESSID. At least, I am on epistemically thin ground here, but that was my understanding of how the devices were meant to work?

You can do that (configure multiple APs and their two frequencies with the exact same SSID and the exact same password) - if the device fails you're non the wiser why.

What seth meant is to pin the device to a fixed BSSID (for testing).

Last edited by -thc (2026-10-06 05:35:00)

seth · 2026-10-06 07:05:41

I suspect what happens is that the connection to the "main" AP is lost but it doesn't realize that and when you want to connect to it through one of the proxies it tells you to go away because you're already connected.

Context: https://en.wikipedia.org/wiki/Wireless_ … ion_system
What does the setup/configuration exactly look like (ie. what extenders are involved and how to the communicate to each other and the router)?

cfr · 2026-10-07 08:14:23

seth wrote:

I suspect what happens is that the connection to the "main" AP is lost but it doesn't realize that and when you want to connect to it through one of the proxies it tells you to go away because you're already connected.
Context: https://en.wikipedia.org/wiki/Wireless_ … ion_system
What does the setup/configuration exactly look like (ie. what extenders are involved and how to the communicate to each other and the router)?

It's a wireless mesh with 3 nodes. One is connected to the ISP's broadband router's ethernet. The other two are at more-or-less strategic locations around the house and connect wirelessly to the gateway node. This was recommended by one of the ISP's engineers, after dutifully reporting the company's official recommendation for poor signal.

4 devices connect to the mesh wirelessly: a PC, a printer, my laptop and an Android phone. The PC (Fedora so using networkmanager) and phone don't seem to have problems. They do not support 5G. The printer does have issues at times but, honestly, I think that's the printer. It is certainly better with the mesh than it was without.

The mesh configuration is rather less informative and rather less extensive than I would like. It seems possible only through an App. Aside from naming the nodes and setting the name and password, I mostly left things default. What information would you like? I don't mind typing out whatever will help, but if there is something I can look for, that would be nice.

seth · 2026-10-07 14:12:02

You're probably also not moving printer and PC around a lot

I mostly left things default. What information would you like?

Brand/model (or a link to the manual) and can you at all affect it's behavior at all (ie. does it use WDS at all or some other bridging/forwarding technique)

It also might help to switch between clientid and duid in /etc/dhcpcd.conf (while that's a wild guess, but we don't know why the router/proxies don't like you anymore itfp)

Did you btw. test the relevance of the actually used BSSID (ie. can the manual wpa_supplicant instance connect to 04:95:e6:63:96:81 or 04:95:e6:63:96:91 and/or does netctl succeed when returning to 04:95:e6:63:96:8c)?

cfr · 2026-10-08 06:34:14

seth wrote:

You're probably also not moving printer and PC around a lot

True, but my phone moves around at least as much .

seth wrote:

Brand/model (or a link to the manual) and can you at all affect it's behavior at all (ie. does it use WDS at all or some other bridging/forwarding technique)

Tenda Mesh3f: https://www.tendacn.com/uk/product/spec … /MW33-Pack (Specifications)
https://www.tendacn.com/uk/material/sho … =MW33-Pack (Manual)

I can change
- how it gets an IP address, but the only relevant option is dynamic (I could try bridge mode, but that disables other things including dhcp)
- network name, password
- QoS mode: on/off [off]
- fast roaming: on/off [off]
- capacity-orientated mode: on/off [off - we don't have 30+ devices]
- smart assistant: run [not run - we don't have a toaster, let alone one with wifi]
- port forwarding [no rules]
- UPnP: on/off [on]
- lan: choose the address range for dhcp [192.168.5.1]
- DNS: method: automatic or manual [automatic]

Nothing else seems even vaguely relevant. Fast roaming *might* help, but it advises not to enable it if 'the' client doesn't support it and since there are a bunch of clients, I figured this might break things for those. I also wasn't actually sure what this meant. (It sounded just like ordinary wifi from the description in the app, but then they gave an iphone as an example of a device which wouldn't support it, so I guess not.)

QoS mode seems to be aimed at gaming and sounded as if it is about prioritising traffic from connected clients and not likely to affect whether they can connect in the first place.

seth wrote:

It also might help to switch between clientid and duid in /etc/dhcpcd.conf (while that's a wild guess, but we don't know why the router/proxies don't like you anymore itfp)

Thanks! I changed this and netctl connects. However, it is now trying 04:95:e6:63:96:8c first, so I am not sure whether I really solved the problem.

seth wrote:

Did you btw. test the relevance of the actually used BSSID (ie. can the manual wpa_supplicant instance connect to 04:95:e6:63:96:81 or 04:95:e6:63:96:91 and/or does netctl succeed when returning to 04:95:e6:63:96:8c)?

I read every manual page I could find on wpa_supplicant and also tried some arbitrary experiments, but I'm afraid I could not figure out how to tell wpa_supplicant to use a specific BSSID and I think I may have been going about trying wrong. I thought I needed to use that rather than SSID and I could not find a way to do that. But maybe I need to add rather than substitute the BSSID? I could not see any example or option in wpa_supplicant.conf's manual page, though.

Last edited by cfr (2026-10-08 16:09:04)

-thc · 2026-10-08 06:43:13

The log errors alone lead my to believe that something on the lower levels of WiFi together with your mesh isn't working properly.

What I would do: Remove the two WiFi extenders and analyze the stability of the PC. This would separate a fundamental WiFi problem from the mesh.

seth · 2026-10-08 08:12:31

Is the directly attached AP configured to act as bridge?

that disables other things including dhcp

You're supposed to have *one* dhcp server in the network . if the main AP is attached to some dumb modem (ie. a modem) you need/want it to provide dhcp; but if it's attached to an integrated routermodemdhcpdnsmasq™ device, you must not run a second dhcp server.

I'd also give fast roaming (likely https://en.wikipedia.org/wiki/IEEE_802.11r-2008 ) a shot, https://gitlab.archlinux.org/archlinux/ … heads#L425

Linux has a tendency to kill firefox for oom reasons

https://wiki.archlinux.org/title/Swap#Swap_file

cfr · 2026-10-08 16:16:15

-thc wrote:

The log errors alone lead my to believe that something on the lower levels of WiFi together with your mesh isn't working properly.

It is a little bit odd that other devices do not have problems, though.

-thc wrote:

What I would do: Remove the two WiFi extenders and analyze the stability of the PC. This would separate a fundamental WiFi problem from the mesh.

Thanks.
Unfortunately, the PC cannot connect without the extenders. The signal is not sufficient. (In fact, I have to have a node very close for the PC to pick up WiFi reliably, which is why there's one in that room.)

The PC is also not mine, so I do not want to mess up its network access. (At least, not in some way I can't definitely easily restore it.)

cfr · 2026-10-08 16:24:24

seth wrote:

Is the directly attached AP configured to act as bridge?
that disables other things including dhcp
You're supposed to have *one* dhcp server in the network . if the main AP is attached to some dumb modem (ie. a modem) you need/want it to provide dhcp; but if it's attached to an integrated routermodemdhcpdnsmasq™ device, you must not run a second dhcp server.

By default, the router would provide dhcp. However, it's currently configured not to provide WiFi, so I thought I wanted the mesh network to provide that. (And dynamic ip was the default and seemed to work.)

seth wrote:

I'd also give fast roaming (likely https://en.wikipedia.org/wiki/IEEE_802.11r-2008 ) a shot, https://gitlab.archlinux.org/archlinux/ … heads#L425
Thanks.
Linux has a tendency to kill firefox for oom reasons
https://wiki.archlinux.org/title/Swap#Swap_file

I have one already That reduces oom, but it still kills firefox and okular fairly often. This is my fault. I am too profligate with tabs.

However, connected now with netctl, I get a 2.4G connection rather than 5G. In the journal I then get e.g.

Hyd 08 16:52:16 MyComputer systemd[1]: Starting (Re)store the netctl profile state...
Hyd 08 16:52:16 MyComputer systemd[1]: Finished (Re)store the netctl profile state.
Hyd 08 16:52:21 MyComputer systemd[1]: Created slice Slice /system/netctl-auto.
Hyd 08 16:52:21 MyComputer systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Hyd 08 16:52:21 MyComputer netctl-auto[179305]: Included profile ...
...
Hyd 08 16:52:21 MyComputer netctl-auto[179403]: Included profile 'networddienw'
Hyd 08 16:52:21 MyComputer netctl-auto[179410]: wlan0: nl80211: kernel reports: multicast RX registrations are not supported
Hyd 08 16:52:21 MyComputer systemd[1]: Started Automatic wireless network connection using netctl profiles.
Hyd 08 16:52:25 MyComputer kernel: wlan0: authenticate with 04:95:e6:63:96:8c (local address=f4:96:34:dc:aa:f5)
Hyd 08 16:52:25 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:8c (try 1/3)
Hyd 08 16:52:25 MyComputer kernel: wlan0: authenticated
Hyd 08 16:52:25 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 08 16:52:25 MyComputer kernel: wlan0: RX AssocResp from 04:95:e6:63:96:8c (capab=0x411 status=0 aid=3)
Hyd 08 16:52:25 MyComputer kernel: wlan0: associated
Hyd 08 16:52:25 MyComputer dhcpcd[7100]: wlan0: carrier acquired
Hyd 08 16:52:25 MyComputer dhcpcd[7100]: wlan0: IAID 34:dc:aa:f5
Hyd 08 16:52:25 MyComputer dhcpcd[7100]: wlan0: adding address fe80::3343:5553:40e9:ee0e
Hyd 08 16:52:25 MyComputer kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 04:95:e6:63:96:8c
Hyd 08 16:52:25 MyComputer dhcpcd[179428]: sending commands to dhcpcd process
Hyd 08 16:52:25 MyComputer dhcpcd[7100]: control command: dhcpcd -4 -q -t 30 -K -L wlan0
Hyd 08 16:52:26 MyComputer avahi-daemon[764]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::3343:5553:40e9:ee0e.
Hyd 08 16:52:26 MyComputer avahi-daemon[764]: New relevant interface wlan0.IPv6 for mDNS.
Hyd 08 16:52:26 MyComputer avahi-daemon[764]: Registering new address record for fe80::3343:5553:40e9:ee0e on wlan0.*.
...
Hyd 08 19:02:11 MyComputer kernel: wlan0: deauthenticated from 04:95:e6:63:96:8c (Reason: 3=DEAUTH_LEAVING)
Hyd 08 19:02:11 MyComputer dhcpcd[7100]: wlan0: carrier lost
Hyd 08 19:02:11 MyComputer dhcpcd[7100]: wlan0: deleting address fe80::3343:5553:40e9:ee0e
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Withdrawing address record for fe80::3343:5553:40e9:ee0e on wlan0.
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::3343:5553:40e9:ee0e.
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Interface wlan0.IPv6 no longer relevant for mDNS.
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Withdrawing address record for 192.168.5.249 on wlan0.
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.249.
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Interface wlan0.IPv4 no longer relevant for mDNS.
Hyd 08 19:02:11 MyComputer dhcpcd[7100]: wlan0: deleting route to 192.168.5.0/24
Hyd 08 19:02:11 MyComputer dhcpcd[7100]: wlan0: deleting default route via 192.168.5.1
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: Got SIGHUP, reloading.
Hyd 08 19:02:11 MyComputer avahi-daemon[764]: No service file found in /etc/avahi/services.
Hyd 08 19:02:13 MyComputer kernel: wlan0: authenticate with 04:95:e6:63:96:89 (local address=f4:96:34:dc:aa:f5)
Hyd 08 19:02:13 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 1/3)
Hyd 08 19:02:13 MyComputer kernel: wlan0: authenticated
Hyd 08 19:02:13 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:89 (try 1/3)
Hyd 08 19:02:13 MyComputer kernel: wlan0: RX AssocResp from 04:95:e6:63:96:89 (capab=0x411 status=0 aid=3)
Hyd 08 19:02:13 MyComputer kernel: wlan0: associated
Hyd 08 19:02:13 MyComputer dhcpcd[7100]: wlan0: carrier acquired
Hyd 08 19:02:13 MyComputer dhcpcd[7100]: wlan0: IAID 34:dc:aa:f5
Hyd 08 19:02:13 MyComputer dhcpcd[7100]: wlan0: adding address fe80::3343:5553:40e9:ee0e
Hyd 08 19:02:13 MyComputer dhcpcd[182548]: sending commands to dhcpcd process
Hyd 08 19:02:13 MyComputer dhcpcd[7100]: control command: dhcpcd -4 -q -t 30 -K -L wlan0
Hyd 08 19:02:14 MyComputer dhcpcd[7100]: wlan0: rebinding lease of 192.168.5.249
Hyd 08 19:02:15 MyComputer avahi-daemon[764]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::3343:5553:40e9:ee0e.
Hyd 08 19:02:15 MyComputer avahi-daemon[764]: New relevant interface wlan0.IPv6 for mDNS.
Hyd 08 19:02:15 MyComputer avahi-daemon[764]: Registering new address record for fe80::3343:5553:40e9:ee0e on wlan0.*.
Hyd 08 19:02:15 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=124 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 08 19:02:15 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=386 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=346
Hyd 08 19:02:15 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=167 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=127
Hyd 08 19:02:15 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=386 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=346
Hyd 08 19:02:15 MyComputer dhcpcd[7100]: wlan0: soliciting an IPv6 router
Hyd 08 19:02:15 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=386 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=346
Hyd 08 19:02:16 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=368 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=328
Hyd 08 19:02:16 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=124 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 08 19:02:16 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=328 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=288
Hyd 08 19:02:17 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=368 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=328
Hyd 08 19:02:18 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:3343:5553:40e9:ee0e DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=124 TC=0 HOPLIMIT=255 FLOWLBL=39936 PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 08 19:02:19 MyComputer kernel: IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:04:95:e6:63:96:80:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=158 TOS=0x00 PREC=0x00 TTL=64 ID=29862 PROTO=UDP SPT=11113 DPT=11111 LEN=138
Hyd 08 19:02:19 MyComputer dhcpcd[7100]: wlan0: DHCP lease expired
Hyd 08 19:02:19 MyComputer dhcpcd[7100]: wlan0: soliciting a DHCP lease
Hyd 08 19:02:20 MyComputer dhcpcd[7100]: wlan0: offered 192.168.5.249 from 192.168.5.1
Hyd 08 19:02:20 MyComputer dhcpcd[7100]: wlan0: probing address 192.168.5.249/24
Hyd 08 19:02:25 MyComputer dhcpcd[7100]: wlan0: leased 192.168.5.249 for 86400 seconds
Hyd 08 19:02:25 MyComputer avahi-daemon[764]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.249.
Hyd 08 19:02:25 MyComputer avahi-daemon[764]: New relevant interface wlan0.IPv4 for mDNS.
Hyd 08 19:02:25 MyComputer avahi-daemon[764]: Registering new address record for 192.168.5.249 on wlan0.IPv4.
Hyd 08 19:02:25 MyComputer dhcpcd[7100]: wlan0: adding route to 192.168.5.0/24
Hyd 08 19:02:25 MyComputer dhcpcd[7100]: wlan0: adding default route via 192.168.5.1
Hyd 08 19:02:25 MyComputer geoclue[7840]: Failed to query location: Error resolving “api.beacondb.net”: Temporary failure in name resolution
Hyd 08 19:02:25 MyComputer avahi-daemon[764]: Got SIGHUP, reloading.
Hyd 08 19:02:25 MyComputer avahi-daemon[764]: No service file found in /etc/avahi/services.
Hyd 08 19:02:27 MyComputer kernel: IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:04:95:e6:63:96:80:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=158 TOS=0x00 PREC=0x00 TTL=64 ID=29870 PROTO=UDP SPT=11113 DPT=11111 LEN=138
Hyd 08 19:02:27 MyComputer dhcpcd[7100]: wlan0: no IPv6 Routers available

1 hour later, this fails:

Hyd 08 20:00:10 MyComputer kernel: iwlwifi 0000:03:00.0: missed beacons exceeds threshold, but receiving data. Stay connected, Expect bugs.
Hyd 08 20:00:10 MyComputer kernel: iwlwifi 0000:03:00.0: missed_beacons:19, missed_beacons_since_rx:3
Hyd 08 20:00:10 MyComputer dhcpcd[7100]: wlan0: carrier lost
Hyd 08 20:00:10 MyComputer kernel: wlan0: Connection to AP 04:95:e6:63:96:89 lost
Hyd 08 20:00:10 MyComputer dhcpcd[7100]: wlan0: deleting address fe80::3343:5553:40e9:ee0e
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Withdrawing address record for fe80::3343:5553:40e9:ee0e on wlan0.
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::3343:5553:40e9:ee0e.
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Interface wlan0.IPv6 no longer relevant for mDNS.
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Withdrawing address record for 192.168.5.249 on wlan0.
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.249.
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Interface wlan0.IPv4 no longer relevant for mDNS.
Hyd 08 20:00:10 MyComputer dhcpcd[7100]: wlan0: deleting route to 192.168.5.0/24
Hyd 08 20:00:10 MyComputer dhcpcd[7100]: wlan0: deleting default route via 192.168.5.1
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: Got SIGHUP, reloading.
Hyd 08 20:00:10 MyComputer avahi-daemon[764]: No service file found in /etc/avahi/services.
Hyd 08 20:00:13 MyComputer kernel: wlan0: authenticate with 04:95:e6:63:96:89 (local address=f4:96:34:dc:aa:f5)
Hyd 08 20:00:13 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 1/3)
Hyd 08 20:00:13 MyComputer kernel: wlan0: 04:95:e6:63:96:89 unexpected authentication state: alg 55612 (expected 0) transact 2 (expected 2)
Hyd 08 20:00:13 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 2/3)
Hyd 08 20:00:13 MyComputer kernel: wlan0: 04:95:e6:63:96:89 unexpected authentication state: alg 23100 (expected 0) transact 2 (expected 2)
Hyd 08 20:00:14 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:89 (try 3/3)
Hyd 08 20:00:14 MyComputer kernel: wlan0: 04:95:e6:63:96:89 unexpected authentication state: alg 42972 (expected 0) transact 2 (expected 2)
Hyd 08 20:00:14 MyComputer kernel: wlan0: authentication with 04:95:e6:63:96:89 timed out
Hyd 08 20:00:17 MyComputer kernel: wlan0: authenticate with 04:95:e6:63:96:91 (local address=f4:96:34:dc:aa:f5)
Hyd 08 20:00:17 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:91 (try 1/3)
Hyd 08 20:00:17 MyComputer kernel: wlan0: 04:95:e6:63:96:91 denied authentication (status 17)

Before bringing the network back up with wpa_supplicant etc., I try to make sure the status is clean:

MyComputer:~ root# systemctl stop netctl.service
MyComputer:~ root# systemctl stop netctl-ifplugd@eth0.service
MyComputer:~ root# systemctl stop netctl-auto@wlan0.service
MyComputer:~ root# ip link set dev wlan0 down
MyComputer:~ root# ps ax | grep wpa
 185625 pts/14   S+     0:00 grep wpa
MyComputer:~ root# ps ax | grep dhcpcd
   7099 ?        Ss     0:00 dhcpcd: wlan0 [ip4] [ip6]
   7100 ?        S      0:00 dhcpcd: [privileged proxy] wlan0 [ip4] [ip6]
   7101 ?        S      0:00 dhcpcd: [network proxy] wlan0 [ip4] [ip6]
   7102 ?        S      0:00 dhcpcd: [control proxy] wlan0 [ip4] [ip6]
  44051 ?        Ss     0:00 dhcpcd: eth0 [ip4] [ip6]
  44052 ?        S      0:00 dhcpcd: [privileged proxy] eth0 [ip4] [ip6]
  44053 ?        S      0:00 dhcpcd: [network proxy] eth0 [ip4] [ip6]
  44054 ?        S      0:00 dhcpcd: [control proxy] eth0 [ip4] [ip6]
  44055 ?        S      0:00 dhcpcd: [DHCP6 proxy] fe80::56e1:adff:fe7b:1b1a
  44136 ?        S      0:00 dhcpcd: [BOOTP proxy] 10.174.241.199
 176934 ?        S      0:00 dhcpcd: [BOOTP proxy] 192.168.5.248
 182657 ?        S      0:00 dhcpcd: [BOOTP proxy] 192.168.5.249
 185631 pts/14   S+     0:00 grep dhcpcd
MyComputer:~ root# dhcpcd -x
dhcpcd is not running

I don't understand why I get this response. Don't those processes show it is running? Inactivity doesn't mean it isn't running, does it?

MyComputer:~ root# ps ax | grep dhcpcd
   7099 ?        Ss     0:00 dhcpcd: wlan0 [ip4] [ip6]
   7100 ?        S      0:00 dhcpcd: [privileged proxy] wlan0 [ip4] [ip6]
   7101 ?        S      0:00 dhcpcd: [network proxy] wlan0 [ip4] [ip6]
   7102 ?        S      0:00 dhcpcd: [control proxy] wlan0 [ip4] [ip6]
  44051 ?        Ss     0:00 dhcpcd: eth0 [ip4] [ip6]
  44052 ?        S      0:00 dhcpcd: [privileged proxy] eth0 [ip4] [ip6]
  44053 ?        S      0:00 dhcpcd: [network proxy] eth0 [ip4] [ip6]
  44054 ?        S      0:00 dhcpcd: [control proxy] eth0 [ip4] [ip6]
  44055 ?        S      0:00 dhcpcd: [DHCP6 proxy] fe80::56e1:adff:fe7b:1b1a
  44136 ?        S      0:00 dhcpcd: [BOOTP proxy] 10.174.241.199
 176934 ?        S      0:00 dhcpcd: [BOOTP proxy] 192.168.5.248
 182657 ?        S      0:00 dhcpcd: [BOOTP proxy] 192.168.5.249
 185649 pts/14   S+     0:00 grep dhcpcd
MyComputer:~ root# pkill dhcpcd
MyComputer:~ root# ps ax | grep dhcpcd
 185676 pts/14   S+     0:00 grep dhcpcd

When I reconnect manually, it works fine and I am back on 5G.

# wpa_supplicant -B -c /etc/wpa_supplicant.networkdienw.conf -iwlan0
Successfully initialized wpa_supplicant
wlan0: nl80211: kernel reports: multicast RX registrations are not supported
p2p-dev-wlan0: nl80211: kernel reports: multicast RX registrations are not supported
# dhcpcd wlan0
dhcpcd-10.5.2 starting
DUID 00:01:00:01:2c:02:f6:13:f4:96:34:dc:aa:f5
wlan0: connected to Access Point: networkdienw
wlan0: IAID 34:dc:aa:f5
wlan0: adding address fe80::3343:5553:40e9:ee0e
wlan0: rebinding lease of 192.168.5.249
wlan0: soliciting an IPv6 router
wlan0: probing address 192.168.5.249/24
wlan0: leased 192.168.5.249 for 86400 seconds
wlan0: adding route to 192.168.5.0/24
wlan0: adding default route via 192.168.5.1

I do not really understand what is being done here. (Except that obviously netctl does not try to connect with the closest point.)

[I also edited my earlier reply above.]

Last edited by cfr (2026-10-08 19:41:17)

seth · 2026-10-08 19:52:32

I could not figure out how to tell wpa_supplicant to use a specific BSSID

https://man.archlinux.org/man/netctl.pr … IP_OPTIONS

AP=
The BSSID (MAC address) of the access point to connect to.

(Obviously you can't use netctl-auto)

I changed this and netctl connects. However, it is now trying 04:95:e6:63:96:8c first, so I am not sure whether I really solved the problem.

If not, try the "Fast roaming" option.

I get a 2.4G connection rather than 5G

"GHz"

Hyd 08 16:52:25 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 08 16:52:25 MyComputer kernel: wlan0: associated
Hyd 08 19:02:11 MyComputer kernel: wlan0: deauthenticated from 04:95:e6:63:96:8c (Reason: 3=DEAUTH_LEAVING)
Hyd 08 19:02:13 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:89 (try 1/3)
Hyd 08 19:02:13 MyComputer kernel: wlan0: associated

You first connected w/ 04:95:e6:63:96:8c (the one from the initial journal), then explicitly leave that ~10m later, then connect w/ 04:95:e6:63:96:89 (that one previously failed)
Neither wpa_ctl nor netctl-auto log SSIDs or frequencies, which one is the 2.4GHz one?

(nb. that neither is inherently "faster" - 2.4GHz has a wider range/is less susceptible to interference/shielding but there's typically more noise as well.
The used protocol and channel width is more important, https://en.wikipedia.org/wiki/IEEE_802.11#Generations)

cfr · Yesterday 06:59:19

seth wrote:

I could not figure out how to tell wpa_supplicant to use a specific BSSID
https://man.archlinux.org/man/netctl.pr … IP_OPTIONS
AP=
The BSSID (MAC address) of the access point to connect to.
(Obviously you can't use netctl-auto)

Sorry, I was trying to figure out how to specify the address for wpa_supplicant w/o netctl i.e. the other way around. I will try it that way.

seth wrote:

I changed this and netctl connects. However, it is now trying 04:95:e6:63:96:8c first, so I am not sure whether I really solved the problem.
If not, try the "Fast roaming" option.

Unfortunately, this did not help. Which makes sense, I suppose, since it disconnected me without the laptop moving at all.

seth wrote:

I get a 2.4G connection rather than 5G

"GHz"

Hyd 08 16:52:25 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 08 16:52:25 MyComputer kernel: wlan0: associated
Hyd 08 19:02:11 MyComputer kernel: wlan0: deauthenticated from 04:95:e6:63:96:8c (Reason: 3=DEAUTH_LEAVING)
Hyd 08 19:02:13 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:89 (try 1/3)
Hyd 08 19:02:13 MyComputer kernel: wlan0: associated

You first connected w/ 04:95:e6:63:96:8c (the one from the initial journal), then explicitly leave that ~10m later,

About 370m later. I leave to try `netctl`. The 370m are using `wpa_supplicant`. That connects me to the 5GHz address in the closest node, 04:95:e6:63:96:8c.

seth wrote:

then connect w/ 04:95:e6:63:96:89 (that one previously failed)

This is the 2.4GHz address in the closest node. This is what netctl sets up.

seth wrote:

(nb. that neither is inherently "faster" - 2.4GHz has a wider range/is less susceptible to interference/shielding but there's typically more noise as well.
The used protocol and channel width is more important, https://en.wikipedia.org/wiki/IEEE_802.11#Generations)

OK. It just seemed odd that netctl always seems to try 2.4GHz and never 5, whereas `wpa_supplicant` manually always seems to prefer 5. (I thought it was faster because that is what people have told me, but often other factors dominate. Still, it would not be a bad thing if my laptop would use 5, since most of the other devices can't and I'm assuming that makes things less cluttered. The TV uses 5, but that's downstairs. But really, it does not matter which it uses, if it works.

seth · Yesterday 13:33:19

Sorry, I was trying to figure out how to specify the address for wpa_supplicant w/o netctl i.e. the other way around. I will try it that way.

network={
        bssid=04:95:e6:63:96:8c
        #psk="pppp"
        psk=XXX
}

should™ work

It just seemed odd that netctl always seems to try 2.4GHz and never 5, whereas `wpa_supplicant` manually always seems to prefer 5.

It is odd since it's the same SSID so you'd expect only one netctl profile and wpa_supplicant on the backend choosing the AP - unless you've set one of the *Frequenc* options in the profile.
Have you checked the scan results in the relevant spots (ie. what produces the better signal and by how far)?

You can btw. impact the roaming, https://wiki.archlinux.org/title/Wpa_supplicant#Roaming but I think will have to use Security=wpa-configsection in netctl for this.

cfr · Yesterday 16:12:16

seth wrote:

I could not figure out how to tell wpa_supplicant to use a specific BSSID
https://man.archlinux.org/man/netctl.pr … IP_OPTIONS
AP=
The BSSID (MAC address) of the access point to connect to.
(Obviously you can't use netctl-auto)

So trying to connect to the 'good' address with netctl (rather than the 'bad' address without it), I get a different error, but I am not sure this isn't due to some failure on my part.

Hyd 09 16:43:11 MyComputer systemd[1]: Starting (Re)store the netctl profile state...
Hyd 09 16:43:12 MyComputer systemd[1]: Finished (Re)store the netctl profile state.
Hyd 09 16:43:56 MyComputer systemd[1]: Created slice Slice /system/netctl.
Hyd 09 16:43:56 MyComputer systemd[1]: Starting Networking for netctl profile prawf...
Hyd 09 16:43:56 MyComputer network[214229]: Starting network profile 'prawf'...
Hyd 09 16:43:56 MyComputer network[214238]: wlan0: nl80211: kernel reports: multicast RX registrations are not supported
Hyd 09 16:43:56 MyComputer avahi-daemon[764]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.249.
Hyd 09 16:43:56 MyComputer avahi-daemon[764]: New relevant interface wlan0.IPv4 for mDNS.
Hyd 09 16:43:56 MyComputer avahi-daemon[764]: Registering new address record for 192.168.5.249 on wlan0.IPv4.
Hyd 09 16:43:56 MyComputer network[214238]: p2p-dev-wlan0: nl80211: kernel reports: multicast RX registrations are not supported
Hyd 09 16:43:56 MyComputer systemd[1]: Started Networking for netctl profile prawf.
Hyd 09 16:43:56 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=104 TOS=0x00 PREC=0x00 TTL=255 ID=54262 DF PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 09 16:43:56 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=308 TOS=0x00 PREC=0x00 TTL=255 ID=54329 DF PROTO=UDP SPT=5353 DPT=5353 LEN=288
Hyd 09 16:43:56 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=147 TOS=0x00 PREC=0x00 TTL=255 ID=54348 DF PROTO=UDP SPT=5353 DPT=5353 LEN=127
Hyd 09 16:43:57 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=308 TOS=0x00 PREC=0x00 TTL=255 ID=54462 DF PROTO=UDP SPT=5353 DPT=5353 LEN=288
Hyd 09 16:43:57 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=308 TOS=0x00 PREC=0x00 TTL=255 ID=54532 DF PROTO=UDP SPT=5353 DPT=5353 LEN=288
Hyd 09 16:43:57 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=290 TOS=0x00 PREC=0x00 TTL=255 ID=54680 DF PROTO=UDP SPT=5353 DPT=5353 LEN=270
Hyd 09 16:43:57 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=104 TOS=0x00 PREC=0x00 TTL=255 ID=54717 DF PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 09 16:43:58 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=147 TOS=0x00 PREC=0x00 TTL=255 ID=54918 DF PROTO=UDP SPT=5353 DPT=5353 LEN=127
Hyd 09 16:43:58 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=290 TOS=0x00 PREC=0x00 TTL=255 ID=55361 DF PROTO=UDP SPT=5353 DPT=5353 LEN=270
Hyd 09 16:43:59 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=104 TOS=0x00 PREC=0x00 TTL=255 ID=55372 DF PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 09 16:44:00 MyComputer kernel: wlan0: authenticate with 04:95:e6:63:96:8c (local address=f4:96:34:dc:aa:f5)
Hyd 09 16:44:00 MyComputer kernel: wlan0: send auth to 04:95:e6:63:96:8c (try 1/3)
Hyd 09 16:44:00 MyComputer kernel: wlan0: authenticated
Hyd 09 16:44:00 MyComputer kernel: wlan0: associate with 04:95:e6:63:96:8c (try 1/3)
Hyd 09 16:44:00 MyComputer kernel: wlan0: RX AssocResp from 04:95:e6:63:96:8c (capab=0x411 status=0 aid=3)
Hyd 09 16:44:00 MyComputer kernel: wlan0: associated
Hyd 09 16:44:00 MyComputer kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 04:95:e6:63:96:8c
Hyd 09 16:44:06 MyComputer kernel: wlan0: deauthenticated from 04:95:e6:63:96:8c (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
Hyd 09 16:44:11 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.5.249 DST=224.0.0.251 LEN=104 TOS=0x00 PREC=0x00 TTL=255 ID=61642 DF PROTO=UDP SPT=5353 DPT=5353 LEN=84
Hyd 09 16:44:13 MyComputer network[214229]: WPA association/authentication failed for interface 'wlan0'
Hyd 09 16:44:13 MyComputer avahi-daemon[764]: Interface wlan0.IPv4 no longer relevant for mDNS.
Hyd 09 16:44:13 MyComputer avahi-daemon[764]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.249.
Hyd 09 16:44:13 MyComputer avahi-daemon[764]: Withdrawing address record for 192.168.5.249 on wlan0.
Hyd 09 16:44:13 MyComputer network[214229]: Failed to bring the network up for profile 'prawf'
Hyd 09 16:44:13 MyComputer systemd[1]: netctl@prawf.service: Main process exited, code=exited, status=1/FAILURE
Hyd 09 16:44:13 MyComputer systemd[1]: netctl@prawf.service: Failed with result 'exit-code'.
Hyd 09 16:44:13 MyComputer systemd[1]: netctl@prawf.service: Consumed 1.991s CPU time over 16.970s wall clock time, 7M memory peak.

Where /etc/netctl/prawf has

Description='Prawf'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
AP=04:95:e6:63:96:8c
Key=myunquotedkey

and myunquotedkey is the plain text version of the key I use to create the psk value for wpa_supplicant, so without the \" as I want netctl to quote the value when passing it to wpa_supplicant.

Although it says I authenticated, the handshake failure looks as if it doesn't finish authenticating?

cfr · Yesterday 16:49:29

seth wrote:

Sorry, I was trying to figure out how to specify the address for wpa_supplicant w/o netctl i.e. the other way around. I will try it that way.
network={
        bssid=04:95:e6:63:96:8c
        #psk="pppp"
        psk=XXX
}
should™ work

Thanks, but how do I create the psk with bssid rather than ssid? wpa_passphrase only seems to accept an SSID, at least according to the manual page, and it does not work to omit the SSID. Do I pass the bssid as if it was an ssid? I thought I tried that and couldn't get it to work, but I tried a number of things, so may just be confused.

seth wrote:

It just seemed odd that netctl always seems to try 2.4GHz and never 5, whereas `wpa_supplicant` manually always seems to prefer 5.
It is odd since it's the same SSID so you'd expect only one netctl profile and wpa_supplicant on the backend choosing the AP - unless you've set one of the *Frequenc* options in the profile.
Have you checked the scan results in the relevant spots (ie. what produces the better signal and by how far)?

          Cell 01 - Address: 20:B8:2B:4F:C4:43
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=35/70  Signal level=-75 dBm
                    Encryption key:on
                    ESSID:"VM4201079"
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000001f0e2cd7217
                    Extra: Last beacon: 3194ms ago
                    IE: Unknown: 0009564D34323031303739
                    IE: Unknown: 01088C129824B048606C
                    IE: Unknown: 030101
                    IE: Unknown: 07064E4C04010D14
                    IE: Unknown: 200100
                    IE: Unknown: 23021200
                    IE: Unknown: 2A0104
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 0B050000610000
                    IE: Unknown: 46057200000000
                    IE: Unknown: 3302796C
                    IE: Unknown: 33025101
                    IE: Unknown: 3B0751040B0C515354
                    IE: Unknown: 2D1AEF1917FFFFFF0000000000000000000000000000000000000000
                    IE: Unknown: 3D1601080000000000000000000000000000000000000000
                    IE: Unknown: 7F0B84000802010000C0014020
                    IE: Unknown: FF1C23050018120010222002C00F02951000CC00EAFFEAFF1A1CC7711C07
                    IE: Unknown: FF072404000135FCFF
                    IE: Unknown: FF0E260800A40820A408404308603208
                    IE: Unknown: DD7F0050F204104A0001101044000102103B000103104700100DF5E179C8513499E20177033788D28B1021000842726F6164636F6D1023000842726F6164636F6D10240006313233343536104200033236371054000800060050F20400011011000A42726F6164636F6D4150100800022008103C0001031049000600372A000120
                    IE: Unknown: DD1A00904C0418BF0CB1698A0FEAFF0000EAFF0020C0050001000000
                    IE: Unknown: DD090010180200001C0000
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00
          Cell 02 - Address: 54:1F:8D:7A:D9:64
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=27/70  Signal level=-83 dBm
                    Encryption key:on
                    ESSID:"Three_7AD964"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000480a2e7002
                    Extra: Last beacon: 3246ms ago
                    IE: Unknown: 000C54687265655F374144393634
                    IE: Unknown: 010482848B96
                    IE: Unknown: 030101
                    IE: Unknown: 050401050000
                    IE: Unknown: 0706474204010D14
                    IE: Unknown: 2A0100
                    IE: Unknown: 32080C1218243048606C
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 3B055353547D81
                    IE: Unknown: 2D1AEF0913FFFF000000000000000000000000000000000000000100
                    IE: Unknown: 3D1601050600000000000000000000000000000000000000
                    IE: Unknown: 7F0B0500000200000000004010
                    IE: Unknown: FF1A2305010082400802334C09000080C8020C00FAFFFAFF191CC771
                    IE: Unknown: FF0724F03F00A3FCFF
                    IE: Unknown: DD180050F2020101810003A4000027A4000042435E0062322F00
                    IE: Unknown: DD180050F204104A00011010440001021049000600372A000120
                    IE: Unknown: 4A0E14000A000A00C800140005001900
          Cell 03 - Address: 00:EB:D8:5E:02:16
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=27/70  Signal level=-83 dBm
                    Encryption key:on
                    ESSID:""
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000031ee8d7f1a4
                    Extra: Last beacon: 3133ms ago
                    IE: Unknown: 0000
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030101
                    IE: Unknown: 050400010000
                    IE: Unknown: 0706444520010D23
                    IE: Unknown: 200100
                    IE: Unknown: 23023F00
                    IE: Unknown: 46050200000000
                    IE: Unknown: 330A0B010203040506070809
                    IE: Unknown: 2A0104
                    IE: Unknown: 32040C183060
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 0B05060000127A
                    IE: Unknown: 2D1AEF1117FFFFFF0000000000000000000000000000001804871100
                    IE: Unknown: 3D1601050600000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: BF0C9179CA33EAFF9204EAFF9204
                    IE: Unknown: C005000000EAFF
                    IE: Unknown: 7F080000080000000000
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: DD07000C430B000000
                    IE: Unknown: DD21000CE708000000BF0CB101C0332AFF92042AFF9204C0050000002AFFC303010202
                    IE: Unknown: DD3A2F25C00100010000EBD85E02141B84FE54675142D69BE8925215B1D0D900C0A84401000000000000000000000000C0A8010200EBD85E02140000
          Cell 04 - Address: 02:EB:D8:2E:02:16
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=27/70  Signal level=-83 dBm
                    Encryption key:on
                    ESSID:"VMHaloWii"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000031ee8d6f1d6
                    Extra: Last beacon: 3189ms ago
                    IE: Unknown: 0009564D48616C6F576969
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030101
                    IE: Unknown: 2A0104
                    IE: Unknown: 32040C183060
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (2) : PSK unknown (4)
                    IE: Unknown: 2D1AEF1117FFFFFF0000000000000000000000000000001804871100
                    IE: Unknown: 3D1601050600000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F080000080000000000
                    IE: Unknown: 0B05060000127A
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: 46050200000000
                    IE: Unknown: 330A0B010203040506070809
                    IE: Unknown: 200103
                    IE: Unknown: 23023F00
                    IE: Unknown: 0706444520010D23
                    IE: Unknown: BF0C9179CA33EAFF9204EAFF9204
                    IE: Unknown: C005000000EAFF
                    IE: Unknown: DD7E0050F204104A0001101044000102103B000103104700100000000000001000000000EBD85E0214102100084D45524355535953102300044835304710240003312E3010420007312E312E312E331054000800060050F2040001101100044835304710080002228C103C0001031049000E00372A0001200106FFFFFFFFFFFF
                    IE: Unknown: 3603534802
                    IE: Unknown: DD07000C430B000000
                    IE: Unknown: DD21000CE708000000BF0CB101C0332AFF92042AFF9204C0050000002AFFC303010202
          Cell 05 - Address: 04:95:E6:63:96:89
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=69/70  Signal level=-41 dBm
                    Encryption key:on
                    ESSID:"Network Dienw"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000012e99227cf
                    Extra: Last beacon: 2999ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: Unknown: 0B0503000C0000
                    IE: Unknown: 2D1AEE191EFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1606070000000000000000000000000000000000000000
                    IE: WPA Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0600E04C020160
                    IE: Unknown: 7F080000080000000000
          Cell 06 - Address: 04:95:E6:63:96:81
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=52/70  Signal level=-58 dBm
                    Encryption key:on
                    ESSID:"Network Dienw"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000012e994793a
                    Extra: Last beacon: 3007ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: Unknown: 0B0503000C0000
                    IE: Unknown: 2D1AEE191EFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1606070000000000000000000000000000000000000000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0600E04C020160
                    IE: Unknown: 7F080000080000000000
          Cell 07 - Address: 04:95:E6:63:96:91
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=52/70  Signal level=-58 dBm
                    Encryption key:on
                    ESSID:"Network Dienw"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000012e991e914
                    Extra: Last beacon: 2985ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: Unknown: 0B0502000E0000
                    IE: Unknown: 2D1AEE191EFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1606070000000000000000000000000000000000000000
                    IE: WPA Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0600E04C020160
                    IE: Unknown: 7F080000080000000000
          Cell 08 - Address: 20:B0:01:98:D8:13
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=28/70  Signal level=-82 dBm
                    Encryption key:on
                    ESSID:"TNCAP98D813"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000cc6d83e7e35
                    Extra: Last beacon: 2749ms ago
                    IE: Unknown: 000B544E434150393844383133
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0104
                    IE: Unknown: 32040C121860
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 0B050700080000
                    IE: Unknown: 46053000000000
                    IE: Unknown: 2D1A2D0017FFFFFF0000000000000000000000000000000000000000
                    IE: Unknown: 3D160B081600000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F080500080000400040
                    IE: Unknown: DD7E0050F204104A0001101044000102103B00010310470010E0FF2CAF7EF651E5B136AC36388579711021000B546563686E69636F6C6F72102300034447411024000434323331104200093139323553414A37521054000800060050F20400011011000744474134323331100800020784103C0001031049000600372A000120
                    IE: Unknown: DD1E00904C0400BF0C1258820FEAFF0000EAFF0000C005000B000000C3020002
                    IE: Unknown: DD090010180207101C0000
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
          Cell 09 - Address: 2C:FB:0F:6F:FE:F9
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=31/70  Signal level=-79 dBm
                    Encryption key:on
                    ESSID:"VM6612826"
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000ceeb22f048
                    Extra: Last beacon: 2837ms ago
                    IE: Unknown: 0009564D36363132383236
                    IE: Unknown: 01088C129824B048606C
                    IE: Unknown: 03010B
                    IE: Unknown: 050400010401
                    IE: Unknown: 07064E4C20010D14
                    IE: Unknown: 200100
                    IE: Unknown: 23021200
                    IE: Unknown: 2A0104
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 0B0501001C0000
                    IE: Unknown: 3302510B
                    IE: Unknown: 3302732C
                    IE: Unknown: 46057200000000
                    IE: Unknown: 3B0404040B0C
                    IE: Unknown: 2D1AEF1917FFFFFF0000000000000000000000000000000000000000
                    IE: Unknown: 3D160B080400000000000000000000000000000000000000
                    IE: Unknown: 7F0B84000802010000C0014020
                    IE: Unknown: FF1C23050018120010222002C00F02951000CC00EAFFEAFF1A1CC7711C07
                    IE: Unknown: FF072404000122FCFF
                    IE: Unknown: FF0E260800A40820A408404308603208
                    IE: Unknown: DD1D0050F204104A0001101044000102103C0001031049000600372A000120
                    IE: Unknown: DD1A00904C0418BF0CB1698A0FEAFF0000EAFF0020C005000B000000
                    IE: Unknown: DD090010180201001C0000
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00
          Cell 10 - Address: 3C:89:94:E7:B6:6A
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=27/70  Signal level=-83 dBm
                    Encryption key:on
                    ESSID:"SKY29EIQ"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000104f444318e
                    Extra: Last beacon: 2780ms ago
                    IE: Unknown: 0008534B593239454951
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0104
                    IE: Unknown: 32040C121860
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 0B050300410000
                    IE: Unknown: 420100
                    IE: Unknown: 46057208010000
                    IE: Unknown: 2D1AAD0117FFFFFFFF00000000000000000000000000000000000000
                    IE: Unknown: 3D160B000400000000000000000000000000000000000000
                    IE: Unknown: 7F080400080000000040
                    IE: Unknown: DD570050F204104A000110104400010210470010308D817D61F7BEA3FE46CE0E9BE31987103C0001011049000600372A00012010580022007FC510001830E87B66EFEABE50B6E6CF542C915CEE303030303030303130000101
                    IE: Unknown: DD090010180203001C0000
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00
          Cell 11 - Address: 04:95:E6:63:96:84
                    Channel:40
                    Frequency:5.2 GHz (Channel 40)
                    Quality=37/70  Signal level=-73 dBm
                    Encryption key:on
                    ESSID:"Network Dienw"
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000012e94d8280
                    Extra: Last beacon: 2601ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 01088C9298A4B0C8E0EC
                    IE: Unknown: 074055532024011E28011E2C011E30011E34011E38011E3C011E40011E6401146801146C01147001147401148801148C011495011E99011E9D011EA1011EA5011E00
                    IE: Unknown: 200100
                    IE: Unknown: 23021400
                    IE: Unknown: 0B050300020000
                    IE: Unknown: 2D1AEF111EFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1628070000000000000000000000000000000000000000
                    IE: Unknown: BF0CB021C103FAFF0C03FAFF0C03
                    IE: Unknown: C005012A00F0FF
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0600E04C020160
                    IE: Unknown: 7F080000080000000040
          Cell 12 - Address: 04:95:E6:63:96:8C
                    Channel:40
                    Frequency:5.2 GHz (Channel 40)
                    Quality=53/70  Signal level=-57 dBm
                    Encryption key:on
                    ESSID:"Network Dienw"
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000012e958e900
                    Extra: Last beacon: 2598ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 01088C9298A4B0C8E0EC
                    IE: Unknown: 074055532024011E28011E2C011E30011E34011E38011E3C011E40011E6401146801146C01147001147401148801148C011495011E99011E9D011EA1011EA5011E00
                    IE: Unknown: 200100
                    IE: Unknown: 23021400
                    IE: Unknown: 0B050200020000
                    IE: Unknown: 2D1AEF111EFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1628070000000000000000000000000000000000000000
                    IE: Unknown: BF0CB021C103FAFF0C03FAFF0C03
                    IE: Unknown: C005012A00F0FF
                    IE: WPA Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0600E04C020160
                    IE: Unknown: 7F080000080000000040
          Cell 13 - Address: 20:B8:2B:4F:C4:44
                    Channel:108
                    Frequency:5.54 GHz (Channel 108)
                    Quality=38/70  Signal level=-72 dBm
                    Encryption key:on
                    ESSID:"VM4201079"
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000001f28048c640
                    Extra: Last beacon: 1637ms ago
                    IE: Unknown: 0009564D34323031303739
                    IE: Unknown: 01088C129824B048606C
                    IE: Unknown: 070A4E4C04240817640B1E00
                    IE: Unknown: 200100
                    IE: Unknown: 23021900
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 0B050000030000
                    IE: Unknown: 46057200000000
                    IE: Unknown: 3302796C
                    IE: Unknown: 3B158001020305060708090A737475767778797A7B8081
                    IE: Unknown: 2D1AEF0117FFFFFFFF00000000000000000000000000000000000000
                    IE: Unknown: 3D166C050000000000000000000000000000000000000000
                    IE: Unknown: 7F0B84000882010000C0014020
                    IE: Unknown: 6B0100
                    IE: Unknown: 6C027F00
                    IE: Unknown: BF0CB6698B0FAAFF0000AAFF0020
                    IE: Unknown: C005016A000000
                    IE: Unknown: C30402313131
                    IE: Unknown: FF27230500181200104C2002C0021B950000CC00AAFFAAFFAAFFAAFF7B1CC7711CC7711CC7711CC771
                    IE: Unknown: FF072404000106FCFF
                    IE: Unknown: FF0E260800A40820A408404308603208
                    IE: Unknown: DD7F0050F204104A0001101044000102103B000103104700100DF5E179C8513499E20177033788D28B1021000842726F6164636F6D1023000842726F6164636F6D10240006313233343536104200033236371054000800060050F20400011011000A42726F6164636F6D4150100800022008103C0001031049000600372A000120
                    IE: Unknown: DD0500904C0417
                    IE: Unknown: DD090010180200001C0000
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00

So the 5GHz has poorer quality but is stronger?

I notice that the 2.4GHz offers WPA as well as WPA2, whereas the 5GHz seems not to. But I don't know why wpa_supplicant should do something different when invoked by netctl.

You can btw. impact the roaming, https://wiki.archlinux.org/title/Wpa_supplicant#Roaming but I think will have to use Security=wpa-configsection in netctl for this.

seth · Yesterday 20:28:44

          Cell 05 - Address: 04:95:E6:63:96:89
                    Frequency:2.437 GHz (Channel 6)
                    Quality=69/70  Signal level=-41 dBm
                    ESSID:"Network Dienw"
          Cell 06 - Address: 04:95:E6:63:96:81
                    Frequency:2.437 GHz (Channel 6)
                    Quality=52/70  Signal level=-58 dBm
                    ESSID:"Network Dienw"
          Cell 07 - Address: 04:95:E6:63:96:91
                    Frequency:2.437 GHz (Channel 6)
                    Quality=52/70  Signal level=-58 dBm
                    ESSID:"Network Dienw"

04:95:E6:63:96:89 @2.437 has a MUCH better signal (it's a logarithmic scale) than the other two (on the 2.4GHz)

          Cell 11 - Address: 04:95:E6:63:96:84
                    Frequency:5.2 GHz (Channel 40)
                    Quality=37/70  Signal level=-73 dBm
                    ESSID:"Network Dienw"
          Cell 12 - Address: 04:95:E6:63:96:8C
                    Frequency:5.2 GHz (Channel 40)
                    Quality=53/70  Signal level=-57 dBm
                    ESSID:"Network Dienw"

04:95:E6:63:96:8C is en par w/ 04:95:E6:63:96:81 and 04:95:E6:63:96:91 (the lesser two of the 2.4GHz connections) and 04:95:E6:63:96:84 is bad.

how do I create the psk with bssid rather than ssid?

The 4WAY_HANDSHAKE_TIMEOUT can be legit or a stealth drop for an invalid password - you can deliberately try a bogus one to see whether the AP responds the same way.
nb that the ESSID is a mandatory profile setting and I ass·u·me netctl will use it to generate the PSK, even if the AP BSSID will he connected explicitly (which seems to have worked)

cfr · Today 06:44:37

seth wrote:

          Cell 05 - Address: 04:95:E6:63:96:89
                    Frequency:2.437 GHz (Channel 6)
                    Quality=69/70  Signal level=-41 dBm
                    ESSID:"Network Dienw"
          Cell 06 - Address: 04:95:E6:63:96:81
                    Frequency:2.437 GHz (Channel 6)
                    Quality=52/70  Signal level=-58 dBm
                    ESSID:"Network Dienw"
          Cell 07 - Address: 04:95:E6:63:96:91
                    Frequency:2.437 GHz (Channel 6)
                    Quality=52/70  Signal level=-58 dBm
                    ESSID:"Network Dienw"

04:95:E6:63:96:89 @2.437 has a MUCH better signal (it's a logarithmic scale) than the other two (on the 2.4GHz)

Thanks. That would be much better, then, if I could connect to it at all.

I did not realise that this would differ so much for a single device. I know they are obviously not the same device as far as the network is concerned, but it seems strange they are so different. It also seems odd that wpa_supplicant doesn't even seem to try the 2.4GHz channel (? wrong word?) if it is so much better.

seth wrote:

          Cell 11 - Address: 04:95:E6:63:96:84
                    Frequency:5.2 GHz (Channel 40)
                    Quality=37/70  Signal level=-73 dBm
                    ESSID:"Network Dienw"
          Cell 12 - Address: 04:95:E6:63:96:8C
                    Frequency:5.2 GHz (Channel 40)
                    Quality=53/70  Signal level=-57 dBm
                    ESSID:"Network Dienw"
04:95:E6:63:96:8C is en par w/ 04:95:E6:63:96:81 and 04:95:E6:63:96:91 (the lesser two of the 2.4GHz connections) and 04:95:E6:63:96:84 is bad.
how do I create the psk with bssid rather than ssid?
The 4WAY_HANDSHAKE_TIMEOUT can be legit or a stealth drop for an invalid password - you can deliberately try a bogus one to see whether the AP responds the same way.
nb that the ESSID is a mandatory profile setting and I ass·u·me netctl will use it to generate the PSK, even if the AP BSSID will he connected explicitly (which seems to have worked)

Thank you. I should probably have figured that out ...

netctl gets a connection like this. I will see if it persists any better.

Arch Linux

#1 2026-10-05 01:10:31

netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#2 2026-10-05 07:30:55

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#3 2026-10-05 07:39:42

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#4 2026-10-05 07:55:05

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#5 2026-10-05 23:20:53

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#6 2026-10-06 05:34:28

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#7 2026-10-06 07:05:41

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#8 2026-10-07 08:14:23

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#9 2026-10-07 14:12:02

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#10 2026-10-08 06:34:14

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#11 2026-10-08 06:43:13

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#12 2026-10-08 08:12:31

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#13 2026-10-08 16:16:15

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#14 2026-10-08 16:24:24

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#15 2026-10-08 19:52:32

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#16 Yesterday 06:59:19

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#17 Yesterday 13:33:19

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#18 Yesterday 16:12:16

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#19 Yesterday 16:49:29

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#20 Yesterday 20:28:44

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

#21 Today 06:44:37

Re: netctl: unexpected authentication state: alg 57980 (expected 0) tra...

Board footer