Crashes with 802.11s on BT HH5 type A

Hi Guys,

I'm having a problem with a 802.11s mesh network comprising 4 devices. One connected to the DMZ of the router and three others all within good range of each other (rssi -60dBm)

The association works fine and seems to be quite stable but from time to time one of the three others will crash such that it can't be used or ping'd but still shows associated (or at least claims to be associated according to the other non crashed devices).

I always get the same trace file in the system log as per below (hope the formatting is ok).
edit I should have mentioned the mesh seems to work ok with just the master and one node, problem seems more prevelant when I have 2 or more nodes plus the master in play.

Any ideas on how to debug / fix this problem as currently the mesh is not reliable enough to use.

Regards Tim

Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.024971] ------------[ cut here ]------------
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.028270] WARNING: CPU: 0 PID: 1649 at net/core/flow_dissector.c:960 0x8045ff84
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.035724] Modules linked in: ath9k ath9k_common iptable_nat ath9k_hw ath10k_pci ath10k_core ath xt_state xt_nat xt_conntrack xt_REDIRECT xt_MASQUERADE xt_FLOWOFFLOAD xt_CT pppoe nf_nat nf_flow_table_hw nf_flow_table nf_conntrack mac80211 ipt_REJECT cfg80211 ath9k_pci_owl_loader xt_time xt_tcpudp xt_multiport xt_mark xt_mac xt_limit xt_comment xt_TCPMSS xt_LOG pppox ppp_async nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 pppoatm ppp_generic slhc br2684 atm drv_ifxos dwc2 gpio_button_hotplug
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.096877] CPU: 0 PID: 1649 Comm: sh Not tainted 5.4.154 #0
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.102381] Stack : 0000011b 0000011c 00000000 80081d1c 00000000 00000000 00000000 00000000
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.110724]         00000000 00000000 00000000 00000000 00000000 00000001 87c0bb78 330fa2eb
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.119081]         87c0bc10 00000000 00000000 0000011c 00000038 80615d04 204e6f74 20746169
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.127436]         0000011c 70800000 00000000 00017a6d 80000000 87c0bb58 00000000 8045ff84
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.135792]         00000009 87e77468 85d25418 80730000 00000003 00000010 00000000 80890000
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.144148]         ...
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.146585] Call Trace:
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.146603] [<80081d1c>] 0x80081d1c
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.152546] [<80615d04>] 0x80615d04
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.156000] [<8045ff84>] 0x8045ff84
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.159485] [<8000ef60>] 0x8000ef60
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.162957] [<8000ef68>] 0x8000ef68
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.166438] [<80760000>] 0x80760000
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.169913] [<805fb8fc>] 0x805fb8fc
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.173401] [<8007e7c4>] 0x8007e7c4
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.176884] [<80030b7c>] 0x80030b7c
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.180365] [<8045ff84>] 0x8045ff84
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.183846] [<80030c24>] 0x80030c24
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.187334] [<805dfaf4>] 0x805dfaf4
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.190815] [<8045ff84>] 0x8045ff84
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.194299] [<873b0180>] 0x873b0180 [mac80211@31a69c81+0x7dad0]
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.200226] [<805e01cc>] 0x805e01cc
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.203690] [<80162460>] 0x80162460
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.207192] [<8016266c>] 0x8016266c
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.210659] [<8046ffb8>] 0x8046ffb8
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.214140] [<805dfe24>] 0x805dfe24
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.217618] [<8046e754>] 0x8046e754
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.221104] [<80452030>] 0x80452030
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.224592] [<80461408>] 0x80461408
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.228073] [<8046f1ac>] 0x8046f1ac
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.231569] [<873b3328>] 0x873b3328 [mac80211@31a69c81+0x7dad0]
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.237512] [<873b959c>] 0x873b959c [mac80211@31a69c81+0x7dad0]
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.243382] [<803297dc>] 0x803297dc
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.246905] [<873bb288>] 0x873bb288 [mac80211@31a69c81+0x7dad0]
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.252791] [<804708a4>] 0x804708a4
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.256266] [<800348e8>] 0x800348e8
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.259753] [<80470c0c>] 0x80470c0c
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.263233] [<80034c28>] 0x80034c28
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.266719] [<8061bdbc>] 0x8061bdbc
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.270183] [<80082f14>] 0x80082f14
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.273675] [<800351ac>] 0x800351ac
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.277153] [<803297dc>] 0x803297dc
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.280641] [<8000aa08>] 0x8000aa08
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.284114]
Mon Jul  4 11:36:08 2022 kern.warn kernel: [   42.285687] ---[ end trace 8545cd34f7a0c70c ]---

