23.05.3 mesh11sd 3.1.0-1 continually resets Linksys EA8300 & TP-Link C7v2 wireless mesh radios

I have a mesh network consisting of a Linksys EA8300 and some TP-Link C7v2s. Today I upgraded the working 23.05.3 routers from mesh11sd 2.00 to mesh11sd 3.1.0. After the mesh11sd upgrade, the wireless signals started to constantly reset every few minutes, rendering the mesh and routers inoperable as the transmitters switched off and on.

Here's an extract from the system log:

Thu Mar 28 19:13:24 2024 daemon.err mesh11sd[22198]: mesh_hwmp_rootmode: command failed: Link has been severed (-67)
Thu Mar 28 19:13:24 2024 daemon.notice wpa_supplicant[1303]: m-11s-0: CTRL-EVENT-DSCP-POLICY clear_all
Thu Mar 28 19:13:24 2024 daemon.notice wpa_supplicant[1303]: nl80211: deinit ifname=m-11s-0 disabled_11b_rates=0
Thu Mar 28 19:13:24 2024 daemon.err wpa_supplicant[1303]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Thu Mar 28 19:13:24 2024 kern.info kernel: [  708.175049] br-lan: port 8(m-11s-0) entered blocking state
Thu Mar 28 19:13:24 2024 kern.info kernel: [  708.175129] br-lan: port 8(m-11s-0) entered listening state
Thu Mar 28 19:13:24 2024 daemon.err mesh11sd[22198]: mesh_gate_announcements: command failed: Link has been severed (-67)
Thu Mar 28 19:13:24 2024 kern.warn kernel: [  708.247116] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 2
Thu Mar 28 19:13:24 2024 kern.warn kernel: [  708.247209] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 2
Thu Mar 28 19:13:24 2024 kern.info kernel: [  708.341863] br-lan: port 8(m-11s-0) entered disabled state
Thu Mar 28 19:13:24 2024 kern.info kernel: [  708.374509] device m-11s-0 left promiscuous mode
Thu Mar 28 19:13:24 2024 kern.info kernel: [  708.374577] br-lan: port 8(m-11s-0) entered disabled state

I've shut down mesh11sd and removed it for now to get things up and running again.

I'm certainly no expert on this so if anyone has any ideas on what I am doing wrong or how I can troubleshoot the problem, I would certainly appreciate it. BTW, this was a working mesh on 23.05.3 with mesh11sd 2.00.

Paging @bluewavenet

Mesh11sd v3.1.0 is a very different beast to v2.0.0 as it by default auto-configures.

As you upgraded from a working v2.0.0, you should:

  1. start from scratch by removing 2.0.0, deleting the /etc/config/mesh11sd file and removing all references to mesh from the wireless config (/etc/config/wireless), then reboot before installing v3.1.0;
  2. Configure manual mode (auto-config off) then upgrade.

It will be cleaner to do 1 above as there are so many changes.

Before doing anything though, please read the documentation here:
https://openwrt.org/docs/guide-user/network/wifi/mesh/mesh11sd

EDIT: I added a warning to the docs about upgrading.

Pfft :rofl:

To provide an update since yesterday. I read the documentation and deleted the mesh11sd file in /etc/config/mesh11sd on the TP-Link C7v2s and the Linksys EA8300 and replaced it with the new 3.1.0 configuration files. I was going to post that this is an RTFM situation (I'm an oldtimer), but you politely beat me to it.

Unfortunately, 23.05.3 was released with version 2.0.0 of mesh11sd and was upgraded to 3.1.0 a few days later. Yes, I originally upgraded without reading the documentation.

The TP-Link C7v2s are up and running, but I am still struggling with my Linksys EA8300. I've got the Linksys EA8300 running without mesh11sd for now. I will try again later and post my results.

Thanks.

1 Like

@thomascrisan

Did you remember to do this bit (with the mesh11sd service stopped)?