I'm currently running batman-adv VLANs over an 802.11s backlink (just two mesh nodes, with an R7800 as the router and an AVM 3000 as an additional access point to increase coverage in a physically difficult room). This works very well on 21.02.2(ish – both devices are running custom branch-builds including the necessary packages, including wpad-openssl).
Today I tried updating first the router and then both devices to 21.02.3ish builds using the same configs as the 21.02.2ish builds. However, as long as one of the devices is on a newer build, the mesh fails with wpa_supplicant[1853]: mesh0: Mesh MPM: failed to send peering frame.
The connection starts to happen on the physical level (according to iw dev if-mesh station dump and the Status view in LuCi), but somehow the connection process breaks down (flooding the log with the peering frame message above).
Before reverting to the old firmware versions, I tried switching to wpad-wolfssl on both devices (without effect). I had no issues when going from 21.02.1 to 21.02.2 with the same config. The radios are set to channel 108, if that matters.
Hi, I have had the same problem. The solution for me was to change channel on the wireless interface. Seems like different country codes work.s with different channels, In my case I am using country code for Sweden and after upgrading to OpenWRT 21.02.3 I had to change from channel 64 to channel 48.
Thank you. I saw those reports but assumed that the cause could not be related since e.g. 21.02.2 works fine, so the earlier issue evidently got fixed. Unfortunately, I cannot simply change the channel as the haul-back radio of the AP is limited to channels above 100.
I've now verified that the issue is indeed the regulatory domain. Setting it to US makes the mesh work again (although of course I'm not allowed to run the system that way). The question now is, what has changed? I've looked through the commits but could not find anything that looks likely (the hostapd changes appear to be unrelated to DFS).
Same here, did an upgrade yesterday to OpenWrt SNAPSHOT r19859-36e46c3c13 / LuCI Master git-22.167.28356-8effea5 and that breaks 802.11s Mesh with the same symptomes. Change to US makes it work but that's a kind of weird of course being in NL
Is just using WDS an option? I have the feeling for most use cases it is the better option. Certainly for me it has been stable across snapshots for the RT3200, whereas mesh has not been.
There was an update to the latest DFS-ETSI standards. You are likely to have a quite long delay before a 5GHz radio will come up on high channel numbers, if at all and if it does come up it could shut down again at any time if the driver detects anything it thinks might be a radar.
Changing to US reg domain puts you on DFS-FCC which is much more relaxed, so will work - although not legal in ETSI areas.
While I'm interested in any information you have on that regdb change (I could not find any for the last year or so), I am pretty confident that this is not the issue here. The channel is coming up fine (i.e. I can connect to the other SSID running in AP mode, just the 802.11s connection fails when an ETSI domain is set. Also, this worked fine in 21.02.2.
So really nobody knows why 802.11s does not work anymore on DFS channels? I can get a mesh with OpenWrt 21.02-SNAPSHOT r16611-b54ef39e0b on channel 149 with ETSI domain, but this would limit TX power to 13 dBm due to SRD. The mesh connection is still somewhat viable, but much worse than with 26 dBm on channel 108.
You are entitled to your opinion.
A mesh must have a fixed channel for all nodes. Use of a DFS channel is not guaranteed, so do not try to use one for your mesh. It might work, it might not, it might be intermittent.
The latest OpenWrt implementations of DFS are stricter, rightly so if you want to prevent radar interference, although why interference is regarded as worse in some countries for exactly the same spectrum usage is a subject for discussion elsewhere.
I don't know why you think there is DFS interference on the channel. There is no evidence of that in the logs and the regular SSID on the same radio (and thus channel) works fine. Only the 802.11s connection does not work anymore for ETSI domains.
Now these are two point releases about a month apart, so it should be possible to pinpoint which change is responsible for this regression.
I don't think there is. The DFS process does a lot of monitoring over some time before allowing transmission. If it sees anything it cannot recognise as "wifi" signals it will restart its monitoring.
It might see a remote wifi device on the same channel, but right down in signal strength and in the normal and ever present microwave background, so not be sure what it is. This triggers a restart of the monitoring process - just to be safe.
The whole question of DFS, particularly in the EU, is a very contentious subject. I suspect bureaucratic interference by "powers that be" that are not technically minded is the root cause of this. But that is just my opinion.
The radio is transmitting fine (as I said, there are two SSIDs, one for the mesh and one for normal clients). When the monitoring algorithm detects something, there are clear log entries (I've been running this system for over a year now, at most every few months there was a dropout due to "something" being detected).
Same goes for the scan, and yes, initial radio startup time is a bit longer and there's a periodic rescan - I am fine with those for this setup. That's simply not what is going on after 21.02.3. The physical radio link is there, but the mesh implementation reports an error during the handshake. Or at least that's what it looks like to me.
Addendum: I'll change channels again and post some logs from both nodes for the mesh handshake.
That error happens when the mesh interface is not established (ie "up"), what would be expected if DFS was actively keeping the interface down.
Are you running mesh11sd? You can get debug information from it that might give useful information.
So this is still without mesh11sd. I've redacted unrelated clients etc. I first switched channel on the router and then on the repeater. MAC addresses etc. are redacted. The logs are from the router (from the point of changing the channel in LuCi to the interfaces being up, then again from the point the channel is changed on the repeater as well. Unrelated DHCP requests in between have been redacted).
Sat Jul 16 12:06:08 2022 daemon.info hostapd: wlan1: STA <CLIENTMAC1> RADIUS: starting accounting session 5DFD53FCDD071A3D
Sat Jul 16 12:06:08 2022 daemon.info hostapd: wlan1: STA <CLIENTMAC1> WPA: pairwise key handshake completed (RSN)
Sat Jul 16 12:06:08 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:09 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:10 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:11 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:12 2022 daemon.info dnsmasq-dhcp[10787]: DHCPDISCOVER(br-lan) <CLIENTMAC1>
Sat Jul 16 12:06:12 2022 daemon.info dnsmasq-dhcp[10787]: DHCPOFFER(br-lan) <CLIENTIP1> <CLIENTMAC1>
Sat Jul 16 12:06:12 2022 daemon.info dnsmasq-dhcp[10787]: DHCPDISCOVER(br-lan) <CLIENTMAC1>
Sat Jul 16 12:06:12 2022 daemon.info dnsmasq-dhcp[10787]: DHCPOFFER(br-lan) <CLIENTIP1> <CLIENTMAC1>
Sat Jul 16 12:06:12 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:13 2022 daemon.info dnsmasq-dhcp[10787]: DHCPREQUEST(br-lan) <CLIENTIP1> <CLIENTMAC1>
Sat Jul 16 12:06:13 2022 daemon.info dnsmasq-dhcp[10787]: DHCPACK(br-lan) <CLIENTIP1> <CLIENTMAC1>
Sat Jul 16 12:06:13 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:14 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:15 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:16 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:17 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:18 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:19 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:20 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:21 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:22 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:23 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:24 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:25 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:26 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:27 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:28 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:29 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:30 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:31 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:32 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:33 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:34 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:35 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:36 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:37 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:38 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:39 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:40 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:41 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:42 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:43 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:44 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:45 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:46 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:47 2022 daemon.notice hostapd: wlan0-1: DFS-CAC-COMPLETED success=1 freq=5540 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0
Sat Jul 16 12:06:47 2022 kern.info kernel: [136317.267575] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
Sat Jul 16 12:06:47 2022 kern.info kernel: [136317.318350] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
Sat Jul 16 12:06:47 2022 kern.info kernel: [136317.318610] br-lan: port 4(wlan0-1) entered blocking state
Sat Jul 16 12:06:47 2022 kern.info kernel: [136317.323785] br-lan: port 4(wlan0-1) entered forwarding state
Sat Jul 16 12:06:47 2022 daemon.notice hostapd: wlan0-1: interface state DFS->ENABLED
Sat Jul 16 12:06:47 2022 daemon.notice hostapd: wlan0-1: AP-ENABLED
Sat Jul 16 12:06:47 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Jul 16 12:06:47 2022 kern.info kernel: [136317.741362] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
Sat Jul 16 12:06:48 2022 kern.info kernel: [136318.326716] br-lan: port 4(wlan0-1) entered disabled state
Sat Jul 16 12:06:49 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Unknown event 54
Sat Jul 16 12:06:49 2022 daemon.notice hostapd: wlan0-1: DFS-PRE-CAC-EXPIRED freq=5500 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5500 cf2=0
Sat Jul 16 12:06:49 2022 daemon.notice hostapd: wlan0-1: DFS-PRE-CAC-EXPIRED freq=5520 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5520 cf2=0
Sat Jul 16 12:06:49 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Unknown event 54
Sat Jul 16 12:06:49 2022 daemon.notice hostapd: wlan0-1: DFS-PRE-CAC-EXPIRED freq=5540 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5540 cf2=0
Sat Jul 16 12:06:49 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Unknown event 54
Sat Jul 16 12:06:49 2022 daemon.notice hostapd: wlan0-1: DFS-PRE-CAC-EXPIRED freq=5560 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5560 cf2=0
Sat Jul 16 12:06:49 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Unknown event 54
Sat Jul 16 12:06:51 2022 daemon.notice wpa_supplicant[2019]: if-mesh: leaving mesh
Sat Jul 16 12:06:51 2022 kern.warn kernel: [136321.875955] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat Jul 16 12:06:51 2022 kern.info kernel: [136321.881686] ath10k_pci 0000:01:00.0: rts threshold -1
Sat Jul 16 12:06:51 2022 daemon.err wpa_supplicant[2019]: if-mesh: mesh leave error=-107
Sat Jul 16 12:06:51 2022 kern.info kernel: [136321.895351] ath10k_pci 0000:01:00.0: rts threshold -1
Sat Jul 16 12:06:51 2022 daemon.notice wpa_supplicant[2019]: if-mesh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat Jul 16 12:06:51 2022 daemon.notice wpa_supplicant[2019]: if-mesh: interface state COUNTRY_UPDATE->DFS
Sat Jul 16 12:06:51 2022 daemon.notice wpa_supplicant[2019]: if-mesh: DFS-CAC-START freq=5540 chan=108 sec_chan=1, width=1, seg0=106, seg1=0, cac_time=60s
Sat Jul 16 12:06:52 2022 daemon.notice netifd: radio0 (31139): command failed: Link has been severed (-67)
Sat Jul 16 12:06:52 2022 daemon.notice netifd: radio0 (31139): command failed: Link has been severed (-67)
Sat Jul 16 12:06:52 2022 daemon.notice netifd: radio0 (31139): command failed: Link has been severed (-67)
Sat Jul 16 12:06:52 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Sat Jul 16 12:06:52 2022 daemon.notice netifd: Interface 'mesh' is enabled
Sat Jul 16 12:07:04 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC3> IEEE 802.11: authenticated
Sat Jul 16 12:07:04 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC3> IEEE 802.11: associated (aid 5)
Sat Jul 16 12:07:04 2022 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED <CLIENTMAC3>
Sat Jul 16 12:07:04 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC3> RADIUS: starting accounting session 279147EC6CE812CB
Sat Jul 16 12:07:04 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC3> WPA: pairwise key handshake completed (RSN)
Sat Jul 16 12:07:04 2022 daemon.info dnsmasq-dhcp[10787]: DHCPDISCOVER(br-iot2) <CLIENTMAC3>
Sat Jul 16 12:07:04 2022 daemon.info dnsmasq-dhcp[10787]: DHCPOFFER(br-iot2) <CLIENTIP3> <CLIENTMAC3>
Sat Jul 16 12:07:04 2022 daemon.info dnsmasq-dhcp[10787]: DHCPREQUEST(br-iot2) <CLIENTIP3> <CLIENTMAC3>
Sat Jul 16 12:07:04 2022 daemon.info dnsmasq-dhcp[10787]: DHCPACK(br-iot2) <CLIENTIP3> <CLIENTMAC3> <CLIENTNAME3>
Sat Jul 16 12:07:05 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC4> IEEE 802.11: authenticated
Sat Jul 16 12:07:05 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC4> IEEE 802.11: associated (aid 6)
Sat Jul 16 12:07:05 2022 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED <CLIENTMAC4>
Sat Jul 16 12:07:05 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC4> RADIUS: starting accounting session 760A89E66534A8C3
Sat Jul 16 12:07:05 2022 daemon.info hostapd: wlan1-1: STA <CLIENTMAC4> WPA: pairwise key handshake completed (RSN)
Sat Jul 16 12:07:05 2022 daemon.info dnsmasq-dhcp[10787]: DHCPDISCOVER(br-iot2) <CLIENTMAC4>
Sat Jul 16 12:07:05 2022 daemon.info dnsmasq-dhcp[10787]: DHCPOFFER(br-iot2) <CLIENTIP4> <CLIENTMAC4>
Sat Jul 16 12:07:05 2022 daemon.info dnsmasq-dhcp[10787]: DHCPREQUEST(br-iot2) <CLIENTIP4> <CLIENTMAC4>
Sat Jul 16 12:07:05 2022 daemon.info dnsmasq-dhcp[10787]: DHCPACK(br-iot2) <CLIENTIP4> <CLIENTMAC4> <CLIENTNAME4>
Sat Jul 16 12:07:11 2022 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED <CLIENTMAC1>
Sat Jul 16 12:07:11 2022 daemon.info hostapd: wlan1: STA <CLIENTMAC1> IEEE 802.11: disassociated
Sat Jul 16 12:07:12 2022 daemon.info hostapd: wlan1: STA <CLIENTMAC1> IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Jul 16 12:07:41 2022 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED <CLIENTMAC2>
Sat Jul 16 12:07:41 2022 daemon.info hostapd: wlan1: STA <CLIENTMAC2> IEEE 802.11: disassociated
Sat Jul 16 12:07:42 2022 daemon.info hostapd: wlan1: STA <CLIENTMAC2> IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Jul 16 12:07:53 2022 daemon.notice wpa_supplicant[2019]: if-mesh: DFS-CAC-COMPLETED success=1 freq=5540 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0
Sat Jul 16 12:07:53 2022 daemon.notice wpa_supplicant[2019]: if-mesh: interface state DFS->ENABLED
Sat Jul 16 12:07:53 2022 daemon.notice wpa_supplicant[2019]: if-mesh: AP-ENABLED
Sat Jul 16 12:07:53 2022 daemon.notice wpa_supplicant[2019]: if-mesh: joining mesh <SSIDMESH>
Sat Jul 16 12:07:53 2022 kern.info kernel: [136383.827873] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
Sat Jul 16 12:07:54 2022 daemon.notice netifd: Network device 'if-mesh' link is up
Sat Jul 16 12:07:54 2022 daemon.notice netifd: Interface 'mesh' has link connectivity
Sat Jul 16 12:07:54 2022 daemon.notice netifd: Interface 'mesh' is setting up now
Sat Jul 16 12:07:54 2022 daemon.notice wpa_supplicant[2019]: if-mesh: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sat Jul 16 12:07:54 2022 daemon.notice wpa_supplicant[2019]: if-mesh: MESH-GROUP-STARTED ssid="<SSIDMESH>" id=0
Sat Jul 16 12:07:54 2022 kern.info kernel: [136384.834901] IPv6: ADDRCONF(NETDEV_CHANGE): if-mesh: link becomes ready
Sat Jul 16 12:07:54 2022 kern.info kernel: [136384.858751] batman_adv: bat0: Adding interface: if-mesh
Sat Jul 16 12:07:54 2022 kern.info kernel: [136384.858846] batman_adv: bat0: Interface activated: if-mesh
Sat Jul 16 12:07:54 2022 daemon.notice netifd: Interface 'mesh' is now up
Sat Jul 16 12:07:55 2022 user.notice nlbwmon: Reloading nlbwmon due to ifup of mesh (if-mesh)
Sat Jul 16 12:07:59 2022 kern.info kernel: [136389.324255] br-lan: port 4(wlan0-1) entered blocking state
Sat Jul 16 12:07:59 2022 kern.info kernel: [136389.324280] br-lan: port 4(wlan0-1) entered forwarding state
Sat Jul 16 12:07:59 2022 daemon.notice netifd: Network device 'wlan0-1' link is up
...
[Here the channel switch happened on the repeater]
...
Sat Jul 16 12:22:37 2022 daemon.notice wpa_supplicant[2019]: if-mesh: new peer notification for <REPEATERMAC>
Sat Jul 16 12:22:37 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:22:37 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:22:37 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:22:37 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
...
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: new peer notification for <REPEATERMAC>
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
Sat Jul 16 12:40:56 2022 daemon.notice wpa_supplicant[2019]: if-mesh: Mesh MPM: failed to send peering frame
...