What would be interesting is what happened in the logs immediately prior to this.

The BT HH5A has a QCA9xxxx series wireless, and your log extract is very similar to what I have seen on other routers with QCA9xxxx when you set mesh parameters in /etc/config/wireless
What I found was after the crash it continues to "work" but when it tries to connect to a second meshnode it will very often lock up.

Of course it may be something else here.

The scenario I described is one of the reasons the mesh11sd package was developed as it applies the mesh parameters to the interface after the interface has come up, unlike what happens if the parameters are set in /etc/config/wireless.

Hi Bluewavenet

here's a bit more info, I'm running OpenWrt 21.02.1 r16325-88151b8303 with mesh11sd installed as recommended. The main log dump is right at the bottom of this post.

The only parameters in the mesh11sd config I've changed is the RSSI minimum from -80 to -90 as one of the nodes was at about -81dBm RSSI and I thought that may be related to problem. All the other mesh parameters are in the wireless config file as per below:

EDIT - as per mesh11sd recommendations I moved all the wireless config info into the mesh11sd config file (leaving the wireless config file empty ) and rebooted.
The device failed to associate and when I check the wireless config file it had become populated with the openwrt defaults !


config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'pci0000:01/0000:01:00.0/0000:02:00.0'
        option htmode 'VHT80'
        option cell_density '0'

config wifi-iface 'mesh0'
        option network 'lan'
        option macaddr '8C:10:D4:16:29:03'
        option device 'radio0'
        option disabled '0'
        option ifname 'mesh0'
        option mode 'mesh'
        option mesh_id 'Homemesh'
        option encryption 'sae'
        option key 'xxxxxx'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:0e.0'
        option htmode 'HT20'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'Home'
        option encryption 'psk2'
        option key 'xxxxxx'

And for good measure here is my network config:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdc8:7c9d:fd05::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

config device
        option name 'eth0.1'
        option macaddr '40:f2:01:3a:b9:b4'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.3'
        option netmask '255.255.255.0'
        option gateway '192.168.1.1'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 4 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 6t'

config device
        option name 'mesh0'

config device
        option name 'wlan1'

The master meshnode which connects to the modem / router has extra stuff for the wan as I'm not currently using VDSL due line vectoring issues.

The crash seems to happen more often when another meshnode is added to the network but sometimes when the mesh has been running ok. I've attached another log file showing what happened prior to the crash. The log starts just after everything is up and running - a lot of it maybe irrelavent.

Hope this helps - I get the same fault log on all meshnodes, I wonder if somewhere I've messed up the config files, maybe I need to put all wireless config stuff into mesh11sd as you mention ?

Regards Tim

Mon Jul  4 11:35:58 2022 kern.info kernel: [   32.633695] ath10k_pci 0000:02:00.0: wmi print 'P 135 V 16 T 433'
Mon Jul  4 11:35:58 2022 kern.warn kernel: [   32.646264] ath10k_pci 0000:02:00.0: pdev param 0 not supported by firmware
Mon Jul  4 11:35:58 2022 kern.info kernel: [   32.668225] ath10k_pci 0000:02:00.0: rts threshold -1
Mon Jul  4 11:35:58 2022 kern.warn kernel: [   32.673159] ath10k_pci 0000:02:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Mon Jul  4 11:35:58 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy wlan1) --> new PHY
Mon Jul  4 11:35:59 2022 kern.info kernel: [   32.956599] br-lan: port 2(wlan1) entered blocking state
Mon Jul  4 11:35:59 2022 kern.info kernel: [   32.960633] br-lan: port 2(wlan1) entered disabled state
Mon Jul  4 11:35:59 2022 kern.info kernel: [   32.966563] device wlan1 entered promiscuous mode
Mon Jul  4 11:35:59 2022 kern.info kernel: [   32.970940] br-lan: port 2(wlan1) entered blocking state
Mon Jul  4 11:35:59 2022 kern.info kernel: [   32.975881] br-lan: port 2(wlan1) entered forwarding state
Mon Jul  4 11:35:59 2022 kern.info kernel: [   32.981792] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Mon Jul  4 11:35:59 2022 daemon.notice netifd: bridge 'br-lan' link is up
Mon Jul  4 11:35:59 2022 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Jul  4 11:35:59 2022 kern.info kernel: [   33.297305] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Mon Jul  4 11:35:59 2022 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->ENABLED
Mon Jul  4 11:35:59 2022 daemon.notice hostapd: wlan1: AP-ENABLED
Mon Jul  4 11:35:59 2022 kern.info kernel: [   33.621249] ath10k_pci 0000:02:00.0: NOTE:  Firmware DBGLOG output disabled in debug_mask: 0x10000000
Mon Jul  4 11:35:59 2022 kern.info kernel: [   33.690137] br-lan: port 3(mesh0) entered blocking state
Mon Jul  4 11:35:59 2022 kern.info kernel: [   33.694095] br-lan: port 3(mesh0) entered disabled state
Mon Jul  4 11:35:59 2022 kern.info kernel: [   33.699913] device mesh0 entered promiscuous mode
Mon Jul  4 11:36:00 2022 daemon.notice netifd: Network device 'wlan1' link is up
Mon Jul  4 11:36:03 2022 daemon.notice wpa_supplicant[1201]: mesh0: leaving mesh
Mon Jul  4 11:36:03 2022 kern.info kernel: [   37.244154] br-lan: port 3(mesh0) entered disabled state
Mon Jul  4 11:36:04 2022 daemon.notice mesh11sd[1649]: mesh11sd v1.1.1 has started: mesh management mode 1
Mon Jul  4 11:36:05 2022 kern.info kernel: [   39.418946] ath10k_pci 0000:02:00.0: wmi print 'P 135 V 16 T 433'
Mon Jul  4 11:36:05 2022 kern.warn kernel: [   39.431255] ath10k_pci 0000:02:00.0: pdev param 0 not supported by firmware
Mon Jul  4 11:36:05 2022 kern.info kernel: [   39.453396] ath10k_pci 0000:02:00.0: rts threshold -1
Mon Jul  4 11:36:05 2022 kern.warn kernel: [   39.457941] ath10k_pci 0000:02:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: nl80211: Failed to set interface into station mode
Mon Jul  4 11:36:05 2022 daemon.err wpa_supplicant[1201]: mesh0: mesh leave error=-134
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: mesh0: interface state UNINITIALIZED->ENABLED
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: mesh0: AP-ENABLED
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: mesh0: joining mesh Homemesh
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Mon Jul  4 11:36:05 2022 daemon.notice netifd: Network device 'mesh0' link is up
Mon Jul  4 11:36:05 2022 kern.info kernel: [   39.501179] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Mon Jul  4 11:36:05 2022 kern.info kernel: [   39.506747] br-lan: port 3(mesh0) entered blocking state
Mon Jul  4 11:36:05 2022 kern.info kernel: [   39.511515] br-lan: port 3(mesh0) entered forwarding state
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: mesh0: MESH-GROUP-STARTED ssid="Homemesh" id=0
Mon Jul  4 11:36:05 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 8c:10:d4:16:29:03
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 00:90:01:08:16:01
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 00:90:01:08:16:01
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 00:90:01:08:16:01
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 00:90:01:08:16:01
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: mesh plink with 00:90:01:08:16:01 established
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: MESH-PEER-CONNECTED 00:90:01:08:16:01
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.479520] ------------[ cut here ]------------
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.482886] WARNING: CPU: 0 PID: 35 at net/core/flow_dissector.c:960 0x8045ff84
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.490100] Modules linked in: ath9k ath9k_common iptable_nat ath9k_hw ath10k_pci ath10k_core ath xt_state xt_nat xt_conntrack xt_REDIRECT xt_MASQUERADE xt_FLOWOFFLOAD xt_CT pppoe nf_nat nf_flow_table_hw nf_flow_table nf_conntrack mac80211 ipt_REJECT cfg80211 ath9k_pci_owl_loader xt_time xt_tcpudp xt_multiport xt_mark xt_mac xt_limit xt_comment xt_TCPMSS xt_LOG pppox ppp_async nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 pppoatm ppp_generic slhc br2684 atm drv_ifxos dwc2 gpio_button_hotplug
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.551275] CPU: 0 PID: 35 Comm: kworker/0:1 Not tainted 5.4.154 #0
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.557406] Workqueue: events 0x802d96d0
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.561297] Stack : 0000011b 0000011c 80661d84 87d19a14 00000000 00000000 00000000 00000000
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.569640]         00000000 00000000 00000000 00000000 00000000 00000001 87d199c8 e0c4771d
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.577996]         87d19a60 00000000 00000000 0000011d 00000038 80615d04 3a206576 656e7473
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.586352]         0000011d 808c0000 00000000 0008815e 00000000 87d199a8 00000000 8045ff84
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.594708]         00000009 865a1468 87154018 80730000 00000003 00000010 00000000 80890000
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.603064]         ...
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.605498] Call Trace:
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.605529] [<80615d04>] 0x80615d04
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.611436] [<8045ff84>] 0x8045ff84
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.614946] [<8000ef60>] 0x8000ef60
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.618390] [<8000ef68>] 0x8000ef68
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.621878] [<80760000>] 0x80760000
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.625358] [<805fb8fc>] 0x805fb8fc
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.628841] [<8007e7c4>] 0x8007e7c4
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.632325] [<80030b7c>] 0x80030b7c
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.635806] [<8045ff84>] 0x8045ff84
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.639286] [<80030c24>] 0x80030c24
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.642770] [<800143a0>] 0x800143a0
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.646243] [<8045ff84>] 0x8045ff84
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.649736] [<80067de8>] 0x80067de8
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.653252] [<80461408>] 0x80461408
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.656741] [<873b3328>] 0x873b3328 [mac80211@553b0959+0x7dad0]
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.662613] [<80066338>] 0x80066338
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.666132] [<873b959c>] 0x873b959c [mac80211@553b0959+0x7dad0]
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.672021] [<80058c70>] 0x80058c70
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.675546] [<873bb288>] 0x873bb288 [mac80211@553b0959+0x7dad0]
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.681427] [<80074bc0>] 0x80074bc0
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.684895] [<8009a4b8>] 0x8009a4b8
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.688387] [<80034c28>] 0x80034c28
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.691863] [<8061bdbc>] 0x8061bdbc
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.695364] [<80034f50>] 0x80034f50
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.698822] [<802d8ec4>] 0x802d8ec4
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.702294] [<80035054>] 0x80035054
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.705786] [<802d9858>] 0x802d9858
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.709267] [<802d9a64>] 0x802d9a64
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.712759] [<802d984c>] 0x802d984c
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.716250] [<8004a358>] 0x8004a358
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.719717] [<8004a714>] 0x8004a714
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.723193] [<80617274>] 0x80617274
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.726676] [<8004a5ac>] 0x8004a5ac
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.730149] [<8004ff94>] 0x8004ff94
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.733638] [<8004fe5c>] 0x8004fe5c
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.737119] [<8004fe5c>] 0x8004fe5c
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.740603] [<8004fe5c>] 0x8004fe5c
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.744081] [<8000a4f8>] 0x8000a4f8
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.747578]
Mon Jul  4 11:36:06 2022 kern.warn kernel: [   40.749150] ---[ end trace ac7d4508411bab38 ]---
Mon Jul  4 11:36:06 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 8c:10:d4:16:29:03
Mon Jul  4 11:36:07 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 8c:10:d4:16:29:03
Mon Jul  4 11:36:07 2022 daemon.notice wpa_supplicant[1201]: mesh0: new peer notification for 8c:10:d4:16:29:03
Mon Jul  4 11:36:07 2022 daemon.notice wpa_supplicant[1201]: mesh0: mesh plink with 8c:10:d4:16:29:03 established
Mon Jul  4 11:36:07 2022 daemon.notice wpa_supplicant[1201]: mesh0: MESH-PEER-CONNECTED 8c:10:d4:16:29:03

As QCA9880 is a wave1 chipset, you may want to test ath10k and the corresponding firmware instead of ath10k-ct.

1 Like

Ah! I think the documentation needed to be clearer.
It now reads " it is recommended that all mesh parameter options are removed from the wireless config"
So only the mesh parameter options such as those already in the mesh11sd config.
eg:

option mesh_fwding '1'
option mesh_rssi_threshold '-80'
option mesh_gate_announcements '1'
option mesh_hwmp_rootmode '3'
option mesh_max_peer_links '150'

This is very unlikely to work, or at best will drop back to a very low data rate. Remember this is a logarithmic scale, a drop of 3dBm in RSSI means half the signal strength. Sounds like you need an intermediate meshnode. This however is nothing to do with your problem.

Please show the output of:
opkg list-installed | grep "ath10k"

Hi again and thanks for your patience !

Here's the info from grep - I had changed the drivers to non ct for the QCA chip, but looking at the output maybe I need to change kmod to non ct as well ?

ath10k-board-qca988x - 20211216-1
ath10k-firmware-qca988x - 20211216-1
kmod-ath10k-ct - 5.4.154+2021-09-22-e6a7d5b5-1

Here's my wireless config

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'pci0000:01/0000:01:00.0/0000:02:00.0'
        option htmode 'VHT80'
        option cell_density '0'

config wifi-iface 'mesh0'
        option network 'lan'
        option macaddr '8C:10:D4:16:29:04'
        option device 'radio0'
        option disabled '0'
        option ifname 'mesh0'
        option mode 'mesh'
        option mesh_id 'Homemesh'
        option encryption 'sae'
        option key 'xxxxxx'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:0e.0'
        option htmode 'HT20'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'Home'
        option encryption 'psk2'
        option key 'xxxx'

And here's my mesh11sd config file - this is how I started and read the instructions ie only minimal mesh related stuff in the mesh11sd config and the rest in the wireless config. So I understood the instructions ok but your edit makes it clearer.

I've changed the rssi back to -80 as you suggested.

One other thing when a mesh node crashes it sometimes takes down the main meshnode and it's ethernet switch stops - I think the crashed meshnode is flooding the network. I'll run up wire shark to see what's going on and report back.

Regards Tim

config mesh11sd 'setup'
        option enabled '1'
        option debuglevel '1'
        option checkinterval '10'
        option interface_timeout '10'

config mesh11sd 'mesh_params'
        option mesh_fwding '1'
        option mesh_rssi_threshold '-80'
        option mesh_gate_announcements '1'
        option mesh_hwmp_rootmode '3'
        option mesh_max_peer_links '150'

I would replace that with the non-ct version

kmod-ath10k

Not sure if it will help though, as I think I read somewhere either should be ok. I use kmod-ath10k, not had a crash, but only have 3 nodes and am using 2 bthub5 with my own build of 22.03 RC4 and one with the current 21. release and am not using mesh11sd.

Thanks mjs

I changed to the kmod-ath10k and while the mesh node associates ok it is not reachable by ping or via its webpage (as you might expect). The meshnode was set to DHCP, setting it to a fixed IP allows me to connect but it will likely crash in due course.

Seems if my meshnodes are are set to dhcp they have trouble getting an ip address. I have set static ip address bindings so I always know where to look for them when DHCP works.

Just seems like there's a disconnect between the mesh and the lan.

Regards Tim

EDIT

just crashed as expected immediately after it joined the mesh, see log

Tue Jul  5 10:38:47 2022 daemon.notice wpa_supplicant[1167]: mesh0: new peer notification for 00:90:01:08:16:01
Tue Jul  5 10:38:48 2022 daemon.notice wpa_supplicant[1167]: mesh0: new peer notification for 8c:10:d4:16:29:03
Tue Jul  5 10:38:49 2022 daemon.notice wpa_supplicant[1167]: mesh0: mesh plink with 00:90:01:08:16:01 established
Tue Jul  5 10:38:49 2022 daemon.notice wpa_supplicant[1167]: mesh0: MESH-PEER-CONNECTED 00:90:01:08:16:01
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.341669] ------------[ cut here ]------------
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.344953] WARNING: CPU: 0 PID: 734 at net/core/flow_dissector.c:960 0x8045ff84
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.352333] Modules linked in: ath9k ath9k_common iptable_nat ath9k_hw ath10k_pci ath10k_core ath xt_state xt_nat xt_conntrack xt_REDIRECT xt_MASQUERADE xt_FLOWOFFLOAD xt_CT pppoe nf_nat nf_flow_table_hw nf_flow_table nf_conntrack mac80211 ipt_REJECT cfg80211 ath9k_pci_owl_loader xt_time xt_tcpudp xt_multiport xt_mark xt_mac xt_limit xt_comment xt_TCPMSS xt_LOG pppox ppp_async nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 pppoatm ppp_generic slhc br2684 atm drv_ifxos dwc2 gpio_button_hotplug
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.413462] CPU: 0 PID: 734 Comm: kworker/0:3 Not tainted 5.4.154 #0
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.419724] Workqueue: events 0x802d96d0
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.423607] Stack : 00000112 00000113 80661d84 872b9a14 00000000 00000000 00000000 00000000
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.431952]         00000000 00000000 00000000 00000000 00000000 00000001 872b99c8 930e01b3
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.440307]         872b9a60 00000000 00000000 00000114 00000038 80615d04 3a206576 656e7473
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.448663]         00000114 808c0000 00000000 0006678c 00000000 872b99a8 00000000 8045ff84
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.457019]         00000009 864f942c 87265a18 80730000 00000003 00000010 00000000 80890000
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.465375]         ...
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.467812] Call Trace:
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.467884] [<80615d04>] 0x80615d04
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.473754] [<8045ff84>] 0x8045ff84
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.477252] [<8000ef60>] 0x8000ef60
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.480709] [<8000ef68>] 0x8000ef68
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.484189] [<80760000>] 0x80760000
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.487662] [<805fb8fc>] 0x805fb8fc
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.491152] [<8007e7c4>] 0x8007e7c4
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.494636] [<80030b7c>] 0x80030b7c
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.498117] [<8045ff84>] 0x8045ff84
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.501598] [<80030c24>] 0x80030c24
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.505096] [<8045ff84>] 0x8045ff84
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.508589] [<864a1d40>] 0x864a1d40 [ath9k@04403f93+0x18210]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.514249] [<8691eb08>] 0x8691eb08 [ath9k_hw@ef3223b7+0x555c0]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.520183] [<864a3fe0>] 0x864a3fe0 [ath9k@04403f93+0x18210]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.525830] [<80461408>] 0x80461408
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.529276] [<8061bdbc>] 0x8061bdbc
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.532813] [<873b3328>] 0x873b3328 [mac80211@b9e6444c+0x7dad0]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.538736] [<873b959c>] 0x873b959c [mac80211@b9e6444c+0x7dad0]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.544676] [<873bb288>] 0x873bb288 [mac80211@b9e6444c+0x7dad0]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.550526] [<805992a0>] 0x805992a0
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.554007] [<80034c28>] 0x80034c28
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.557481] [<8061bdbc>] 0x8061bdbc
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.560975] [<80034f50>] 0x80034f50
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.564446] [<802d8ec4>] 0x802d8ec4
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.567921] [<80035054>] 0x80035054
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.571403] [<802d9858>] 0x802d9858
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.574886] [<802d9a64>] 0x802d9a64
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.578366] [<802d984c>] 0x802d984c
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.581869] [<8004a358>] 0x8004a358
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.585345] [<8004a714>] 0x8004a714
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.588812] [<80617274>] 0x80617274
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.592309] [<8004a5ac>] 0x8004a5ac
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.595768] [<8004ff94>] 0x8004ff94
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.599250] [<8004fe5c>] 0x8004fe5c
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.602752] [<8004fe5c>] 0x8004fe5c
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.606227] [<8004fe5c>] 0x8004fe5c
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.609700] [<8000a4f8>] 0x8000a4f8
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.613197]
Tue Jul  5 10:38:50 2022 kern.warn kernel: [   41.614759] ---[ end trace 2b911626760ecbef ]---

I have all three nodes set up with static lan addresses.

I've only been using the 21.x branch on one of my routers for a couple of days, as I'd previous skipped it as I had been using the DSA patches with master. I had a few dns and dhcp issues when I used it as my gateway/ vdsl router, so swapped it out to a node, although that may well have been my config, having had to flash all three routers in the last few days.

Here are the relevant bits out of wireless and network from my freshly set up 21.x node, although it will quite likely contain errors.

I intend flashing it to my minimal 22.03 RC4 build, now that I've got one that boots up ok.


config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'pci0000:01/0000:01:00.0/0000:02:00.0'
        option noscan '1'
        option country 'GB'
        option channels '36-48'
        option htmode 'VHT80'
        option channel '48'
        option cell_density '0'



config wifi-iface 'mesh0'
        option device 'radio0'
        option ifname 'mesh0'
        option mode 'mesh'
        option mesh_id 'xxxxxxxxxxxxxxxxxxxx'
        option encryption 'sae'
        option key 'xxxxxxxxxxxxxxxxxx'
        option mesh_fwding '0'
        option network 'mesh_5ghz'
        option disassoc_low_ack '0'
        option mesh_gate_announcements '1'
        option max_inactivity '15'
        option macaddr 'xxxxxxxxx'
config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'bat0'
        list ports 'eth0.1'

config device
        option name 'eth0.1'
        option macaddr 'xxxxxxxxx'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.250'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option gateway '192.168.1.1'
        list dns '192.168.1.1'


config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '6t 4 2 0 1'
        option vid '1'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '6t 5'
        option vid '2'

config interface 'bat0'
        option proto 'batadv'
        option routing_algo 'BATMAN_IV'
        option aggregated_ogms '1'
        option ap_isolation '0'
        option bonding '0'
        option fragmentation '1'
        option gw_mode 'off'
        option log_level '0'
        option orig_interval '1000'
        option bridge_loop_avoidance '1'
        option distributed_arp_table '1'
        option multicast_mode '1'
        option network_coding '0'
        option hop_penalty '30'
        option isolation_mark '0x00000000/0x00000000'

config interface 'mesh_5ghz'
        option mtu '2304'
        option proto 'batadv_hardif'
        option master 'bat0'

config interface 'mesh_2ghz'
        option mtu '2304'
        option proto 'batadv_hardif'
        option master 'bat0'

root@router:/etc/config#

Hi mjs

thanks for letting me have a peak at your config files, I'm begining to wonder if my problem lies with the master meshnode ie the node which links the mesh to the wan ethernet connector and so onto my dmz within the router / modem.

My wireless and network configs are very similar to yours but I'm not currenty using BATMAN as I have enough problems as things stand !

Here are the config files for my 'master' meshnode

Network


config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

config device
        option name 'eth0.1'
        option macaddr '34:8a:ae:d7:39:66'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option delegate '0'
        option gateway '212.158.250.32'
        option ipaddr '192.168.1.1'

config interface 'wan'
        option device 'eth0.2'
        option proto 'static'
        option ipaddr '192.168.2.2'
        option netmask '255.255.255.0'
        option gateway '192.168.2.1'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 4 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 6t'

config device
        option name 'wlan1'

config device
        option name 'mesh0'
        option ipv6 '0'

here are my wifi config from master meshnode, the commented out bits are handled by mesh11sd

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'pci0000:01/0000:01:00.0/0000:02:00.0'
        option htmode 'VHT80'
        option country 'GB'
        option cell_density '0'

config wifi-iface 'mesh0'
        option macaddr '00:90:01:08:16:01'
        option device 'radio0'
        option ifname 'mesh0'
        option mode 'mesh'
        option mesh_id 'Homemesh'
        option encryption 'sae'
        option key 'xxx'
#       option mesh_fwding '1'
        option disassoc_low_ack '0'
        option skip_inactivity_poll '1'
#       option mesh_rssi_threshold '1'
#       option mesh_gate_announcements '1'
        option max_inactivity '15'
        option network 'lan'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:0e.0'
        option htmode 'HT20'
        option cell_density '0'
        option country 'GB'
        option channel '1'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option mode 'ap'
        option ssid 'Home'
        option encryption 'psk2'
        option key 'xxxx'
        option network 'lan'

I don't have a mesh_5ghz like you, rather mine connects to the LAN along with the 4 port 1gigabit switch.

Me thinks I need some guidance here as I'm well and truly wrapped around the axle and going round in circles for good measure !

Regards Tim

Ok So I've taken the 'nuclear option' and reflashed the three mesh nodes with 22.03.0 rc4 and then changed the IP's to dhcp clients and disabled DHCP server on each one.

I then followed this guide exactly with only minor changes for the SSID of the meshnode and AP.
Mesh11sd was installed but not changed, ath10k non CT drivers installed along withwpad-mesh-openssl.

The main meshnode which connects via wan to the DMZ is currently untouched with 21.02.1.

Things seems a lot more stable - time will tell but one of the meshnodes seems slow to boot, sometimes hangs during boot (starts solid green, then flashing green then sticks on solid green) and when it is running its download speed on speedtest.net starts of at 25M then slowly drops to 10M. None of the other mesh nodes do this despite them all having good signals.

Progress of sorts and lots of lessons learned.

Regards Tim

On the node with the direct Internet feed, show the outputs of:

mesh11sd status

and

iw dev mesh0 mpath dump

As requested here are the outputs from the following commands taken from the meshnode which connects to the direct internet feed. As mentioned before this device is running 21.02.1

mesh11sd status

{
  "setup":{
    "version":"1.1.1",
    "enabled":"1",
    "service":"running",
    "checkinterval":"10",
    "interface_timeout":"10",
    "debuglevel":"1"
  }
  "interfaces":{
    "mesh0":{
      "mesh_retry_timeout":"100",
      "mesh_confirm_timeout":"100",
      "mesh_holding_timeout":"100",
      "mesh_max_peer_links":"150",
      "mesh_max_retries":"3",
      "mesh_ttl":"31",
      "mesh_element_ttl":"31",
      "mesh_auto_open_plinks":"0",
      "mesh_hwmp_max_preq_retries":"4",
      "mesh_path_refresh_time":"1000",
      "mesh_min_discovery_timeout":"100",
      "mesh_hwmp_active_path_timeout":"5000",
      "mesh_hwmp_preq_min_interval":"10",
      "mesh_hwmp_net_diameter_traversal_time":"50",
      "mesh_hwmp_rootmode":"3",
      "mesh_hwmp_rann_interval":"5000",
      "mesh_gate_announcements":"1",
      "mesh_fwding":"1",
      "mesh_sync_offset_max_neighor":"50",
      "mesh_rssi_threshold":"-80",
      "mesh_hwmp_active_path_to_root_timeout":"6000",
      "mesh_hwmp_root_interval":"5000",
      "mesh_hwmp_confirmation_interval":"2000",
      "mesh_power_mode":"active",
      "mesh_awake_window":"10",
      "mesh_plink_timeout":"0",
      "mesh_connected_to_gate":"0",
      "mesh_nolearn":"0",
      "mesh_connected_to_as":"0",
      "mesh_id":"Homemesh",
      "device":"radio0",
      "channel":"36",
      "active_peers":"3"
    }
  }
}



and iw dev mesh0 mpath dump

DEST ADDR         NEXT HOP          IFACE       SN      METRIC  QLEN    EXPTIME         DTIM    DRET    FLAGS   HOP_COUNT       PATH_CHANGE
8c:10:d4:16:29:02 8c:10:d4:16:29:02 mesh0       10979   17      0       5732    100     0       0x15    1       12
8c:10:d4:16:29:03 8c:10:d4:16:29:03 mesh0       5875    1354    0       5736    0       0       0x15    1       97
8c:10:d4:16:29:04 8c:10:d4:16:29:02 mesh0       11102   200     0       5664    200     1       0x15    2       221
root@Mesh1:/# 

Recent 22.03 builds for the BT Hub 5A, both master and rc4 tend to frequently crash during boot , so can take a while to boot successfully.

The larger the size of the firmware, them more unstable booting seems to be.

I managed to build a version of 22.03rc4 which I can update from the repositories that boots reliably (so far) by omitting LUCI and most of the packages, and using opkg to install them.

I created a long list of opkg commands listing the modules I was missing, which I copy and pasted in the shh terminal. I had actually intended to first try only leaving luci and just a couple of the larger packages out, but messed up.

With a bit of luck you could just use an image builder and leave enough packages out to get it to boot first time. Or maybe a snapshot without luci might be stable.

See my post here:- OpenWrt 22.03.0-rc4 fourth release candidate - #103 by mjs

I took a look at the system logs of my 3 routers, no crashes, but the one with 21.x on it does show regular hardware restarts for ath10k_pci

Tue Jul  5 11:47:54 2022 kern.warn kernel: [ 5365.256727] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Tue Jul  5 11:47:54 2022 kern.warn kernel: [ 5365.262699] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 1, skipped old beacon
Tue Jul  5 11:47:54 2022 kern.warn kernel: [ 5365.359127] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Tue Jul  5 11:47:54 2022 kern.warn kernel: [ 5365.365100] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 1, skipped old beacon
Tue Jul  5 11:47:57 2022 kern.info kernel: [ 5368.106720] ieee80211 phy0: Hardware restart was requested
Tue Jul  5 11:47:58 2022 kern.info kernel: [ 5369.425357] ath10k_pci 0000:02:00.0: device successfully recovered

Thanks for the help and info, I feel as though I'm making progress and the mesh is much more stable so far at least.

I can live with the flakey booting on one of the meshnodes for now.

Just need confirmation that there's nothing seriously wrong with my config before moving onto the next phase.

My next step is to build a new master node with VDSL and vectoring so I can dump my existing vodafone modem / router / dmz etc.

Regards Tim

So I turned on 802.11r and checked that my laptop switched to the nearest AP ok - happy days !

I also tried out VDSL with the expectation that the latest build with vectoring would help with line stability - sadly it didn't with re-syncs happening frequently - not too surprising given our distance from the cabinet.

So I reverted to using the Vodafone modem / router with a DMZ for the mesh. So far seems very stable.

Thanks to everyone who helped me on this journey !

Regards Tim

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.