Improving Documentation and better understanding it

Hello,

I've been trying to get mesh11sd working (but all hell breaks loose when I turn it on... the br-lan ridge keeps getting reinitialized)

So here are some "definitions" and what I understand of 802.11s meshes and their mesh nodes

--- = wired connection s s s = 802.11s mesh connection ax ac n g b = standard wifi connection

[ ] = optional

 Upstream >>> Portal [Gateway] Node [>>> Downstream]
                    |
                    |         Peer Node     Peer Node    Gateway Node >>> Downstream
                    |s s s s s s s|s s s s s s s|s s s s s s s s|
                    |                           |
                    |         Peer Node         |
                    |s s s s s s s|s s s s s s s|
                                  |
                                  |      Gateway Node >>> Downstream
                                  |s s s s s s s|

Upstream can be:

[ISP|---][---|Router|---|] on different ip network than mesh (i.e. Non ridged Portal Node that hosts DHCP server for the mesh nodes and their Downstream)]
```
ISP|---Public ipv4/ipv6---|Portal Node|s s s s s 192.168.3.0/24
```
```
Router|--- 192.168.1.0/24---|Portal Node|s s s s s 192.168.2.0/24
```

[ISP|---][---|Router|---] on the same ip network and hosting DHCP for the mesh nodes and their downstream (i.e. portal wired to Upstream through its br-lan interface i.e. Bridged Portal Node]

                              Portal Node (10.0.0.2)
ISP CGNAT (10.0.0.1)|--- 10.0.0.0/24 ---|
                                    |s s s 10.0.0.0/24 s s s

                                 Portal Node (192.168.2.2)
Router (192.168.2.1)|--- 192.168.2.0/24 ---|
                                       |s s s 192.168.2.0/24 s s s

Downstream can be:

Wireless Clients or Wired clients|routers on different ip network if Gateway Node is non bridged

s s s|(192.168.1.4) Gateway Node (192.168.2.1)|ax ac n g b 192.168.2.0/24 ax ac n g b|wifi Client (192.168.2.2)
                                          |--- 192.168.2.0/24 ---|(192.168.2.3) wired Client

Wireless Clients or Wired clients|routers on same ip network if Gateway Node is bridged

         Gateway Node (192.168.2.4)
192.168.2.0/24 s s s|
                |ax ac n g b 192.168.2.0/24 ax ac n g b|wifi Client (192.168.2.5)
                |--- 192.168.2.0/24 ---|(192.168.2.6) wired Client

I've been trying to understand the documentation of the setup section and get the feeling (but maybe I haven't understood in which case the documentation is less dummy proof than I hoped ;-):

if auto_config=1

if portal_detect=1 mesh11sd works for 3 cases:

1. Non bridged Portal [Gateway] Node (i.e. with internet (or upstream) on wan interface (plugged in wan device) and with br-lan containing a wireless device in 802.11s mode, [a lan device,] [a wireless devices in AP mode]. For portal nodes mesh11sd will set up dhcp v4 server handing out ipv4 to the devices on the mesh (or connected through AP or ethernet cables to the gateway nodes of the mesh

                                                       [|ax ac n g b 192.168.1.0/24 ax ac n g b|Wifi Device (192.168.1.5)]
                                                        |
ISP|---Public ipv4/ipv6---|(public ip) Portal Node (192.168.1.1)|s s s 192.168.1.0/24 s s s|(192.168.1.2) Peer Node
                                                        |s s s 192.168.1.0/24 s s s|(192.168.1.3) Gateway Node
                                                        |
                                                       [|--- 192.168.1.0/24 ---|(192.168.1.4)Ethernet Device]
                                                       [|--- 192.168.1.0/24 ---|(192.168.1.6)Ethernet Device]

2. Peer Node (i.e. with just a wireless device in 802.11s mode)

                                          Peer Node (192.168.2.2)    Peer Node (192.168.2.3)
Portal Node (192.168.2.1)| s s s 192.168.2.0/24 s s s |s s s 192.168.2.0/24 s s s|s s s 192.168.2.0/24 s s s|(192.168.2.4) GateWay Node
                                              |
                                              |
                                              | s s s 192.168.2.0/24 s s s |(192.168.2.5) Gateway Node

3. Bridged Gateway Node (i.e. with a wireless device in AP mode and/or with others devices plugged into its lan device ports and with br-lan interface containing lan device, wireless device in AP mode and wireless device in 802.11s mode)

                                          Peer Node (192.168.2.2)  GateWay Node (192.168.2.3)
Portal Node (192.168.2.1)| s s s 192.168.2.0/24 s s s |s s s 192.168.2.0/24 s s s|
                 |                                                       |ax ac n g b 192.168.2.0/24 ax ac n g b|(192.168.2.5) wifi client
                 |                                                       |
                 |                    Gateway Node (192.168.2.4)         |--- 192.168.2.0/24 ---|(192.162.2.6) wired Client
                 | s s s 192.168.2.0/24 s s s|
                                             |ax ac n g b 192.168.2.0/24 ax ac n g b|(192.168.2.5) wifi client
                                             |
                                             |--- 192.168.2.0/24 ---|(192.162.2.6) wired Client

if portal_detect=0 mesh11sd should to handle a Bridged Portal [Gateway] Node (ie. portal node where wan device, lan device and all wirelesss devices are bridged in br-lan interface and all DHCP (v4 or v6) and IPV6 RA is turned off (as in a dumb AP)

                           Portal Node (192.168.1.2)
Router(192.168.1.1)|--- 192.168.1.0/24---|
                                 |s s s 192.168.1.0/24 s s s|(192.168.1.3) Peer Node
                                 |s s s 192.168.1.0/24 s s s|(192.168.1.4) Gateway Node
                                 |
                                 |ax ac n g b 192.168.1.0/24 ax ac n g b|(192.168.1.5) Wifi Device
                                 |
                                 |--- 192.168.1.0/24 ---|(192.168.1.6)Ethernet Device
                                 |--- 192.168.1.0/24 ---|(192.168.1.7)Ethernet Device

mesh11sd will use the parameters imposed in its mesh_params configuration file (or their default values)
if auto_config=0 meshsd will only dynamiccally verify and set the parameters defined in the mesh_params section of the configuration file (or their default values if not defined)

Concerning the mesh_params from reading the openwrt formums and your recommednations/answers to others I've understood that:

all mesh nodes should have
- mesh_gate_announcements=1
- mesh_rssi_threshold seet to something reasonnable (and not 0)
- mesh_fwding=1
a Portal [Gateway] Node should have
- mesh_hwmp_rootmode=4
- mesh_connected_to_as=1
- [mesh_connected_to_gate=1]
a Gateway Node should have
- mesh_hwmp_rootmode=0
- mesh_connected_to_gate=1
a Peer Nodes have
- mesh_hwmp_rootmode=2

I'm not sure I understand what a root mesh is... is it just a portal

Please feel free to correct my misunderstandings, and if ever I understood things feel free to reuse (my dummy wordings and examples) in the documentation

Now back to my case... I'm testing 2 Linksys A03 (using non-ct ath10k driver and firmawares (as per the instrucitons) on self built openwrt-25.03 branch (so as to have access to all channels patch that is not in 23.05.3)

The first as a Bridged Portal Gateway Node, so using
- auto_config=0
- portal_detect=0
- mesh_gate_announcements=1
- mesh_rssi_threshold=-80
- mesh_fwding=1
- mesh_hwmp_rootmode=4
- mesh_connected_to_as=1
- mesh_connected_to_gate=1
The second as a Bridged Gateway Node, so using
- auto_config=0 [could have used 1 but am staying coherent with the other in terms of auto configuration)
- portal_detect=1
- mesh_gate_announcements=1
- mesh_rssi_threshold=-80
- mesh_fwding=1
- mesh_hwmp_rootmode=4
- mesh_connected_to_gate=1

As soon as I start mesh11sd on any node (including both) the connection keeps going Seeing disconnects for "reason 55" and the holme bridge being taken down and then brought ack up Seeing alos messages that nft-bridge module is not installed although it is !!!

@dwardor mesh11sd has 2 basic modes, auto-config and manual-config.

There are various issues with releases less than v4.0.0.

Unfortunately due to a bug in v3.x.x, manual mode does not completely turn off auto-config. This can then cause "all havoc" as you say, if you have done any manual mesh configuration.
On some architectures, DSA has not been fully, or in some instances not been correctly, implemented. This in turn causes crashes in wireless drivers when a mesh interface comes up.
Problems with some wireless drivers cause ip routing to fail even though the layer 2 mesh backhaul is up and running. The mt798x range is particularly effected by this. Work is apparently being done elsewhere on OpenWrt master to fix this.
On kernel v6.x.x (current snapshot), backports from higher kernel versions can cause segfaults and other crashes on some chipsets eg mt76x8 range.

To mitigate all these problems, much refactoring has been done on mesh11sd and is currently on v4.0.0-beta-9

If you are interested in testing I can post the ipk here. Note it is all ash script so is architecture independent.

@dwardor

Please feel free to correct my misunderstandings,

FYI - I will clarify "Meshnode Types"....

Portal Node: A mesh portal will usually have an upstream connection (eg an Internet connection). It will autoconfigure or be configured as a router supporting both ipv4 and ipv6, serving ipv4 dhcp and dns for downstream devices. It will participate in the mesh HWMP at level 4 and advertises mesh_connected_to_as=1 if the upstream link is up, and advertises mesh_connected_to_as=0 if the upstream link is down. If it also supports an access point it will advertise mesh_connected_to_gate=1 in the mesh station information field. If it does NOT support an access point it will advertise mesh_connected_to_gate=0 in the mesh station information field.
Peer Node: A mesh peer will have ipv4 dhcp disabled and be configured as an ipv4 dhcp client. It will participate in the mesh HWMP at level 2 and advertises mesh_connected_to_as=0 in the mesh station information field. It will advertise mesh_connected_to_gate=0 in the mesh station information field, unless it is also a "Gate" This is the mesh equivalent of the "Dumb AP".
Gateway Node (or "Gate"): If a portal or peer meshnode is connected to a separate network infrastructure such as a wireless network or downstream router, is is a gateway to that separate infrastructure. For example if a meshnode also has a built in access point, it will be a gateway. It will advertise mesh_connected_to_gate=1 in the mesh station information field. It will participate in the mesh HWMP at level 2, unless it is also a portal, in which case it will participate at level 4.
Gateway Leech Node (configurable in v4 onwards): This is similar to a Gateway "Peer" Node, is connected to the mesh backhaul, but does not contribute to it. It does not participate in the mesh HWMP (is set to level 0) and does not forward peer packets.

Thanks you very much for these clarifications (and confirming mesh11sd 3.1.0 and 3.1.1 tested both) have manual configuration issues (and that I wasn't going crazy).

I've been digging since yesterday and find interesting that your Node Types definition are not coherent with https://www.cwnp.com/wp-content/uploads/pdf/802.11s_mesh_networking_v1.0.pdf which suggests:

Mesh Station : Mesh Node (i.e. a Node participating in the 802.11s Mesh)
- Mesh Gate : Mesh Station that also translates to "anything other than a 802.11s Distribution System" i.e. to 802.11ax|ac|g|n wireless or to ethernet
  - Mesh Portal : Mesh Gate that translates to "non-802.11 Distribution System" i.e. to ethernet (whether upstream or downstream)
  - Mesh AP : Mesh Gate that translates to "non-mesh 802.11 Distribution Systems" i.e. to 802.11ax|ac|g|n wireless
- Mesh Peer : a Mesh Station that is/does nothing more ;-) as illustrated by the folling image taken from the referenced whitepaper

So a Gate connected to a router (whether downstream or upstream, bridged or unbridged) by ethernet would be a Portal. That white paper also states that it is common (good practice ?) to set mesh_hwmp_rootmode=4 on Mesh Gates (ie. Mesh Portals and Mesh APs per their definition) [By the way if I manually set mesh_hwmp_rootmode=0 on my Mesh AP (serving as a repeater) using iw... it gets set... but something else (the driver ?) changes it back to 4 within a few seconds (and its not mesh1sd as its not running) which is coherent with the fact it is a MeshAP so should be set to 4 !]

--> what is your take on this node type definition and where to set mesh_hwmp_rootmode=4 incoherence ? That ref is old or just wrong ?

Whatever your answer I think adding the clarifications (or a modified version if necessary) in the Documentation would make things clearer for all !

Concerning what mesh11sd does:

It[Portal] will autoconfigure

In case portal_detect=0 ? Using LuCi/user prefconfigured br-lan bridge interface having all devices (i.e. my "Bridged Portal AP Gate" ?

or be configured as a router supporting both ipv4 and ipv6, serving ipv4 dhcp and dns for downstream devices.

In case portal_detect=1 ?

If you are interested in testing I can post the ipk here. Note it is all ash script so is architecture independent.

Yes willing to help test ! And redo some of my examples from first comment to use in documentation and explicit what mesh11sd handles when using what setup parameters !

@dwardor

Thank you for your continued input. I will post the installable ipk here.

your Node Types definition are not coherent with https://www.cwnp.com/wp-content/uploads/pdf/802.11s_mesh_networking_v1.0.pdf

"not coherent" is a very strange statement.

You do realise that the paper referred to was published as a "newsletter" type of document by a commercial organisation when the IEEE finally published the 802.11s amendment to 802.11 standards. The paper was written in 2011 and there has been no known update to it since. Effectively the author wrote an article having read the amendment, with the aim of generating interest. Take it with a fairly large pinch of salt!

That white paper also states that it is common (good practice ?) to set mesh_hwmp_rootmode=4 on Mesh Gates

The link you posted does not mention mesh_hwmp_rootmode anywhere..... so I do not know where you got that from, but not to worry.

Figure 2 of the paper shows a generic mesh layout. The paper uses the term "Mesh STA" to mean "Mesh Peer" as it is in the mesh11sd context.

So a Gate connected to a router (whether downstream or upstream, bridged or unbridged) by ethernet would be a Portal.

A "Router" is, eg a commodity item sold as a routing device with wan and lan ports and one or more physical wireless devices. So we need to use terms that do not lead to confusion:

IP Router - what we normally expect - routes packets at layer 3 according to an IP routing table or protocol
MAC Router - routes packets at layer 2 according to the mesh mac-routing protocol, HWMP
MeshNode - AKA MAC Router

That said we can look in more detail about meshnode types.

A Portal is a special type of meshnode. Its properties will be:

It connects to a mesh backhaul
It connects to an upstream layer 3 infrastructure
It provides IP4 and IP6 routing between the upstream layer 3 infrastructure and the layer 2 mesh backhaul
It supports IP4 dhcp and dns services for the mesh backhaul. This means there would normally be only one IP4 Portal for a mesh backhaul to prevent dhcp clashes.
It supports IP6 traffic to and from the backhaul via dhcp6 and/or multicast RA solicitation.
It can support a downstream link to a further infrastructure such as a wifi network, an ethernet network, another ip-router or even another separate mesh backhaul. If it does this, it is also known as a "Gate" or "gateway" to the other infrastructure.

Lets look at one of your questions:

In case portal_detect=0 ?

Portal detect can have 3 values and is only valid when auto_config is enabled: 0 meaning force Portal mode, as described above; 1 meaning detect if the node is to be a portal or not; 2 force into non-portal "peer" mode (mesh equivalent of Dumb AP)

Note: Everything I discuss here is applicable to mesh11sd v4 onwards unless stated otherwise.

_By default in v4.0.0, auto_config is DISABLED_

Tar-gz of mesh11sd_4.0.0-beta-9_all.ipk : mesh11sd.tar.gz

Just tested.

I Started mesh11sd4beta on the the portal (and not on the gate) and all hell still breaks loose :-(

On both Portal and Gate:

5ghzlow is the mesh interface device (using radio2)
5ghzhigh is the AP interface device (using radio0)
2.4ghz is an unactivated (for now) AP interface device (using radio1)
mesh11sd configuration is stock (including auto_config=0) except :
- option debuglevel '3'
- option mesh_basename '5ghzlow'
- option mesh_rssi_threshold '-80'
- option mesh_max_peer_links '16'
- option mesh_hwmp_rootmode '4'

kmod_nft-bridge is installed on both Portal and Gate

# opkg list-installed | grep kmod-nft-bridge
kmod-nft-bridge - 5.15.155-1

Gate for now has nothing plugged into its ethernet (whereas portal does)

log on Portal are the following:

>logread -f
Fri May 10 23:43:31 2024 daemon.notice mesh11sd[15941]: 5ghzlow is not up - giving up for now.
Fri May 10 23:43:36 2024 daemon.notice mesh11sd[15941]: 5ghzlow is not up - giving up for now.
Fri May 10 23:43:37 2024 daemon.notice netifd: radio0 (19197): Command failed: ubus call hostapd config_set { "phy": "phy0", "config":"/var/run/hostapd-phy0.conf", "prev_config": "/var/run/hostapd-phy0.conf.prev"} (Request timed out)
Fri May 10 23:43:37 2024 daemon.notice netifd: radio0 (19197): Device setup failed: HOSTAPD_START_FAILED
Fri May 10 23:43:37 2024 daemon.notice netifd: Wireless device 'radio0' set retry=0
Fri May 10 23:43:38 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Fri May 10 23:43:38 2024 kern.info kernel: [104545.949981] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Fri May 10 23:43:38 2024 kern.info kernel: [104545.950264] br-lan: port 4(5ghzhigh) entered blocking state
Fri May 10 23:43:38 2024 kern.info kernel: [104545.955779] br-lan: port 4(5ghzhigh) entered listening state
Fri May 10 23:43:38 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Fri May 10 23:43:39 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Fri May 10 23:43:39 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Fri May 10 23:43:39 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Fri May 10 23:43:39 2024 kern.info kernel: [104546.615988] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Fri May 10 23:43:39 2024 kern.info kernel: [104546.616331] br-lan: port 3(5ghzlow) entered blocking state
Fri May 10 23:43:39 2024 kern.info kernel: [104546.621498] br-lan: port 3(5ghzlow) entered listening state
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=7 id_str=]
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=7
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Fri May 10 23:43:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Fri May 10 23:43:40 2024 daemon.info mesh11sd[15941]: -------------------------------------------------------------------------------------------------------------------------
Fri May 10 23:43:40 2024 daemon.info mesh11sd[15941]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Fri May 10 23:43:40 2024 daemon.info mesh11sd[15941]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Fri May 10 23:43:40 2024 daemon.info mesh11sd[15941]: -------------------------------------------------------------------------------------------------------------------------
Fri May 10 23:43:40 2024 daemon.info mesh11sd[15941]: Path to station [ 30:23:03:99:bd:7d ] is stable
Fri May 10 23:43:40 2024 daemon.debug mesh11sd[15941]: checkinterval 10 seconds
Fri May 10 23:43:47 2024 kern.info kernel: [104554.219255] br-lan: port 4(5ghzhigh) entered learning state
Fri May 10 23:43:47 2024 kern.info kernel: [104554.859257] br-lan: port 3(5ghzlow) entered learning state
Fri May 10 23:43:51 2024 daemon.debug mesh11sd[15941]: interface 5ghzlow is up
Fri May 10 23:43:51 2024 daemon.info mesh11sd[15941]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Fri May 10 23:43:51 2024 daemon.info mesh11sd[15941]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Fri May 10 23:43:51 2024 daemon.info mesh11sd[15941]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Fri May 10 23:43:51 2024 daemon.info mesh11sd[15941]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Fri May 10 23:43:51 2024 daemon.debug mesh11sd[15941]: Disconnecting nodes
Fri May 10 23:43:51 2024 daemon.info sh[15941]: 'radio1' is disabled
Fri May 10 23:43:52 2024 daemon.info sh[15941]: 'radio1' is disabled
Fri May 10 23:43:52 2024 daemon.notice hostapd: Set new config for phy phy0:
Fri May 10 23:43:52 2024 daemon.notice hostapd: Remove interface 'phy0'
Fri May 10 23:43:52 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Fri May 10 23:43:52 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Fri May 10 23:43:52 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Fri May 10 23:43:52 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Fri May 10 23:43:52 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Fri May 10 23:43:52 2024 kern.info kernel: [104559.405644] device 5ghzhigh left promiscuous mode
Fri May 10 23:43:52 2024 kern.info kernel: [104559.405970] br-lan: port 4(5ghzhigh) entered disabled state
Fri May 10 23:43:52 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Fri May 10 23:43:52 2024 kern.warn kernel: [104559.510124] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Fri May 10 23:43:52 2024 kern.warn kernel: [104559.510291] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Fri May 10 23:43:52 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:43:52 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:43:52 2024 daemon.notice hostapd: Set new config for phy phy2:
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Fri May 10 23:43:52 2024 daemon.info mesh11sd[15941]: Old value:mesh_connected_to_gate=0, Setting new value:mesh_connected_to_gate=1
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Fri May 10 23:43:52 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Fri May 10 23:43:52 2024 daemon.debug mesh11sd[15941]: node [DEST,ADDR]
Fri May 10 23:43:52 2024 daemon.debug mesh11sd[15941]: node [30:23:03:99:bd:7d,30:23:03:99:bd:7d]
Fri May 10 23:43:52 2024 daemon.notice netifd: radio0 (21178): WARNING: Variable 'data' does not exist or is not an array/object
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Fri May 10 23:43:52 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Fri May 10 23:43:52 2024 kern.warn kernel: [104559.960057] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Fri May 10 23:43:53 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Fri May 10 23:43:53 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Fri May 10 23:43:53 2024 kern.info kernel: [104560.071729] br-lan: port 3(5ghzlow) entered disabled state
Fri May 10 23:43:53 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Fri May 10 23:43:53 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Fri May 10 23:43:53 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Fri May 10 23:43:53 2024 kern.info kernel: [104560.110693] br-lan: port 3(5ghzlow) entered blocking state
Fri May 10 23:43:53 2024 kern.info kernel: [104560.110763] br-lan: port 3(5ghzlow) entered listening state
Fri May 10 23:43:53 2024 daemon.notice hostapd: Set new config for phy phy0:
Fri May 10 23:43:53 2024 kern.warn kernel: [104560.175020] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Fri May 10 23:43:53 2024 kern.warn kernel: [104560.175135] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Fri May 10 23:43:53 2024 kern.info kernel: [104560.187211] br-lan: port 3(5ghzlow) entered disabled state
Fri May 10 23:43:53 2024 kern.info kernel: [104560.249861] device 5ghzlow left promiscuous mode
Fri May 10 23:43:53 2024 kern.info kernel: [104560.249934] br-lan: port 3(5ghzlow) entered disabled state
Fri May 10 23:43:53 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:43:53 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Fri May 10 23:43:53 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Fri May 10 23:43:53 2024 daemon.notice netifd: radio0 (21178): command failed: Not supported (-95)
Fri May 10 23:43:53 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:43:53 2024 daemon.notice netifd: radio2 (21280): WARNING: Variable 'data' does not exist or is not an array/object
Fri May 10 23:43:53 2024 daemon.notice hostapd: Set new config for phy phy2:
Fri May 10 23:43:53 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:43:53 2024 daemon.notice netifd: radio2 (21280): command failed: Not supported (-95)
Fri May 10 23:43:53 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Fri May 10 23:43:54 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Fri May 10 23:43:54 2024 daemon.notice hostapd: Restart interface for phy phy0
Fri May 10 23:43:54 2024 daemon.debug mesh11sd[15941]: checkinterval 10 seconds
Fri May 10 23:43:54 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=32:23:03:2e:b0:85 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=####
Fri May 10 23:43:54 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:43:56 2024 kern.warn kernel: [104563.457443] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Fri May 10 23:43:56 2024 kern.info kernel: [104563.461988] br-lan: port 3(5ghzhigh) entered blocking state
Fri May 10 23:43:56 2024 kern.info kernel: [104563.462202] br-lan: port 3(5ghzhigh) entered disabled state
Fri May 10 23:43:56 2024 kern.info kernel: [104563.468192] device 5ghzhigh entered promiscuous mode
Fri May 10 23:43:56 2024 kern.info kernel: [104563.473776] br-lan: port 3(5ghzhigh) entered blocking state
Fri May 10 23:43:56 2024 kern.info kernel: [104563.478437] br-lan: port 3(5ghzhigh) entered listening state
Fri May 10 23:43:56 2024 kern.info kernel: [104563.484530] br-lan: port 3(5ghzhigh) entered disabled state
Fri May 10 23:43:56 2024 daemon.warn hostapd: nl80211: Failed to add interface 5ghzhigh into bridge br-lan: Resource busy
Fri May 10 23:43:56 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri May 10 23:43:56 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Fri May 10 23:43:56 2024 daemon.notice hostapd: Set new config for phy phy2:
Fri May 10 23:43:56 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:43:56 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:43:56 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:43:56 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Fri May 10 23:43:58 2024 kern.info kernel: [104565.251739] br-lan: port 4(5ghzlow) entered blocking state
Fri May 10 23:43:58 2024 kern.info kernel: [104565.251821] br-lan: port 4(5ghzlow) entered disabled state
Fri May 10 23:43:58 2024 kern.info kernel: [104565.256554] device 5ghzlow entered promiscuous mode
Fri May 10 23:43:58 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:43:58 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:43:58 2024 kern.info kernel: [104565.775662] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Fri May 10 23:43:58 2024 kern.info kernel: [104565.775954] br-lan: port 3(5ghzhigh) entered blocking state
Fri May 10 23:43:58 2024 kern.info kernel: [104565.781536] br-lan: port 3(5ghzhigh) entered listening state
Fri May 10 23:43:58 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Fri May 10 23:43:58 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Fri May 10 23:43:58 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Fri May 10 23:43:58 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Fri May 10 23:44:01 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Fri May 10 23:44:01 2024 kern.info kernel: [104568.495373] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Fri May 10 23:44:01 2024 kern.info kernel: [104568.495704] br-lan: port 4(5ghzlow) entered blocking state
Fri May 10 23:44:01 2024 kern.info kernel: [104568.500882] br-lan: port 4(5ghzlow) entered listening state
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=8 id_str=]
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=8
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Fri May 10 23:44:01 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Fri May 10 23:44:04 2024 daemon.debug mesh11sd[15941]: interface 5ghzlow is up
Fri May 10 23:44:04 2024 daemon.info mesh11sd[15941]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Fri May 10 23:44:04 2024 daemon.info mesh11sd[15941]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Fri May 10 23:44:04 2024 daemon.info mesh11sd[15941]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Fri May 10 23:44:04 2024 daemon.info mesh11sd[15941]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Fri May 10 23:44:04 2024 daemon.debug mesh11sd[15941]: Disconnecting nodes
Fri May 10 23:44:05 2024 daemon.info sh[15941]: 'radio1' is disabled
Fri May 10 23:44:05 2024 daemon.info sh[15941]: 'radio1' is disabled
Fri May 10 23:44:05 2024 daemon.notice hostapd: Set new config for phy phy2:
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Fri May 10 23:44:05 2024 daemon.notice hostapd: Set new config for phy phy0:
Fri May 10 23:44:05 2024 daemon.notice hostapd: Remove interface 'phy0'
Fri May 10 23:44:05 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Fri May 10 23:44:05 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Fri May 10 23:44:05 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Fri May 10 23:44:05 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Fri May 10 23:44:05 2024 kern.warn kernel: [104572.479867] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Fri May 10 23:44:05 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Fri May 10 23:44:05 2024 kern.warn kernel: [104572.620121] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Fri May 10 23:44:05 2024 kern.warn kernel: [104572.620282] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Fri May 10 23:44:05 2024 kern.info kernel: [104572.704445] br-lan: port 3(5ghzhigh) entered disabled state
Fri May 10 23:44:05 2024 kern.info kernel: [104572.705330] br-lan: port 4(5ghzlow) entered disabled state
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Fri May 10 23:44:05 2024 kern.info kernel: [104572.711478] device 5ghzhigh left promiscuous mode
Fri May 10 23:44:05 2024 kern.info kernel: [104572.714641] br-lan: port 3(5ghzhigh) entered disabled state
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Fri May 10 23:44:05 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Fri May 10 23:44:05 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Fri May 10 23:44:05 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Fri May 10 23:44:05 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Fri May 10 23:44:05 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:44:05 2024 kern.warn kernel: [104572.939644] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Fri May 10 23:44:05 2024 kern.warn kernel: [104572.939760] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Fri May 10 23:44:05 2024 kern.info kernel: [104572.951741] br-lan: port 4(5ghzlow) entered disabled state
Fri May 10 23:44:06 2024 kern.info kernel: [104573.020113] device 5ghzlow left promiscuous mode
Fri May 10 23:44:06 2024 kern.info kernel: [104573.020194] br-lan: port 4(5ghzlow) entered disabled state
Fri May 10 23:44:06 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:44:06 2024 daemon.info mesh11sd[15941]: Failed to get current value of mesh_connected_to_gate, mesh interface not established.
Fri May 10 23:44:06 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:44:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Fri May 10 23:44:06 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:44:06 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Fri May 10 23:44:06 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Fri May 10 23:44:06 2024 daemon.notice netifd: radio2 (22022): WARNING: Variable 'data' does not exist or is not an array/object
Fri May 10 23:44:06 2024 daemon.notice netifd: radio0 (22024): WARNING: Variable 'data' does not exist or is not an array/object
Fri May 10 23:44:06 2024 daemon.notice hostapd: Set new config for phy phy2:
Fri May 10 23:44:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:44:06 2024 daemon.notice hostapd: Set new config for phy phy0:
Fri May 10 23:44:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Fri May 10 23:44:06 2024 daemon.notice netifd: radio2 (22022): command failed: Not supported (-95)
Fri May 10 23:44:06 2024 daemon.notice netifd: radio0 (22024): command failed: Not supported (-95)
Fri May 10 23:44:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:44:07 2024 daemon.debug mesh11sd[15941]: checkinterval 10 seconds
Fri May 10 23:44:07 2024 daemon.notice hostapd: Set new config for phy phy2:
Fri May 10 23:44:07 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Fri May 10 23:44:08 2024 kern.info kernel: [104575.757899] br-lan: port 3(5ghzlow) entered blocking state
Fri May 10 23:44:08 2024 kern.info kernel: [104575.757958] br-lan: port 3(5ghzlow) entered disabled state
Fri May 10 23:44:08 2024 kern.info kernel: [104575.762740] device 5ghzlow entered promiscuous mode
Fri May 10 23:44:08 2024 kern.info kernel: [104575.772469] device 5ghzlow left promiscuous mode
Fri May 10 23:44:08 2024 kern.info kernel: [104575.773333] br-lan: port 3(5ghzlow) entered disabled state
Fri May 10 23:44:08 2024 kern.info kernel: [104575.821987] br-lan: port 3(5ghzlow) entered blocking state
Fri May 10 23:44:08 2024 kern.info kernel: [104575.822048] br-lan: port 3(5ghzlow) entered disabled state
Fri May 10 23:44:08 2024 kern.info kernel: [104575.826757] device 5ghzlow entered promiscuous mode
Fri May 10 23:44:08 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:44:08 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Fri May 10 23:44:08 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Fri May 10 23:44:08 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Fri May 10 23:44:08 2024 daemon.notice hostapd: Restart interface for phy phy0
Fri May 10 23:44:08 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Fri May 10 23:44:08 2024 daemon.notice netifd: Interface 'lan6' has lost the connection
Fri May 10 23:44:09 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=32:23:03:2e:b0:85 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=####
Fri May 10 23:44:09 2024 daemon.notice netifd: lan (16876): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Fri May 10 23:44:09 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:44:10 2024 daemon.warn odhcp6c[16552]: Server returned message status 'Success (success)'
Fri May 10 23:44:11 2024 kern.warn kernel: [104578.397027] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Fri May 10 23:44:11 2024 daemon.notice netifd: Interface 'lan' is now up
Fri May 10 23:44:11 2024 kern.info kernel: [104578.407642] br-lan: port 4(5ghzhigh) entered blocking state
Fri May 10 23:44:11 2024 kern.info kernel: [104578.407714] br-lan: port 4(5ghzhigh) entered disabled state
Fri May 10 23:44:11 2024 kern.info kernel: [104578.412869] device 5ghzhigh entered promiscuous mode
Fri May 10 23:44:11 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri May 10 23:44:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Fri May 10 23:44:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Fri May 10 23:44:11 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Fri May 10 23:44:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Fri May 10 23:44:11 2024 daemon.notice netifd: lan (16876): udhcpc: sending renew to server 192.168.2.1
Fri May 10 23:44:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=9 id_str=]
Fri May 10 23:44:11 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Fri May 10 23:44:11 2024 daemon.notice netifd: lan (16876): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Fri May 10 23:44:11 2024 daemon.notice netifd: Interface 'lan6' is now up

Next test: I activated mesh11sd on the gate (while it was still running on the ) --> hell was still loose (and logs on Portal looked identical)

Final test : I deactivated mesh11sd on the Portal (while still running on the Gate) --> the connection got up and stayed up. logread on Gate says:

Sat May 11 00:47:41 2024 daemon.debug mesh11sd[2795]: node [DEST,ADDR]
Sat May 11 00:47:41 2024 daemon.debug mesh11sd[2795]: node [30:23:03:2d:b0:87,30:23:03:2d:b0:87]
Sat May 11 00:47:41 2024 daemon.info mesh11sd[2795]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 00:47:41 2024 daemon.info mesh11sd[2795]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 00:47:41 2024 daemon.info mesh11sd[2795]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 00:47:41 2024 daemon.info mesh11sd[2795]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 00:47:42 2024 daemon.info mesh11sd[2795]: Path to station [ 30:23:03:2d:b0:87 ] is stable
Sat May 11 00:47:42 2024 daemon.debug mesh11sd[2795]: checkinterval 10 seconds
Sat May 11 00:47:52 2024 daemon.debug mesh11sd[2795]: interface 5ghzlow is up
Sat May 11 00:47:53 2024 daemon.debug mesh11sd[2795]: node [DEST,ADDR]
Sat May 11 00:47:53 2024 daemon.debug mesh11sd[2795]: node [30:23:03:2d:b0:87,30:23:03:2d:b0:87]
Sat May 11 00:47:53 2024 daemon.info mesh11sd[2795]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 00:47:53 2024 daemon.info mesh11sd[2795]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 00:47:53 2024 daemon.info mesh11sd[2795]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 00:47:53 2024 daemon.info mesh11sd[2795]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 00:47:54 2024 daemon.info mesh11sd[2795]: Path to station [ 30:23:03:2d:b0:87 ] is stable
Sat May 11 00:47:54 2024 daemon.debug mesh11sd[2795]: checkinterval 10 seconds

Hope some of this can help

@dwardor Manual mode (autoconfig=0) means you have to configure all_ of the wireless yourself. From your logs it looks, initially, very much like your configuration is broken. But is it. At the end of the log snippet it says the mesh is up.... The manual mesh configuration should bring up a mesh interface without mesh11sd even being installed. Is this the case?

As I mentioned earlier, some wireless driver/dsa/kernel-versions need specific workarounds that mesh11sd would put into place. In manual mode you will have to do this yourself.

I am not saying this is actually the problem here but it could be. To find out we need the detail of your hardware, firmware version and contents of your config files BEFORE mesh11sd.

For configs, first do:

service mesh11sd stop
revert mesh11sd
uci revert wireless
uci revert network
uci revert dhcp
uci revert system

Then show the outputs of:

uci show wireless

uci show network and uci show dhcp

Also don't forget to list the hardware make, model and OpenWrt Version.

Sat May 11 00:47:53 2024 daemon.info mesh11sd[2795]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?

This means, literally as it says, Unable to add nftables rule(s). It suggests, as the most common reason, that kmod-nft-bridge is not installed but can indicate something more serious is wrong with the nft ruleset.

To check this, please also show the output of: nft list ruleset

You could also capture the mesh11sd startup logs with: service mesh11sd restart; logread -f

stopped mesh11sd and reverted

service mesh11sd stop
uci revert mesh11sd
uci revert wireless
uci revert network
uci revert dhcp
uci revert system

I am running self built (using non -ct ath10k driver and firmwares) openwrt-23.05-snapshot-r23854-06be957f86-ipq40xx-generic-linksys_whw03v2-squashfs-sysupgrade.bin on my 2 Linksys A03v2 (marketing name of WHW03v2 for Apple customers):

a03_1 is plugged into main ddwrt router on its [a03_1's] wan port (that is bridged to lan in br-lan cf. network config below)
a03_2 is the repeater with 802.11s mesh backhaul

So here is my manually set mesh config (identical on both units) that works (as long as mesh11sd is not started) as illustrated by the picture below

wireless config : uci show wireless

uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.path='soc/40000000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
wireless.radio0.band='5g'
wireless.radio0.htmode='VHT80'
wireless.radio0.cell_density='0'
wireless.radio0.country='FR'
wireless.radio0.frag='2346'
wireless.radio0.rts='2347'
wireless.radio0.beacon_int='250'
wireless.radio0.channel='100'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='airdwardo_5GHz'
wireless.default_radio0.encryption='psk2+ccmp'
wireless.default_radio0.ifname='5ghzhigh'
wireless.default_radio0.dtim_period='1'
wireless.default_radio0.key='REDACTED'
wireless.default_radio0.ieee80211r='1'
wireless.default_radio0.mobility_domain='DEAD'
wireless.default_radio0.ft_over_ds='0'
wireless.default_radio0.ft_psk_generate_local='1'
wireless.default_radio0.ieee80211k='1'
wireless.default_radio0.bss_transition='1'
wireless.default_radio0.time_advertisement='2'
wireless.default_radio0.time_zone='CET-1CEST,M3.5.0,M10.5.0/3'
wireless.default_radio0.wnm_sleep_mode='1'
wireless.default_radio0.wnm_sleep_mode_no_keys='1'
wireless.default_radio0.proxy_arp='1'
wireless.default_radio0.disabled='0'
wireless.radio1=wifi-device
wireless.radio1.type='mac80211'
wireless.radio1.path='platform/soc/a000000.wifi'
wireless.radio1.band='2g'
wireless.radio1.htmode='HT20'
wireless.radio1.country='FR'
wireless.radio1.cell_density='0'
wireless.radio1.frag='2346'
wireless.radio1.rts='2347'
wireless.radio1.beacon_int='400'
wireless.radio1.channel='auto'
wireless.radio1.disabled='1'
wireless.default_radio1=wifi-iface
wireless.default_radio1.device='radio1'
wireless.default_radio1.network='lan'
wireless.default_radio1.mode='ap'
wireless.default_radio1.ssid='airdwardor'
wireless.default_radio1.encryption='psk2+ccmp'
wireless.default_radio1.key='REDACTED'
wireless.default_radio1.ieee80211r='1'
wireless.default_radio1.mobility_domain='DEAD'
wireless.default_radio1.ft_over_ds='0'
wireless.default_radio1.ft_psk_generate_local='1'
wireless.default_radio1.ieee80211k='1'
wireless.default_radio1.ifname='2.4ghz'
wireless.default_radio1.dtim_period='1'
wireless.default_radio1.bss_transition='1'
wireless.default_radio1.time_advertisement='2'
wireless.default_radio1.time_zone='CET-1CEST,M3.5.0,M10.5.0/3'
wireless.default_radio1.wnm_sleep_mode='1'
wireless.default_radio1.wnm_sleep_mode_no_keys='1'
wireless.default_radio1.proxy_arp='1'
wireless.default_radio1.disabled='1'
wireless.radio2=wifi-device
wireless.radio2.type='mac80211'
wireless.radio2.path='platform/soc/a800000.wifi'
wireless.radio2.band='5g'
wireless.radio2.htmode='VHT80'
wireless.radio2.cell_density='0'
wireless.radio2.country='FR'
wireless.radio2.frag='2346'
wireless.radio2.rts='2347'
wireless.radio2.beacon_int='250'
wireless.radio2.channel='36'
wireless.default_radio2=wifi-iface
wireless.default_radio2.device='radio2'
wireless.default_radio2.network='lan'
wireless.default_radio2.mode='mesh'
wireless.default_radio2.encryption='sae'
wireless.default_radio2.ifname='5ghzlow'
wireless.default_radio2.dtim_period='1'
wireless.default_radio2.key='REDACTED'
wireless.default_radio2.bss_transition='1'
wireless.default_radio2.time_advertisement='2'
wireless.default_radio2.time_zone='CET-1CEST,M3.5.0,M10.5.0/3'
wireless.default_radio2.wnm_sleep_mode='1'
wireless.default_radio2.wnm_sleep_mode_no_keys='1'
wireless.default_radio2.proxy_arp='1'
wireless.default_radio2.mesh_id='meshdwardo_5GHz'
wireless.default_radio2.mesh_fwding='1'
wireless.default_radio2.mesh_rssi_threshold='-79'

network config: uci show network

network.loopback=interface
network.loopback.device='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fddc::/64'
network.@device[0]=device
network.@device[0].name='br-lan'
network.@device[0].type='bridge'
network.@device[0].ports='lan' 'wan'
network.@device[0].bridge_empty='1'
network.lan=interface
network.lan.device='br-lan'
network.lan.proto='dhcp'
network.lan6=interface
network.lan6.proto='dhcpv6'
network.lan6.device='br-lan'
network.lan6.reqaddress='try'
network.lan6.reqprefix='auto'
network.lan6.force_link='1'
network.safe=interface
network.safe.proto='static'
network.safe.device='br-lan'
network.safe.ipaddr='192.168.3.1'
network.safe.netmask='255.255.255.0'
network.safe.delegate='0'

dhcp config: uci show dhcp

dhcp.@dnsmasq[0]=dnsmasq
dhcp.@dnsmasq[0].rebind_protection='0'
dhcp.@dnsmasq[0].cachesize='1000'
dhcp.@dnsmasq[0].readethers='1'
dhcp.@dnsmasq[0].leasefile='/tmp/dhcp.leases'
dhcp.@dnsmasq[0].resolvfile='/tmp/resolv.conf.d/resolv.conf.auto'
dhcp.@dnsmasq[0].localservice='1'
dhcp.@dnsmasq[0].ednspacket_max='1232'
dhcp.@dnsmasq[0].logfacility='-'
dhcp.@dnsmasq[0].quietdhcp='1'
dhcp.@dnsmasq[0].localise_queries='1'
dhcp.@dnsmasq[0].expandhosts='1'
dhcp.@dnsmasq[0].boguspriv='0'
dhcp.lan=dhcp
dhcp.lan.interface='lan'
dhcp.lan.start='100'
dhcp.lan.limit='150'
dhcp.lan.leasetime='12h'
dhcp.lan.dhcpv4='disabled'
dhcp.lan.dhcpv6='disabled'
dhcp.lan.ra='disabled'
dhcp.lan.ra_flags='managed-config' 'other-config'
dhcp.lan.ignore='1'
dhcp.lan.ra_default='2'
dhcp.odhcpd=odhcpd
dhcp.odhcpd.maindhcp='0'
dhcp.odhcpd.leasefile='/tmp/hosts/odhcpd'
dhcp.odhcpd.leasetrigger='/usr/sbin/odhcpd-update'
dhcp.odhcpd.loglevel='4'

mesh11sd config

uci show mesh11sd
mesh11sd.setup=mesh11sd
mesh11sd.setup.debuglevel='3'
mesh11sd.setup.mesh_basename='5ghzlow'
mesh11sd.setup.auto_config='0'
mesh11sd.mesh_params=mesh11sd
mesh11sd.mesh_params.mesh_rssi_threshold='-80'
mesh11sd.mesh_params.mesh_hwmp_rootmode='4'
mesh11sd.mesh_params.mesh_max_peer_links='16'
mesh11sd.mesh_params.mesh_fwding='1'
mesh11sd.mesh_params.mesh_gate_announcements='1'
mesh11sd.mesh_params.mesh_hwmp_rann_interval='5000'
mesh11sd.mesh_params.mesh_hwmp_root_interval='5000'
mesh11sd.mesh_params.mesh_hwmp_active_path_timeout='5000'
mesh11sd.mesh_params.mesh_hwmp_active_path_to_root_timeout='6000'
mesh11sd.mesh_params.mesh_connected_to_gate='0'

firewall ruleset: nft list ruleset

table inet fw4 {
    chain input {
            type filter hook input priority filter; policy drop;
            iifname "lo" accept comment "!fw4: Accept traffic from loopback"
            ct state established,related accept comment "!fw4: Allow inbound established and related flows"
            tcp flags syn / fin,syn,rst,ack jump syn_flood comment "!fw4: Rate limit TCP syn packets"
            iifname "br-lan" jump input_lan comment "!fw4: Handle lan IPv4/IPv6 input traffic"
            jump handle_reject
    }

    chain forward {
            type filter hook forward priority filter; policy drop;
            ct state established,related accept comment "!fw4: Allow forwarded established and related flows"
            iifname "br-lan" jump forward_lan comment "!fw4: Handle lan IPv4/IPv6 forward traffic"
            jump handle_reject
    }

    chain output {
            type filter hook output priority filter; policy accept;
            oifname "lo" accept comment "!fw4: Accept traffic towards loopback"
            ct state established,related accept comment "!fw4: Allow outbound established and related flows"
            oifname "br-lan" jump output_lan comment "!fw4: Handle lan IPv4/IPv6 output traffic"
    }

    chain prerouting {
            type filter hook prerouting priority filter; policy accept;
            iifname "br-lan" jump helper_lan comment "!fw4: Handle lan IPv4/IPv6 helper assignment"
    }

    chain handle_reject {
            meta l4proto tcp reject with tcp reset comment "!fw4: Reject TCP traffic"
            reject comment "!fw4: Reject any other traffic"
    }

    chain syn_flood {
            limit rate 25/second burst 50 packets return comment "!fw4: Accept SYN packets below rate-limit"
            drop comment "!fw4: Drop excess packets"
    }

    chain input_lan {
            jump accept_from_lan
    }

    chain output_lan {
            jump accept_to_lan
    }

    chain forward_lan {
            jump accept_to_wan comment "!fw4: Accept lan to wan forwarding"
            jump accept_to_lan
    }

    chain helper_lan {
    }

    chain accept_from_lan {
            iifname "br-lan" counter packets 26 bytes 7898 accept comment "!fw4: accept lan IPv4/IPv6 traffic"
    }

    chain accept_to_lan {
            oifname "br-lan" counter packets 109 bytes 9186 accept comment "!fw4: accept lan IPv4/IPv6 traffic"
    }

    chain input_wan {
            meta nfproto ipv4 udp dport 68 counter packets 0 bytes 0 accept comment "!fw4: Allow-DHCP-Renew"
            icmp type echo-request counter packets 0 bytes 0 accept comment "!fw4: Allow-Ping"
            meta nfproto ipv4 meta l4proto igmp counter packets 0 bytes 0 accept comment "!fw4: Allow-IGMP"
            meta nfproto ipv6 udp dport 546 counter packets 0 bytes 0 accept comment "!fw4: Allow-DHCPv6"
            ip6 saddr fe80::/10 icmpv6 type . icmpv6 code { mld-listener-query . no-route, mld-listener-report . no-route, mld-listener-done . no-route, mld2-listener-report . no-route } counter packets 0 bytes 0 accept comment "!fw4: Allow-MLD"
            icmpv6 type { destination-unreachable, time-exceeded, echo-request, echo-reply, nd-router-solicit, nd-router-advert } limit rate 1000/second counter packets 0 bytes 0 accept comment "!fw4: Allow-ICMPv6-Input"
            icmpv6 type . icmpv6 code { packet-too-big . no-route, parameter-problem . no-route, nd-neighbor-solicit . no-route, nd-neighbor-advert . no-route, parameter-problem . admin-prohibited } limit rate 1000/second counter packets 0 bytes 0 accept comment "!fw4: Allow-ICMPv6-Input"
            jump reject_from_wan
    }

    chain output_wan {
            jump accept_to_wan
    }

    chain forward_wan {
            icmpv6 type { destination-unreachable, time-exceeded, echo-request, echo-reply } limit rate 1000/second counter packets 0 bytes 0 accept comment "!fw4: Allow-ICMPv6-Forward"
            icmpv6 type . icmpv6 code { packet-too-big . no-route, parameter-problem . no-route, parameter-problem . admin-prohibited } limit rate 1000/second counter packets 0 bytes 0 accept comment "!fw4: Allow-ICMPv6-Forward"
            meta l4proto esp counter packets 0 bytes 0 jump accept_to_lan comment "!fw4: Allow-IPSec-ESP"
            udp dport 500 counter packets 0 bytes 0 jump accept_to_lan comment "!fw4: Allow-ISAKMP"
            jump reject_to_wan
    }

    chain accept_to_wan {
    }

    chain reject_from_wan {
    }

    chain reject_to_wan {
    }

    chain dstnat {
            type nat hook prerouting priority dstnat; policy accept;
    }

    chain srcnat {
            type nat hook postrouting priority srcnat; policy accept;
    }

    chain srcnat_wan {
            meta nfproto ipv4 masquerade comment "!fw4: Masquerade IPv4 wan traffic"
    }

    chain raw_prerouting {
            type filter hook prerouting priority raw; policy accept;
    }

    chain raw_output {
            type filter hook output priority raw; policy accept;
    }

    chain mangle_prerouting {
            type filter hook prerouting priority mangle; policy accept;
    }

    chain mangle_postrouting {
            type filter hook postrouting priority mangle; policy accept;
    }

    chain mangle_input {
            type filter hook input priority mangle; policy accept;
    }

    chain mangle_output {
            type route hook output priority mangle; policy accept;
    }

    chain mangle_forward {
            type filter hook forward priority mangle; policy accept;
    }
}

So here are the first 153 seconds of service mesh11sd start && logread -f outpit. It Ran for more than 5min cycling without stabilising a connection.

Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option enabled [ 1 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option debuglevel [ 3 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option checkinterval [ 10 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option portal_detect [ 1 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option portal_channel [ default ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option portal_detect_threshold [ 0 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option mesh_path_cost [ 10 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option interface_timeout [ 10 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option auto_config [ 0 ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: auto_mesh_id hash [ 92d490daf46cfe534c56ddd669297e ]
Sat May 11 11:07:51 2024 daemon.info mesh11sd[4130]: option auto_mesh_band [ 2g40 ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option auto_mesh_key [ 78c8068012f8481fec118451e1041b3751801a24ab3e222643a0a6a4424b82a1 ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option auto_mesh_network [ lan ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option auto_mesh_network [ lan ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option mesh_basename [ m-5ghz- ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option mesh_gate_encryption [ 0 ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option mesh_gate_key [  ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option mesh_gate_enable [ 1 ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option mesh_gate_only [ 0 ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option ssid_suffix_enable [ 1 ]
Sat May 11 11:07:52 2024 daemon.info mesh11sd[4130]: option watchdog_nonvolatile_log [ 0 ]
Sat May 11 11:07:52 2024 daemon.notice mesh11sd[4130]: mesh11sd is in startup
Sat May 11 11:07:52 2024 daemon.debug mesh11sd[4130]: Kernel version: Major [ 5 ], Minor [ 15 ], Patch [ 155 ]
Sat May 11 11:07:52 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:07:52 2024 daemon.notice netifd: lan (17534): udhcpc: received SIGTERM
Sat May 11 11:07:52 2024 daemon.notice netifd: lan (17534): udhcpc: unicasting a release of 192.168.2.80 to 192.168.2.1
Sat May 11 11:07:52 2024 daemon.notice netifd: lan (17534): udhcpc: sending release
Sat May 11 11:07:52 2024 daemon.notice netifd: lan (17534): udhcpc: entering released state
Sat May 11 11:07:52 2024 daemon.notice netifd: Interface 'loopback' is now down
Sat May 11 11:07:52 2024 daemon.notice netifd: Interface 'loopback' is disabled
Sat May 11 11:07:52 2024 daemon.notice netifd: Network device 'lo' link is down
Sat May 11 11:07:52 2024 daemon.notice netifd: Interface 'loopback' has link connectivity loss
Sat May 11 11:07:52 2024 daemon.notice netifd: Interface 'safe' is now down
Sat May 11 11:07:52 2024 daemon.notice netifd: Interface 'lan6' is now down
Sat May 11 11:07:52 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:07:52 2024 daemon.notice netifd: lan (17534): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "lan" } (Permission denied)
Sat May 11 11:07:52 2024 daemon.notice netifd: Interface 'lan' is now down
Sat May 11 11:07:52 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:07:52 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 11:07:52 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 11:07:52 2024 kern.info kernel: [145599.415258] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:07:52 2024 kern.info kernel: [145599.415484] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:07:52 2024 kern.info kernel: [145599.420243] br-lan: port 2(wan) entered disabled state
Sat May 11 11:07:52 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 11:07:52 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 11:07:52 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 11:07:52 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:07:52 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 11:07:52 2024 kern.info kernel: [145599.430679] device 5ghzhigh left promiscuous mode
Sat May 11 11:07:52 2024 kern.info kernel: [145599.430942] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:07:52 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 11:07:52 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 11:07:52 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 11:07:52 2024 kern.info kernel: [145599.483733] device 5ghzlow left promiscuous mode
Sat May 11 11:07:52 2024 kern.info kernel: [145599.483978] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:07:52 2024 kern.info kernel: [145599.543213] device lan left promiscuous mode
Sat May 11 11:07:52 2024 kern.info kernel: [145599.543681] br-lan: port 1(lan) entered disabled state
Sat May 11 11:07:52 2024 kern.warn kernel: [145599.682167] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:07:52 2024 kern.warn kernel: [145599.682345] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:07:52 2024 kern.info kernel: [145599.769619] device wan left promiscuous mode
Sat May 11 11:07:52 2024 kern.info kernel: [145599.769891] br-lan: port 2(wan) entered disabled state
Sat May 11 11:07:53 2024 kern.info kernel: [145599.923186] qca8k-ipq4019 c000000.switch wan: Link is Down
Sat May 11 11:07:53 2024 kern.info kernel: [145599.923531] device eth0 left promiscuous mode
Sat May 11 11:07:53 2024 kern.info kernel: [145599.929993] ipqess-edma c080000.ethernet eth0: Link is Down
Sat May 11 11:07:53 2024 kern.warn kernel: [145600.012088] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 11:07:53 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 11:07:53 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 11:07:53 2024 daemon.notice netifd: Interface 'lan' is disabled
Sat May 11 11:07:53 2024 daemon.notice netifd: Interface 'lan6' is disabled
Sat May 11 11:07:53 2024 daemon.notice netifd: Interface 'safe' is disabled
Sat May 11 11:07:53 2024 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 11 11:07:53 2024 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 11 11:07:53 2024 daemon.notice netifd: Interface 'lan6' has link connectivity loss
Sat May 11 11:07:53 2024 daemon.notice netifd: Interface 'safe' has link connectivity loss
Sat May 11 11:07:53 2024 daemon.notice netifd: Network device 'wan' link is down
Sat May 11 11:07:53 2024 daemon.notice netifd: Network device 'eth0' link is down
Sat May 11 11:07:53 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:07:53 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 11:07:53 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:07:53 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 11:07:53 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 11:07:53 2024 kern.warn kernel: [145600.387134] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:07:53 2024 kern.warn kernel: [145600.387259] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:07:53 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:07:53 2024 user.notice : Added device handler type: bonding
Sat May 11 11:07:53 2024 user.notice : Added device handler type: 8021ad
Sat May 11 11:07:53 2024 user.notice : Added device handler type: 8021q
Sat May 11 11:07:53 2024 user.notice : Added device handler type: macvlan
Sat May 11 11:07:53 2024 user.notice : Added device handler type: veth
Sat May 11 11:07:53 2024 user.notice : Added device handler type: bridge
Sat May 11 11:07:53 2024 user.notice : Added device handler type: Network device
Sat May 11 11:07:53 2024 user.notice : Added device handler type: tunnel
Sat May 11 11:07:55 2024 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces?
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'lan' is enabled
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'lan6' is enabled
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'safe' is enabled
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'lan6' is setting up now
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'safe' is setting up now
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'safe' is now up
Sat May 11 11:07:55 2024 kern.info kernel: [145602.244620] ipqess-edma c080000.ethernet eth0: configuring for fixed/internal link mode
Sat May 11 11:07:55 2024 kern.info kernel: [145602.244969] ipqess-edma c080000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 11 11:07:55 2024 kern.info kernel: [145602.255944] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sat May 11 11:07:55 2024 kern.info kernel: [145602.268895] qca8k-ipq4019 c000000.switch lan: configuring for phy/psgmii link mode
Sat May 11 11:07:55 2024 kern.info kernel: [145602.275066] br-lan: port 1(lan) entered blocking state
Sat May 11 11:07:55 2024 kern.info kernel: [145602.275403] br-lan: port 1(lan) entered disabled state
Sat May 11 11:07:55 2024 kern.info kernel: [145602.281381] device lan entered promiscuous mode
Sat May 11 11:07:55 2024 kern.info kernel: [145602.285816] device eth0 entered promiscuous mode
Sat May 11 11:07:55 2024 kern.info kernel: [145602.303535] qca8k-ipq4019 c000000.switch wan: configuring for phy/psgmii link mode
Sat May 11 11:07:55 2024 kern.info kernel: [145602.306076] br-lan: port 2(wan) entered blocking state
Sat May 11 11:07:55 2024 kern.info kernel: [145602.310043] br-lan: port 2(wan) entered disabled state
Sat May 11 11:07:55 2024 kern.info kernel: [145602.315878] device wan entered promiscuous mode
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'loopback' is enabled
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'loopback' is setting up now
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'loopback' is now up
Sat May 11 11:07:55 2024 daemon.notice netifd: Network device 'eth0' link is up
Sat May 11 11:07:55 2024 daemon.notice netifd: Network device 'lo' link is up
Sat May 11 11:07:55 2024 daemon.notice netifd: Interface 'loopback' has link connectivity
Sat May 11 11:07:55 2024 daemon.err odhcp6c[4730]: Failed to send RS (Network unreachable)
Sat May 11 11:07:55 2024 daemon.notice netifd: radio2 (4726): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:07:55 2024 daemon.notice netifd: radio0 (4725): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:07:55 2024 daemon.err odhcp6c[4730]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Sat May 11 11:07:55 2024 user.notice firewall: Reloading firewall due to ifup of safe (br-lan)
Sat May 11 11:07:55 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:07:55 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:07:55 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:07:55 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:07:56 2024 daemon.notice netifd: radio2 (4726): command failed: Not supported (-95)
Sat May 11 11:07:56 2024 daemon.notice netifd: radio0 (4725): command failed: Not supported (-95)
Sat May 11 11:07:56 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:07:56 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:07:56 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:07:56 2024 daemon.err odhcp6c[4730]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Sat May 11 11:07:57 2024 kern.info kernel: [145604.422490] qca8k-ipq4019 c000000.switch wan: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 11 11:07:58 2024 kern.info kernel: [145604.795486] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:07:58 2024 kern.info kernel: [145604.795550] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:07:58 2024 kern.info kernel: [145604.800290] device 5ghzlow entered promiscuous mode
Sat May 11 11:07:58 2024 kern.info kernel: [145604.805839] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:07:58 2024 kern.info kernel: [145604.810669] br-lan: port 3(5ghzlow) entered forwarding state
Sat May 11 11:07:58 2024 kern.info kernel: [145604.820763] br-lan: port 2(wan) entered blocking state
Sat May 11 11:07:58 2024 kern.info kernel: [145604.821918] br-lan: port 2(wan) entered forwarding state
Sat May 11 11:07:58 2024 daemon.err odhcp6c[4730]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Sat May 11 11:07:58 2024 daemon.err odhcp6c[4730]: Failed to send RS (Address not available)
Sat May 11 11:07:58 2024 kern.info kernel: [145604.831615] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:07:58 2024 kern.info kernel: [145604.832889] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Sat May 11 11:07:58 2024 daemon.notice netifd: Network device 'wan' link is up
Sat May 11 11:07:58 2024 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 11 11:07:58 2024 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 11 11:07:58 2024 daemon.notice netifd: Interface 'lan' is setting up now
Sat May 11 11:07:58 2024 daemon.notice netifd: Interface 'lan6' has link connectivity
Sat May 11 11:07:58 2024 daemon.notice netifd: Interface 'safe' has link connectivity
Sat May 11 11:07:58 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:07:58 2024 daemon.notice netifd: lan (5157): udhcpc: started, v1.36.1
Sat May 11 11:07:58 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 11:07:58 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 11:07:58 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 11:07:58 2024 daemon.err odhcp6c[4730]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Sat May 11 11:07:58 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=30:23:03:2d:b0:88 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 11:07:58 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting discover
Sat May 11 11:07:58 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 11:07:58 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:07:59 2024 daemon.err odhcp6c[4730]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Sat May 11 11:08:00 2024 kern.warn kernel: [145607.428485] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 11:08:00 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 11:08:00 2024 kern.info kernel: [145607.434345] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:08:00 2024 kern.info kernel: [145607.434411] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:08:00 2024 kern.info kernel: [145607.439521] device 5ghzhigh entered promiscuous mode
Sat May 11 11:08:00 2024 kern.info kernel: [145607.445099] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:08:00 2024 kern.info kernel: [145607.449701] br-lan: port 4(5ghzhigh) entered forwarding state
Sat May 11 11:08:00 2024 kern.info kernel: [145607.456864] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:08:00 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 11:08:00 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 11:08:00 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:00 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:00 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:08:01 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 11:08:01 2024 daemon.debug mesh11sd[4130]: dsa_mesh_maclist [  30:23:03:2d:b0:88 30:23:03:2d:b0:86 30:23:03:2d:b0:87 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_fwding [ 1 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_rssi_threshold [ -80 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_gate_announcements [ 1 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_hwmp_rootmode [ 4 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_hwmp_rann_interval [ 5000 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_hwmp_root_interval [ 5000 ]
Sat May 11 11:08:01 2024 daemon.info mesh11sd[4130]: option mesh_hwmp_active_path_timeout [ 5000 ]
Sat May 11 11:08:02 2024 daemon.info mesh11sd[4130]: option mesh_hwmp_active_path_to_root_timeout [ 6000 ]
Sat May 11 11:08:02 2024 daemon.info mesh11sd[4130]: option mesh_max_peer_links [ 16 ]
Sat May 11 11:08:02 2024 daemon.notice mesh11sd[4130]: mesh11sd v4.0.0beta has started: mesh management mode 1
Sat May 11 11:08:02 2024 daemon.notice mesh11sd[4130]: Setting mac address of mesh interface m-5ghz-0 to [ 32:23:03:2d:b0:85 ]
Sat May 11 11:08:02 2024 daemon.notice mesh11sd[4130]: Setting mac address of mesh interface m-5ghz-1 to [ 32:23:03:2d:b0:85 ]
Sat May 11 11:08:02 2024 daemon.notice mesh11sd[4130]: Setting mac address of mesh interface m-5ghz-2 to [ 32:23:03:2d:b0:85 ]
Sat May 11 11:08:02 2024 daemon.debug mesh11sd[4130]: Disconnecting nodes
Sat May 11 11:08:02 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:08:02 2024 kern.info kernel: [145609.580467] device 5ghzhigh left promiscuous mode
Sat May 11 11:08:02 2024 kern.info kernel: [145609.580684] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:08:02 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:02 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:08:02 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:05 2024 daemon.warn odhcp6c[4730]: Server returned message status 'Success (success)'
Sat May 11 11:08:05 2024 daemon.notice netifd: Interface 'lan6' is now up
Sat May 11 11:08:05 2024 user.notice firewall: Reloading firewall due to ifup of lan6 (br-lan)
Sat May 11 11:08:10 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 11:08:11 2024 daemon.notice netifd: radio0 (6115): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:08:13 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:08:24 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:08:30 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:08:30 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:08:30 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 11:08:30 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->DISABLED
Sat May 11 11:08:30 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 11:08:30 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 11:08:30 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 11:08:30 2024 daemon.err hostapd: hostapd_free_hapd_data: Interface 5ghzhigh wasn't started
Sat May 11 11:08:30 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 11:08:30 2024 daemon.notice hostapd: nl80211: Failed to remove interface 5ghzhigh from bridge br-lan: Invalid argument
Sat May 11 11:08:30 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:30 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 11:08:30 2024 kern.warn kernel: [145637.071510] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:08:30 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:08:30 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:08:30 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 11:08:30 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 11:08:30 2024 kern.warn kernel: [145637.301443] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:08:30 2024 kern.info kernel: [145637.307646] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:08:30 2024 kern.info kernel: [145637.361761] device 5ghzlow left promiscuous mode
Sat May 11 11:08:30 2024 kern.info kernel: [145637.361838] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:08:30 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:30 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:08:30 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 11:08:30 2024 daemon.notice netifd: radio0 (6115): command failed: Not supported (-95)
Sat May 11 11:08:30 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:30 2024 daemon.notice netifd: radio2 (6263): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:08:31 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:08:31 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:31 2024 daemon.notice netifd: radio2 (6263): command failed: Not supported (-95)
Sat May 11 11:08:31 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:08:31 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 11:08:31 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 11:08:31 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:31 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=32:23:03:2e:b0:85 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 11:08:33 2024 kern.warn kernel: [145640.527764] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 11:08:33 2024 kern.info kernel: [145640.534412] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 11:08:33 2024 kern.info kernel: [145640.534489] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 11:08:33 2024 kern.info kernel: [145640.539588] device 5ghzhigh entered promiscuous mode
Sat May 11 11:08:33 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 11:08:33 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 11:08:33 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:08:33 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:33 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:33 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:33 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 11:08:35 2024 kern.info kernel: [145642.313130] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 11:08:35 2024 kern.info kernel: [145642.313215] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 11:08:35 2024 kern.info kernel: [145642.318013] device 5ghzlow entered promiscuous mode
Sat May 11 11:08:35 2024 kern.info kernel: [145642.323488] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 11:08:35 2024 kern.info kernel: [145642.328353] br-lan: port 4(5ghzlow) entered forwarding state
Sat May 11 11:08:35 2024 kern.info kernel: [145642.335028] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 11:08:35 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:35 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:36 2024 kern.info kernel: [145642.867846] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 11:08:36 2024 kern.info kernel: [145642.868170] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 11:08:36 2024 kern.info kernel: [145642.873699] br-lan: port 3(5ghzhigh) entered forwarding state
Sat May 11 11:08:36 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 11:08:36 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 11:08:36 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 11:08:36 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 11:08:37 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 11:08:37 2024 kern.info kernel: [145644.127017] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 11:08:37 2024 kern.info kernel: [145644.127348] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 11:08:37 2024 kern.info kernel: [145644.132522] br-lan: port 4(5ghzlow) entered forwarding state
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=63 id_str=]
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=63
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 11:08:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 11:08:37 2024 daemon.debug mesh11sd[4130]: interface 5ghzlow is up
Sat May 11 11:08:38 2024 daemon.info mesh11sd[4130]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 11:08:38 2024 daemon.info mesh11sd[4130]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 11:08:38 2024 daemon.info mesh11sd[4130]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 11:08:38 2024 daemon.info mesh11sd[4130]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 11:08:38 2024 daemon.debug mesh11sd[4130]: Disconnecting nodes
Sat May 11 11:08:38 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:08:38 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:08:38 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:08:38 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 11:08:38 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 11:08:38 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 11:08:38 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 11:08:38 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 11:08:39 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 11:08:39 2024 kern.info kernel: [145645.935972] device 5ghzhigh left promiscuous mode
Sat May 11 11:08:39 2024 kern.info kernel: [145645.936305] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 11:08:39 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 11:08:39 2024 kern.warn kernel: [145646.052064] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:08:39 2024 kern.warn kernel: [145646.052196] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:08:39 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:39 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:39 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 11:08:39 2024 daemon.debug mesh11sd[4130]: node [DEST,ADDR]
Sat May 11 11:08:39 2024 daemon.debug mesh11sd[4130]: node [30:23:03:99:bd:7d,30:23:03:99:bd:7d]
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 11:08:39 2024 kern.warn kernel: [145646.521785] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 11:08:39 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:08:39 2024 kern.info kernel: [145646.594676] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:08:39 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 11:08:39 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 11:08:39 2024 kern.info kernel: [145646.642612] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 11:08:39 2024 kern.info kernel: [145646.642682] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 11:08:39 2024 kern.warn kernel: [145646.706921] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:08:39 2024 kern.warn kernel: [145646.707036] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:08:39 2024 kern.info kernel: [145646.719142] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 11:08:39 2024 kern.info kernel: [145646.761761] device 5ghzlow left promiscuous mode
Sat May 11 11:08:39 2024 kern.info kernel: [145646.761821] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 11:08:40 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:40 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:08:40 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:40 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 11:08:40 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 11:08:40 2024 daemon.notice netifd: radio2 (7020): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:08:40 2024 daemon.notice netifd: radio0 (7019): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:08:40 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:08:40 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:40 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:08:40 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:08:40 2024 daemon.notice netifd: radio2 (7020): command failed: Not supported (-95)
Sat May 11 11:08:40 2024 daemon.notice netifd: radio0 (7019): command failed: Not supported (-95)
Sat May 11 11:08:40 2024 daemon.debug mesh11sd[4130]: checkinterval 10 seconds
Sat May 11 11:08:40 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:40 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:08:40 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:08:42 2024 kern.info kernel: [145649.429975] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:08:42 2024 kern.info kernel: [145649.430036] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:08:42 2024 kern.info kernel: [145649.434810] device 5ghzlow entered promiscuous mode
Sat May 11 11:08:42 2024 kern.info kernel: [145649.444180] device 5ghzlow left promiscuous mode
Sat May 11 11:08:42 2024 kern.info kernel: [145649.445378] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:08:42 2024 kern.info kernel: [145649.485020] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:08:42 2024 kern.info kernel: [145649.485096] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:08:42 2024 kern.info kernel: [145649.489976] device 5ghzlow entered promiscuous mode
Sat May 11 11:08:42 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:42 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:08:42 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:42 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 11:08:42 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 11:08:42 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 11:08:42 2024 daemon.notice netifd: Interface 'lan6' has lost the connection
Sat May 11 11:08:42 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:42 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:42 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=32:23:03:2e:b0:85 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 11:08:44 2024 daemon.warn odhcp6c[4730]: Server returned message status 'Success (success)'
Sat May 11 11:08:45 2024 kern.warn kernel: [145652.068882] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 11:08:45 2024 kern.info kernel: [145652.072983] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:08:45 2024 kern.info kernel: [145652.073644] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:08:45 2024 kern.info kernel: [145652.079663] device 5ghzhigh entered promiscuous mode
Sat May 11 11:08:45 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 11:08:45 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 11:08:45 2024 kern.info kernel: [145652.089723] device 5ghzhigh left promiscuous mode
Sat May 11 11:08:45 2024 kern.info kernel: [145652.090074] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:08:45 2024 kern.info kernel: [145652.144768] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:08:45 2024 kern.info kernel: [145652.144832] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:08:45 2024 kern.info kernel: [145652.149926] device 5ghzhigh entered promiscuous mode
Sat May 11 11:08:45 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:08:45 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 11:08:45 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting discover
Sat May 11 11:08:45 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 11:08:45 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:08:45 2024 daemon.notice netifd: Interface 'lan6' is now up
Sat May 11 11:08:45 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 11:08:46 2024 user.notice firewall: Reloading firewall due to ifup of lan6 (br-lan)
Sat May 11 11:08:47 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 11:08:47 2024 kern.info kernel: [145654.755472] br-lan: port 2(wan) received tcn bpdu
Sat May 11 11:08:47 2024 kern.info kernel: [145654.755532] br-lan: topology change detected, propagating
Sat May 11 11:08:48 2024 kern.info kernel: [145655.471917] br-lan: port 2(wan) received tcn bpdu
Sat May 11 11:08:48 2024 kern.info kernel: [145655.471975] br-lan: topology change detected, propagating
Sat May 11 11:08:53 2024 daemon.warn dawn: Connection closed
Sat May 11 11:09:01 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:09:11 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:09:12 2024 daemon.notice netifd: radio0 (7019): Command failed: ubus call hostapd config_set { "phy": "phy0", "config":"/var/run/hostapd-phy0.conf", "prev_config": "/var/run/hostapd-phy0.conf.prev"} (Request timed out)
Sat May 11 11:09:12 2024 daemon.notice netifd: radio0 (7019): Device setup failed: HOSTAPD_START_FAILED
Sat May 11 11:09:12 2024 daemon.notice netifd: Wireless device 'radio0' set retry=0
Sat May 11 11:09:13 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 11:09:14 2024 kern.info kernel: [145681.118189] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 11:09:14 2024 kern.info kernel: [145681.118469] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:09:14 2024 kern.info kernel: [145681.124028] br-lan: port 4(5ghzhigh) entered listening state
Sat May 11 11:09:14 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 11:09:14 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 11:09:14 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 11:09:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 11:09:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 11:09:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 11:09:14 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 11:09:14 2024 kern.info kernel: [145681.762026] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 11:09:14 2024 kern.info kernel: [145681.762349] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:09:14 2024 kern.info kernel: [145681.767489] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 11:09:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=64 id_str=]
Sat May 11 11:09:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=64
Sat May 11 11:09:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 11:09:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 11:09:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 11:09:16 2024 daemon.info mesh11sd[4130]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 11:09:16 2024 daemon.info mesh11sd[4130]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 11:09:16 2024 daemon.info mesh11sd[4130]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 11:09:16 2024 daemon.info mesh11sd[4130]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 11:09:16 2024 daemon.debug mesh11sd[4130]: checkinterval 10 seconds
Sat May 11 11:09:22 2024 kern.info kernel: [145689.380859] br-lan: port 4(5ghzhigh) entered learning state
Sat May 11 11:09:23 2024 kern.info kernel: [145690.020869] br-lan: port 3(5ghzlow) entered learning state
Sat May 11 11:09:26 2024 daemon.debug mesh11sd[4130]: interface 5ghzlow is up
Sat May 11 11:09:26 2024 daemon.info mesh11sd[4130]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 11:09:26 2024 daemon.info mesh11sd[4130]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 11:09:26 2024 daemon.info mesh11sd[4130]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 11:09:27 2024 daemon.info mesh11sd[4130]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 11:09:27 2024 daemon.debug mesh11sd[4130]: Disconnecting nodes
Sat May 11 11:09:27 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:09:27 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:09:27 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:09:27 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:09:27 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 11:09:27 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 11:09:27 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 11:09:27 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 11:09:27 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 11:09:27 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 11:09:27 2024 kern.info kernel: [145694.311347] device 5ghzhigh left promiscuous mode
Sat May 11 11:09:27 2024 kern.info kernel: [145694.311597] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:09:27 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 11:09:27 2024 kern.warn kernel: [145694.481547] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 11:09:27 2024 kern.warn kernel: [145694.482527] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:09:27 2024 kern.warn kernel: [145694.487530] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 11:09:27 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:09:27 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:09:27 2024 kern.info kernel: [145694.713583] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:09:27 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:09:27 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 11:09:28 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 11:09:28 2024 kern.info kernel: [145694.792178] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:09:28 2024 kern.info kernel: [145694.792251] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 11:09:28 2024 kern.warn kernel: [145694.881340] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:09:28 2024 kern.warn kernel: [145694.881420] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:09:28 2024 kern.info kernel: [145694.896027] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:09:28 2024 kern.info kernel: [145694.951562] device 5ghzlow left promiscuous mode
Sat May 11 11:09:28 2024 kern.info kernel: [145694.951642] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:09:28 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:09:28 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:09:28 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 11:09:28 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 11:09:28 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:09:28 2024 daemon.notice netifd: radio0 (8721): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:09:28 2024 daemon.notice netifd: radio2 (8722): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:09:28 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:09:28 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:09:28 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:09:28 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:09:28 2024 daemon.notice netifd: radio2 (8722): command failed: Not supported (-95)
Sat May 11 11:09:28 2024 daemon.notice netifd: radio0 (8721): command failed: Not supported (-95)
Sat May 11 11:09:28 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:09:28 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:09:28 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:09:30 2024 kern.info kernel: [145697.479152] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:09:30 2024 kern.info kernel: [145697.479225] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:09:30 2024 kern.info kernel: [145697.483970] device 5ghzlow entered promiscuous mode
Sat May 11 11:09:30 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:09:30 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:09:30 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 11:09:30 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 11:09:30 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 11:09:30 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:09:30 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=32:23:03:2e:b0:85 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 11:09:33 2024 kern.warn kernel: [145700.050411] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 11:09:33 2024 kern.info kernel: [145700.054221] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:09:33 2024 kern.info kernel: [145700.055171] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:09:33 2024 kern.info kernel: [145700.061266] device 5ghzhigh entered promiscuous mode
Sat May 11 11:09:33 2024 kern.info kernel: [145700.066668] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:09:33 2024 kern.info kernel: [145700.071431] br-lan: port 4(5ghzhigh) entered listening state
Sat May 11 11:09:33 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 11:09:33 2024 kern.info kernel: [145700.077624] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:09:33 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 11:09:33 2024 kern.info kernel: [145700.089212] device 5ghzhigh left promiscuous mode
Sat May 11 11:09:33 2024 kern.info kernel: [145700.089458] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:09:33 2024 kern.info kernel: [145700.175853] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:09:33 2024 kern.info kernel: [145700.175940] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:09:33 2024 kern.info kernel: [145700.181113] device 5ghzhigh entered promiscuous mode
Sat May 11 11:09:33 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:09:33 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 11:09:33 2024 daemon.notice netifd: Interface 'lan6' has lost the connection
Sat May 11 11:09:33 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting discover
Sat May 11 11:09:33 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 11:09:33 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:09:33 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 11:09:34 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 11:09:36 2024 daemon.warn odhcp6c[4730]: Server returned message status 'Success (success)'
Sat May 11 11:09:38 2024 daemon.notice netifd: Interface 'lan6' is now up
Sat May 11 11:09:38 2024 user.notice firewall: Reloading firewall due to ifup of lan6 (br-lan)
Sat May 11 11:09:40 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:09:51 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:10:00 2024 daemon.notice netifd: radio0 (8721): Command failed: ubus call hostapd config_set { "phy": "phy0", "config":"/var/run/hostapd-phy0.conf", "prev_config": "/var/run/hostapd-phy0.conf.prev"} (Request timed out)
Sat May 11 11:10:00 2024 daemon.notice netifd: radio0 (8721): Device setup failed: HOSTAPD_START_FAILED
Sat May 11 11:10:00 2024 daemon.notice netifd: Wireless device 'radio0' set retry=0
Sat May 11 11:10:02 2024 daemon.notice mesh11sd[4130]: 5ghzlow is not up - giving up for now.
Sat May 11 11:10:02 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 11:10:03 2024 kern.info kernel: [145730.107440] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 11:10:03 2024 kern.info kernel: [145730.107722] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:10:03 2024 kern.info kernel: [145730.113301] br-lan: port 4(5ghzhigh) entered listening state
Sat May 11 11:10:03 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 11:10:03 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 11:10:03 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 11:10:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 11:10:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 11:10:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 11:10:03 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 11:10:03 2024 kern.info kernel: [145730.766737] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 11:10:03 2024 kern.info kernel: [145730.767070] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:10:03 2024 kern.info kernel: [145730.772240] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 11:10:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=65 id_str=]
Sat May 11 11:10:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=65
Sat May 11 11:10:04 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 11:10:04 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 11:10:04 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 11:10:04 2024 daemon.info mesh11sd[4130]: Old value:mesh_connected_to_gate=0, Setting new value:mesh_connected_to_gate=1
Sat May 11 11:10:05 2024 daemon.debug mesh11sd[4130]: node [DEST,ADDR]
Sat May 11 11:10:05 2024 daemon.info mesh11sd[4130]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 11:10:05 2024 daemon.info mesh11sd[4130]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 11:10:05 2024 daemon.info mesh11sd[4130]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 11:10:05 2024 daemon.info mesh11sd[4130]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 11:10:06 2024 daemon.info mesh11sd[4130]: Path to station [ 30:23:03:99:bd:7d ] is stable
Sat May 11 11:10:06 2024 daemon.debug mesh11sd[4130]: checkinterval 10 seconds
Sat May 11 11:10:11 2024 kern.info kernel: [145738.660626] br-lan: port 4(5ghzhigh) entered learning state
Sat May 11 11:10:12 2024 kern.info kernel: [145739.300618] br-lan: port 3(5ghzlow) entered learning state
Sat May 11 11:10:16 2024 daemon.debug mesh11sd[4130]: interface 5ghzlow is up
Sat May 11 11:10:16 2024 daemon.info mesh11sd[4130]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 11:10:16 2024 daemon.info mesh11sd[4130]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 11:10:16 2024 daemon.info mesh11sd[4130]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 11:10:16 2024 daemon.info mesh11sd[4130]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 11:10:16 2024 daemon.debug mesh11sd[4130]: Disconnecting nodes
Sat May 11 11:10:17 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:10:17 2024 daemon.info sh[4130]: 'radio1' is disabled
Sat May 11 11:10:17 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:10:17 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 11:10:17 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 11:10:17 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 11:10:17 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 11:10:17 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 11:10:17 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 11:10:17 2024 kern.info kernel: [145744.346798] device 5ghzhigh left promiscuous mode
Sat May 11 11:10:17 2024 kern.info kernel: [145744.347049] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:10:17 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 11:10:17 2024 kern.warn kernel: [145744.441459] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:10:17 2024 kern.warn kernel: [145744.441618] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 11:10:17 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:10:17 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:10:17 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:10:17 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:10:17 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 11:10:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 11:10:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 11:10:18 2024 kern.warn kernel: [145744.931375] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 11:10:18 2024 daemon.debug mesh11sd[4130]: node [DEST,ADDR]
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:10:18 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 11:10:18 2024 kern.info kernel: [145745.003156] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 11:10:18 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 11:10:18 2024 kern.info kernel: [145745.082022] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:10:18 2024 kern.info kernel: [145745.082087] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 11:10:18 2024 kern.warn kernel: [145745.156265] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:10:18 2024 kern.warn kernel: [145745.156371] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 11:10:18 2024 kern.info kernel: [145745.168756] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:10:18 2024 kern.info kernel: [145745.201251] device 5ghzlow left promiscuous mode
Sat May 11 11:10:18 2024 kern.info kernel: [145745.201330] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:10:18 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:10:18 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:10:18 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 11:10:18 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 11:10:18 2024 daemon.notice netifd: radio2 (10443): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:10:18 2024 daemon.notice netifd: radio0 (10449): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 11:10:18 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:10:18 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:10:18 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 11:10:19 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:10:19 2024 daemon.notice netifd: radio2 (10443): command failed: Not supported (-95)
Sat May 11 11:10:19 2024 daemon.notice netifd: radio0 (10449): command failed: Not supported (-95)
Sat May 11 11:10:19 2024 daemon.debug mesh11sd[4130]: checkinterval 10 seconds
Sat May 11 11:10:19 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:10:19 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 11:10:19 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 11:10:21 2024 kern.info kernel: [145747.860001] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:10:21 2024 kern.info kernel: [145747.860064] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:10:21 2024 kern.info kernel: [145747.864870] device 5ghzlow entered promiscuous mode
Sat May 11 11:10:21 2024 kern.info kernel: [145747.874934] device 5ghzlow left promiscuous mode
Sat May 11 11:10:21 2024 kern.info kernel: [145747.875395] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:10:21 2024 kern.info kernel: [145747.933326] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 11:10:21 2024 kern.info kernel: [145747.933394] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 11:10:21 2024 kern.info kernel: [145747.938108] device 5ghzlow entered promiscuous mode
Sat May 11 11:10:21 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:10:21 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 11:10:21 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 11:10:21 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 11:10:21 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 11:10:21 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 11:10:21 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=32:23:03:2e:b0:85 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 11:10:23 2024 kern.warn kernel: [145750.521722] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 11:10:23 2024 kern.info kernel: [145750.526477] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:10:23 2024 kern.info kernel: [145750.526536] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:10:23 2024 kern.info kernel: [145750.532542] device 5ghzhigh entered promiscuous mode
Sat May 11 11:10:23 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 11:10:23 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 11:10:23 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 11:10:23 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 11:10:23 2024 kern.info kernel: [145750.542749] device 5ghzhigh left promiscuous mode
Sat May 11 11:10:23 2024 kern.info kernel: [145750.543024] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:10:23 2024 daemon.notice netifd: lan (5157): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 11:10:23 2024 daemon.notice netifd: lan (5157): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 11:10:23 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 11:10:23 2024 kern.info kernel: [145750.615056] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 11:10:23 2024 kern.info kernel: [145750.615144] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 11:10:23 2024 kern.info kernel: [145750.620268] device 5ghzhigh entered promiscuous mode
Sat May 11 11:10:23 2024 daemon.notice netifd: lan (5157): udhcpc: sending renew to server 192.168.2.1
Sat May 11 11:10:23 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 11:10:23 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 11:10:24 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=66 id_str=]
Sat May 11 11:10:24 2024 daemon.notice netifd: Network device '5ghzlow' link is up

After looking at the code for protal detection here is a suggested patch:

--- /usr/sbin/mesh11sd.ori  2024-05-11 13:08:45.000000000 +0200
+++ /usr/sbin/mesh11sd      2024-05-11 13:08:46.000000000 +0200
@@ -882,7 +882,7 @@
                        if [ "$gwproto" -eq 1 ] || [ "$gwsrc" -eq 1 ]; then
                                # must test if upstream gateway is actually up
                                # On an ethernet link to eg an isp router, trigger arp with a ping:
-                               gwstatus=$(ping -q -c 2 -W 1 "$gw_ip" &>/dev/null; ip neigh | grep "$gw_ip" | awk 'NR==1 {printf "%s", $NF}')
+                               gwstatus=$(ping -q -c 2 -W 1 "$gw_ip" &>/dev/null; ip neigh | grep -w "$gw_ip" | awk 'NR==1 {printf "%s", $NF}')

Without this gwstatus can be that of an ip containing $gw_ip as was my case:

#gw_ip=192.168.2.1 && ping -q -c 2 -W 1 "$gw_ip" &>/dev/null; ip neigh | grep "$gw_ip" | awk 'NR==1 {printf "%s", $NF}'
STALE

vs.

#gw_ip=192.168.2.1 && ping -q -c 2 -W 1 "$gw_ip" &>/dev/null; ip neigh | grep -w "$gw_ip" | awk 'NR==1 {printf "%s", $NF}'
REACHABLE

Because

gw_ip=192.168.2.1 && ping -q -c 2 -W 1 "$gw_ip" &>/dev/null; ip neigh | grep "$gw_ip" 
192.168.2.14 dev br-lan lladdr 18:b4:30:81:9f:fc used 0/0/0 probes 1 STALE
192.168.2.1 dev br-lan lladdr a4:2b:b0:e9:90:66 ref 1 used 0/0/0 probes 1 DELAY
192.168.2.13 dev br-lan lladdr 18:b4:30:83:d6:50 used 0/0/0 probes 1 STALE
192.168.2.19 dev br-lan lladdr 30:23:03:99:bd:7b used 0/0/0 probes 1 STALE
192.168.2.18 dev br-lan lladdr 30:23:03:99:bd:7b used 0/0/0 probes 1 STALE
192.168.2.17 dev br-lan lladdr 30:23:03:99:bd:7b used 0/0/0 probes 1 STALE

gw_ip=192.168.2.1 && ping -q -c 2 -W 1 "$gw_ip" &>/dev/null; ip neigh | grep "$gw_ip" | awk 'NR==1 {print $0}'
192.168.2.14 dev br-lan lladdr 18:b4:30:81:9f:fc used 0/0/0 probes 1 STALE

@dwardor

Without this gwstatus can be that of an ip containing $gw_ip as was my case:

That is true, but you are running with auto_config=0, so portal detect is never run.....

I have updated the code anyway - thanks!

Your setup in general is unusual to the extreme and absolutely requires auto_config=0 :-D

On looking closer, I see mesh11sd still had some "auto_config" aspects enabled even with auto_config disabled. This was to do with fixups for the previous mentioned issues with wireless driver/dsa/kernel combinations on some architectures.

Here is beta-10, please give it a try so we can see if auto_config=0 is now fixed! mesh11sd.tar.gz

That is true, but you are running with auto_config=0, so portal detect is never run.....

Yes I know.

Here is what I get on a03_1 (my portal) with beta10 (I also updated mesh11sd config mesh_params)

Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option enabled [ 1 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option debuglevel [ 3 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option checkinterval [ 10 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option portal_detect [ 1 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option portal_channel [ default ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option portal_detect_threshold [ 0 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_path_cost [ 10 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option interface_timeout [ 10 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option auto_config [ 0 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: auto_mesh_id hash [ 92d490daf46cfe534c56ddd669297e ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option auto_mesh_band [ 2g40 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option auto_mesh_key [ 78c8068012f8481fec118451e1041b3751801a24ab3e222643a0a6a4424b82a1 ]
Sat May 11 17:32:04 2024 daemon.warn mesh11sd[22246]: option auto_mesh_network is not configured, defaulting to [ lan ]. Is this what you intended?
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option auto_mesh_network [ lan ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option auto_mesh_network [ lan ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_basename [ m-5ghz- ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_gate_encryption [ 0 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_gate_key [  ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_gate_enable [ 1 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_gate_only [ 0 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option ssid_suffix_enable [ 1 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option watchdog_nonvolatile_log [ 0 ]
Sat May 11 17:32:04 2024 daemon.notice mesh11sd[22246]: mesh11sd is in startup
Sat May 11 17:32:04 2024 daemon.debug mesh11sd[22246]: Kernel version: Major [ 5 ], Minor [ 15 ], Patch [ 155 ]
Sat May 11 17:32:04 2024 daemon.info mesh11sd[22246]: option mesh_fwding [ 1 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_rssi_threshold [ -80 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_gate_announcements [ 1 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_hwmp_rootmode [ 4 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_hwmp_rann_interval [ 5000 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_hwmp_root_interval [ 5000 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_hwmp_active_path_timeout [ 5000 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_hwmp_active_path_to_root_timeout [ 6000 ]
Sat May 11 17:32:05 2024 daemon.info mesh11sd[22246]: option mesh_max_peer_links [ 16 ]
Sat May 11 17:32:05 2024 daemon.notice mesh11sd[22246]: mesh11sd v4.0.0beta has started: mesh management mode 1
Sat May 11 17:32:05 2024 daemon.debug mesh11sd[22246]: Disconnecting nodes
Sat May 11 17:32:05 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:32:05 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:32:05 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:32:05 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:32:05 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 17:32:05 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 17:32:05 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 17:32:05 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 17:32:05 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 17:32:05 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:32:05 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 17:32:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 17:32:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 17:32:05 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 17:32:05 2024 kern.info kernel: [168652.581942] device 5ghzhigh left promiscuous mode
Sat May 11 17:32:05 2024 kern.info kernel: [168652.582162] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:32:05 2024 kern.warn kernel: [168652.588594] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 17:32:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 17:32:05 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 17:32:05 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 17:32:06 2024 kern.warn kernel: [168652.716831] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:32:06 2024 kern.warn kernel: [168652.717085] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:32:06 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:32:06 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 17:32:06 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:32:06 2024 kern.info kernel: [168652.862580] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:32:06 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:32:06 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 17:32:06 2024 kern.info kernel: [168652.930168] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:32:06 2024 kern.info kernel: [168652.930265] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 17:32:06 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 17:32:06 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:32:06 2024 kern.warn kernel: [168653.011872] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:32:06 2024 kern.warn kernel: [168653.011955] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:32:06 2024 kern.info kernel: [168653.027796] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:32:06 2024 kern.info kernel: [168653.086720] device 5ghzlow left promiscuous mode
Sat May 11 17:32:06 2024 kern.info kernel: [168653.086806] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:32:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:32:06 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:32:06 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:32:06 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 17:32:06 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 17:32:06 2024 daemon.notice netifd: radio2 (22729): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:32:06 2024 daemon.notice netifd: radio0 (22731): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:32:06 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:32:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:32:06 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:32:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:32:06 2024 daemon.notice netifd: radio2 (22729): command failed: Not supported (-95)
Sat May 11 17:32:07 2024 daemon.notice netifd: radio0 (22731): command failed: Not supported (-95)
Sat May 11 17:32:07 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:32:07 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:32:07 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:32:08 2024 kern.info kernel: [168655.636098] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:32:08 2024 kern.info kernel: [168655.636161] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:32:08 2024 kern.info kernel: [168655.640920] device 5ghzlow entered promiscuous mode
Sat May 11 17:32:08 2024 kern.info kernel: [168655.652230] device 5ghzlow left promiscuous mode
Sat May 11 17:32:08 2024 kern.info kernel: [168655.652533] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:32:09 2024 kern.info kernel: [168655.718641] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:32:09 2024 kern.info kernel: [168655.718702] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:32:09 2024 kern.info kernel: [168655.723463] device 5ghzlow entered promiscuous mode
Sat May 11 17:32:09 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:32:09 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:32:09 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 17:32:09 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 17:32:09 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 17:32:09 2024 daemon.notice netifd: lan (9912): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 17:32:09 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:32:09 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 17:32:09 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 17:32:18 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:32:28 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:32:39 2024 daemon.notice netifd: radio0 (22731): Command failed: ubus call hostapd config_set { "phy": "phy0", "config":"/var/run/hostapd-phy0.conf", "prev_config": "/var/run/hostapd-phy0.conf.prev"} (Request timed out)
Sat May 11 17:32:39 2024 daemon.notice netifd: radio0 (22731): Device setup failed: HOSTAPD_START_FAILED
Sat May 11 17:32:39 2024 daemon.notice netifd: Wireless device 'radio0' set retry=0
Sat May 11 17:32:39 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 17:32:39 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=30:23:03:2d:b0:88 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 17:32:39 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:32:41 2024 kern.warn kernel: [168688.293960] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 17:32:41 2024 kern.info kernel: [168688.302466] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 17:32:41 2024 kern.info kernel: [168688.302569] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:32:41 2024 kern.info kernel: [168688.307912] device 5ghzhigh entered promiscuous mode
Sat May 11 17:32:41 2024 daemon.warn hostapd: nl80211: Failed to add interface 5ghzhigh into bridge br-lan: Resource busy
Sat May 11 17:32:41 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 17:32:41 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 17:32:41 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 17:32:41 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 17:32:41 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:32:41 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 17:32:41 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:32:41 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=90 id_str=]
Sat May 11 17:32:41 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 17:32:51 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:33:02 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:33:09 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 17:33:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=90
Sat May 11 17:33:11 2024 kern.info kernel: [168718.357383] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 17:33:11 2024 kern.info kernel: [168718.357698] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:33:11 2024 kern.info kernel: [168718.362837] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 17:33:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:11 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 kern.info kernel: [168718.872947] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 17:33:12 2024 kern.info kernel: [168718.873285] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 17:33:12 2024 kern.info kernel: [168718.878834] br-lan: port 4(5ghzhigh) entered listening state
Sat May 11 17:33:12 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 17:33:12 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 17:33:12 2024 daemon.warn dawn: Connection closed
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 daemon.info mesh11sd[22246]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 17:33:12 2024 daemon.info mesh11sd[22246]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 17:33:12 2024 daemon.info mesh11sd[22246]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 17:33:12 2024 daemon.info mesh11sd[22246]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:12 2024 daemon.debug mesh11sd[22246]: checkinterval 10 seconds
Sat May 11 17:33:12 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:13 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:14 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:15 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:16 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:17 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:20 2024 kern.info kernel: [168726.695513] br-lan: port 3(5ghzlow) entered learning state
Sat May 11 17:33:20 2024 kern.info kernel: [168727.335501] br-lan: port 4(5ghzhigh) entered learning state
Sat May 11 17:33:23 2024 daemon.debug mesh11sd[22246]: interface 5ghzlow is up
Sat May 11 17:33:23 2024 daemon.info mesh11sd[22246]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 17:33:23 2024 daemon.info mesh11sd[22246]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 17:33:23 2024 daemon.info mesh11sd[22246]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 17:33:23 2024 daemon.info mesh11sd[22246]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 17:33:23 2024 daemon.debug mesh11sd[22246]: Disconnecting nodes
Sat May 11 17:33:23 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:33:24 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:33:24 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:33:24 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 17:33:24 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 17:33:24 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 17:33:24 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 17:33:24 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 17:33:24 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 17:33:24 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 17:33:24 2024 kern.info kernel: [168731.032716] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:33:24 2024 kern.warn kernel: [168731.101811] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:24 2024 kern.warn kernel: [168731.101938] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:24 2024 kern.info kernel: [168731.201262] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:33:24 2024 kern.info kernel: [168731.203356] device 5ghzhigh left promiscuous mode
Sat May 11 17:33:24 2024 kern.info kernel: [168731.206225] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:33:24 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:24 2024 daemon.info mesh11sd[22246]: Old value:mesh_connected_to_as=0, Setting new value:mesh_connected_to_as=1
Sat May 11 17:33:24 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 17:33:24 2024 daemon.debug mesh11sd[22246]: node [DEST,ADDR]
Sat May 11 17:33:24 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:33:24 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:24 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 17:33:24 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 17:33:25 2024 daemon.notice netifd: radio0 (24147): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:33:25 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:33:25 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 17:33:25 2024 kern.info kernel: [168731.697640] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:33:25 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:33:25 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 17:33:25 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 17:33:25 2024 kern.info kernel: [168731.767155] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:33:25 2024 kern.info kernel: [168731.767239] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 17:33:25 2024 kern.warn kernel: [168731.816073] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:25 2024 kern.warn kernel: [168731.816169] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:25 2024 kern.info kernel: [168731.828878] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:33:25 2024 kern.info kernel: [168731.896168] device 5ghzlow left promiscuous mode
Sat May 11 17:33:25 2024 kern.info kernel: [168731.896247] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:33:25 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:25 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:33:25 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 17:33:25 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:25 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:25 2024 daemon.notice netifd: radio2 (24252): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:33:25 2024 daemon.notice netifd: radio0 (24147): command failed: Not supported (-95)
Sat May 11 17:33:25 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:25 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:25 2024 daemon.debug mesh11sd[22246]: checkinterval 10 seconds
Sat May 11 17:33:25 2024 daemon.notice netifd: radio2 (24252): command failed: Not supported (-95)
Sat May 11 17:33:26 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:26 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:26 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 17:33:26 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 17:33:26 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=30:23:03:2d:b0:88 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 17:33:28 2024 kern.warn kernel: [168735.272644] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 17:33:28 2024 kern.info kernel: [168735.279888] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:28 2024 kern.info kernel: [168735.279950] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:28 2024 kern.info kernel: [168735.284993] device 5ghzhigh entered promiscuous mode
Sat May 11 17:33:28 2024 kern.info kernel: [168735.295145] device 5ghzhigh left promiscuous mode
Sat May 11 17:33:28 2024 kern.info kernel: [168735.295419] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:28 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 17:33:28 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 17:33:28 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:28 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:28 2024 kern.info kernel: [168735.368284] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:28 2024 kern.info kernel: [168735.368371] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:28 2024 kern.info kernel: [168735.373487] device 5ghzhigh entered promiscuous mode
Sat May 11 17:33:28 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:28 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 17:33:28 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 17:33:30 2024 daemon.notice netifd: Interface 'lan6' has lost the connection
Sat May 11 17:33:30 2024 kern.info kernel: [168737.105080] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:30 2024 kern.info kernel: [168737.105147] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:30 2024 kern.info kernel: [168737.110137] device 5ghzlow entered promiscuous mode
Sat May 11 17:33:30 2024 daemon.notice netifd: lan (9912): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 17:33:30 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:30 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 17:33:30 2024 kern.info kernel: [168737.643494] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 17:33:30 2024 kern.info kernel: [168737.643815] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:30 2024 kern.info kernel: [168737.649443] br-lan: port 3(5ghzhigh) entered listening state
Sat May 11 17:33:30 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 17:33:31 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 17:33:31 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 17:33:31 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 17:33:31 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 17:33:32 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 17:33:32 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 17:33:32 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 17:33:32 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=91 id_str=]
Sat May 11 17:33:32 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 17:33:32 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=91
Sat May 11 17:33:32 2024 kern.info kernel: [168739.475516] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 17:33:32 2024 kern.info kernel: [168739.475854] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:32 2024 kern.info kernel: [168739.480978] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:33:32 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:33 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 17:33:33 2024 daemon.warn odhcp6c[9481]: Server returned message status 'Success (success)'
Sat May 11 17:33:33 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 17:33:34 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:33:36 2024 daemon.debug mesh11sd[22246]: interface 5ghzlow is up
Sat May 11 17:33:36 2024 daemon.info mesh11sd[22246]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 17:33:36 2024 daemon.info mesh11sd[22246]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 17:33:36 2024 daemon.info mesh11sd[22246]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 17:33:36 2024 daemon.info mesh11sd[22246]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 17:33:36 2024 daemon.debug mesh11sd[22246]: Disconnecting nodes
Sat May 11 17:33:36 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:33:37 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:33:37 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:33:37 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 17:33:37 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 17:33:37 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 17:33:37 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 17:33:37 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 17:33:37 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 17:33:37 2024 kern.info kernel: [168743.981694] device 5ghzhigh left promiscuous mode
Sat May 11 17:33:37 2024 kern.info kernel: [168743.981919] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:37 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 17:33:37 2024 kern.warn kernel: [168744.146432] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:37 2024 kern.warn kernel: [168744.146586] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:37 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:37 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 17:33:37 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:37 2024 daemon.info mesh11sd[22246]: Old value:mesh_connected_to_as=0, Setting new value:mesh_connected_to_as=1
Sat May 11 17:33:37 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 17:33:37 2024 kern.warn kernel: [168744.556305] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 17:33:37 2024 daemon.debug mesh11sd[22246]: node [DEST,ADDR]
Sat May 11 17:33:37 2024 daemon.notice netifd: radio0 (25385): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:33:37 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:33:37 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 17:33:37 2024 kern.info kernel: [168744.658807] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:38 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:33:38 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 17:33:38 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 17:33:38 2024 kern.info kernel: [168744.736874] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:38 2024 kern.info kernel: [168744.736954] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:33:38 2024 kern.warn kernel: [168744.795844] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:38 2024 kern.warn kernel: [168744.795955] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:38 2024 kern.info kernel: [168744.807720] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:38 2024 kern.info kernel: [168744.876119] device 5ghzlow left promiscuous mode
Sat May 11 17:33:38 2024 kern.info kernel: [168744.876199] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:38 2024 daemon.notice netifd: Interface 'lan6' is now up
Sat May 11 17:33:38 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:38 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:33:38 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 17:33:38 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:38 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:38 2024 daemon.notice netifd: radio2 (25488): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:33:38 2024 daemon.notice netifd: radio0 (25385): command failed: Not supported (-95)
Sat May 11 17:33:38 2024 user.notice firewall: Reloading firewall due to ifup of lan6 (br-lan)
Sat May 11 17:33:38 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:38 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:39 2024 daemon.notice netifd: radio2 (25488): command failed: Not supported (-95)
Sat May 11 17:33:39 2024 daemon.debug mesh11sd[22246]: checkinterval 10 seconds
Sat May 11 17:33:39 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:39 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:39 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 17:33:39 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 17:33:39 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=30:23:03:2d:b0:88 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 17:33:41 2024 kern.warn kernel: [168748.433211] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 17:33:41 2024 kern.info kernel: [168748.436827] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:41 2024 kern.info kernel: [168748.437972] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:41 2024 kern.info kernel: [168748.443983] device 5ghzhigh entered promiscuous mode
Sat May 11 17:33:41 2024 kern.info kernel: [168748.449533] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:41 2024 kern.info kernel: [168748.454206] br-lan: port 3(5ghzhigh) entered listening state
Sat May 11 17:33:41 2024 kern.info kernel: [168748.461794] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:41 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 17:33:41 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 17:33:41 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:41 2024 kern.info kernel: [168748.470988] device 5ghzhigh left promiscuous mode
Sat May 11 17:33:41 2024 kern.info kernel: [168748.471499] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:41 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:41 2024 kern.info kernel: [168748.530517] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:41 2024 kern.info kernel: [168748.530588] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:41 2024 kern.info kernel: [168748.535778] device 5ghzhigh entered promiscuous mode
Sat May 11 17:33:41 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:43 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:33:43 2024 kern.info kernel: [168750.245853] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.245926] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.250704] device 5ghzlow entered promiscuous mode
Sat May 11 17:33:43 2024 kern.info kernel: [168750.256126] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.261042] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.267080] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.274171] device 5ghzlow left promiscuous mode
Sat May 11 17:33:43 2024 kern.info kernel: [168750.277768] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.347668] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.347730] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:43 2024 kern.info kernel: [168750.352436] device 5ghzlow entered promiscuous mode
Sat May 11 17:33:43 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:43 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 17:33:43 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:43 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 17:33:44 2024 kern.info kernel: [168750.672363] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 17:33:44 2024 kern.info kernel: [168750.672645] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:44 2024 kern.info kernel: [168750.678217] br-lan: port 3(5ghzhigh) entered listening state
Sat May 11 17:33:44 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 17:33:44 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 17:33:44 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 17:33:44 2024 daemon.notice netifd: lan (9912): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 17:33:44 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 17:33:44 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:44 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 17:33:44 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 17:33:46 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 17:33:46 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 17:33:46 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 17:33:46 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 17:33:46 2024 kern.info kernel: [168753.631604] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 17:33:46 2024 kern.info kernel: [168753.631972] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:46 2024 kern.info kernel: [168753.637155] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:33:46 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=92 id_str=]
Sat May 11 17:33:46 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=92
Sat May 11 17:33:47 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:47 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 17:33:47 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 17:33:49 2024 daemon.debug mesh11sd[22246]: interface 5ghzlow is up
Sat May 11 17:33:49 2024 daemon.info mesh11sd[22246]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 17:33:49 2024 daemon.info mesh11sd[22246]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 17:33:49 2024 daemon.info mesh11sd[22246]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 17:33:49 2024 daemon.info mesh11sd[22246]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 17:33:49 2024 daemon.debug mesh11sd[22246]: Disconnecting nodes
Sat May 11 17:33:50 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:33:50 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:33:50 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:33:50 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 17:33:50 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 17:33:50 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 17:33:50 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 17:33:50 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 17:33:50 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 17:33:50 2024 kern.info kernel: [168757.191437] device 5ghzhigh left promiscuous mode
Sat May 11 17:33:50 2024 kern.info kernel: [168757.191693] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:50 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 17:33:50 2024 kern.warn kernel: [168757.286367] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:50 2024 kern.warn kernel: [168757.286494] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:50 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:50 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:50 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:50 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:50 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 17:33:50 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:50 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 17:33:50 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 17:33:50 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 17:33:50 2024 daemon.info mesh11sd[22246]: Old value:mesh_connected_to_as=0, Setting new value:mesh_connected_to_as=1
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 17:33:51 2024 kern.warn kernel: [168757.706216] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 2
Sat May 11 17:33:51 2024 daemon.notice netifd: radio0 (26621): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:33:51 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:33:51 2024 kern.info kernel: [168757.787871] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:51 2024 daemon.debug mesh11sd[22246]: node [DEST,ADDR]
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 17:33:51 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 17:33:51 2024 kern.info kernel: [168757.876950] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:51 2024 kern.info kernel: [168757.877021] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:33:51 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:33:51 2024 kern.warn kernel: [168757.936011] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:51 2024 kern.warn kernel: [168757.936095] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:33:51 2024 kern.info kernel: [168757.949139] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:51 2024 kern.info kernel: [168757.986625] device 5ghzlow left promiscuous mode
Sat May 11 17:33:51 2024 kern.info kernel: [168757.986707] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:51 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:51 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 17:33:51 2024 daemon.notice netifd: radio0 (26621): command failed: Not supported (-95)
Sat May 11 17:33:51 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:51 2024 daemon.notice netifd: radio2 (26732): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:33:51 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:51 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:51 2024 daemon.debug mesh11sd[22246]: checkinterval 10 seconds
Sat May 11 17:33:51 2024 daemon.notice netifd: radio2 (26732): command failed: Not supported (-95)
Sat May 11 17:33:52 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:33:52 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 17:33:52 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 17:33:52 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:52 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=30:23:03:2d:b0:88 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 17:33:52 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:33:54 2024 kern.warn kernel: [168761.244150] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 17:33:54 2024 kern.info kernel: [168761.250170] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.250250] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.255408] device 5ghzhigh entered promiscuous mode
Sat May 11 17:33:54 2024 kern.info kernel: [168761.260885] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.265587] br-lan: port 3(5ghzhigh) entered listening state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.271581] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:54 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 17:33:54 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 17:33:54 2024 kern.info kernel: [168761.283216] device 5ghzhigh left promiscuous mode
Sat May 11 17:33:54 2024 kern.info kernel: [168761.283518] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.332918] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.332998] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:33:54 2024 kern.info kernel: [168761.338207] device 5ghzhigh entered promiscuous mode
Sat May 11 17:33:54 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:54 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:33:54 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:33:54 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:54 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 17:33:54 2024 daemon.notice netifd: Interface 'lan6' has lost the connection
Sat May 11 17:33:56 2024 kern.info kernel: [168763.142576] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:56 2024 kern.info kernel: [168763.142640] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:33:56 2024 kern.info kernel: [168763.147484] device 5ghzlow entered promiscuous mode
Sat May 11 17:33:56 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:33:56 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 17:33:56 2024 daemon.notice netifd: lan (9912): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 17:33:56 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:33:57 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 17:33:57 2024 kern.info kernel: [168763.762849] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 17:33:57 2024 kern.info kernel: [168763.763161] br-lan: port 3(5ghzhigh) entered blocking state
Sat May 11 17:33:57 2024 kern.info kernel: [168763.768740] br-lan: port 3(5ghzhigh) entered listening state
Sat May 11 17:33:57 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 17:33:57 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 17:33:57 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 17:33:57 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 17:33:57 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=93 id_str=]
Sat May 11 17:33:58 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=93
Sat May 11 17:33:58 2024 kern.info kernel: [168765.004993] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 17:33:58 2024 kern.info kernel: [168765.005462] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:33:58 2024 kern.info kernel: [168765.010457] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:58 2024 daemon.warn odhcp6c[9481]: Server returned message status 'Success (success)'
Sat May 11 17:33:58 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:59 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:33:59 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 17:33:59 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 17:34:02 2024 daemon.debug mesh11sd[22246]: interface 5ghzlow is up
Sat May 11 17:34:02 2024 daemon.info mesh11sd[22246]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 17:34:02 2024 daemon.info mesh11sd[22246]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 17:34:02 2024 daemon.info mesh11sd[22246]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 17:34:02 2024 daemon.info mesh11sd[22246]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 17:34:02 2024 daemon.debug mesh11sd[22246]: Disconnecting nodes
Sat May 11 17:34:03 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:34:03 2024 daemon.info sh[22246]: 'radio1' is disabled
Sat May 11 17:34:03 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:34:03 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:34:03 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 17:34:03 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 17:34:03 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 17:34:03 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 17:34:03 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: Remove interface 5ghzlow
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-REMOVED 5ghzlow
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: leaving mesh
Sat May 11 17:34:03 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0
Sat May 11 17:34:03 2024 kern.info kernel: [168770.111495] device 5ghzhigh left promiscuous mode
Sat May 11 17:34:03 2024 kern.info kernel: [168770.111787] br-lan: port 3(5ghzhigh) entered disabled state
Sat May 11 17:34:03 2024 kern.warn kernel: [168770.118586] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 4
Sat May 11 17:34:03 2024 daemon.notice netifd: Network device '5ghzhigh' link is down
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state ENABLED->DISABLED
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-DISABLED
Sat May 11 17:34:03 2024 kern.warn kernel: [168770.236267] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:34:03 2024 kern.warn kernel: [168770.236435] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat May 11 17:34:03 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:34:03 2024 daemon.notice netifd: Network device '5ghzlow' link is down
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:34:03 2024 kern.info kernel: [168770.408530] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:34:03 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-DSCP-POLICY clear_all
Sat May 11 17:34:03 2024 daemon.notice wpa_supplicant[1044]: nl80211: deinit ifname=5ghzlow disabled_11b_rates=0
Sat May 11 17:34:03 2024 kern.info kernel: [168770.479130] br-lan: port 4(5ghzlow) entered blocking state
Sat May 11 17:34:03 2024 kern.info kernel: [168770.479216] br-lan: port 4(5ghzlow) entered listening state
Sat May 11 17:34:03 2024 daemon.err wpa_supplicant[1044]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat May 11 17:34:03 2024 kern.warn kernel: [168770.561249] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:34:03 2024 kern.warn kernel: [168770.561335] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 1
Sat May 11 17:34:03 2024 kern.info kernel: [168770.575609] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:34:03 2024 kern.info kernel: [168770.646103] device 5ghzlow left promiscuous mode
Sat May 11 17:34:03 2024 kern.info kernel: [168770.646180] br-lan: port 4(5ghzlow) entered disabled state
Sat May 11 17:34:04 2024 daemon.info mesh11sd[22246]: Failed to get current value of mesh_connected_to_gate, mesh interface not established.
Sat May 11 17:34:04 2024 daemon.notice netifd: Interface 'lan6' is now up
Sat May 11 17:34:04 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:34:04 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:34:04 2024 daemon.notice netifd: Wireless device 'radio2' is now down
Sat May 11 17:34:04 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat May 11 17:34:04 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:34:04 2024 daemon.info mesh11sd[22246]: Failed to get current value of mesh_connected_to_as, mesh interface not established.
Sat May 11 17:34:04 2024 daemon.notice netifd: radio2 (27865): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:34:04 2024 daemon.notice netifd: radio0 (27867): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 11 17:34:04 2024 user.notice firewall: Reloading firewall due to ifup of lan6 (br-lan)
Sat May 11 17:34:04 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:34:04 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:34:04 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 17:34:04 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:34:04 2024 daemon.notice netifd: radio2 (27865): command failed: Not supported (-95)
Sat May 11 17:34:04 2024 daemon.notice netifd: radio0 (27867): command failed: Not supported (-95)
Sat May 11 17:34:05 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:34:05 2024 daemon.notice hostapd: Set new config for phy phy2:
Sat May 11 17:34:05 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy2
Sat May 11 17:34:05 2024 daemon.debug mesh11sd[22246]: checkinterval 10 seconds
Sat May 11 17:34:05 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:34:06 2024 kern.info kernel: [168773.557654] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:34:06 2024 kern.info kernel: [168773.557724] br-lan: port 3(5ghzlow) entered disabled state
Sat May 11 17:34:06 2024 kern.info kernel: [168773.562487] device 5ghzlow entered promiscuous mode
Sat May 11 17:34:06 2024 daemon.notice wpa_supplicant[1044]: Set new config for phy phy0
Sat May 11 17:34:06 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:34:07 2024 daemon.notice netifd: Wireless device 'radio2' is now up
Sat May 11 17:34:07 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 11 17:34:07 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat May 11 17:34:07 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:34:07 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=FR ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=250 chanlist=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=106 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=100  interface=5ghzhigh bssid=30:23:03:2d:b0:88 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=REDACTED
Sat May 11 17:34:09 2024 kern.warn kernel: [168776.136076] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat May 11 17:34:09 2024 kern.info kernel: [168776.141393] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 17:34:09 2024 kern.info kernel: [168776.141473] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:34:09 2024 kern.info kernel: [168776.146963] device 5ghzhigh entered promiscuous mode
Sat May 11 17:34:09 2024 daemon.notice hostapd: 5ghzhigh: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 11 17:34:09 2024 daemon.notice hostapd: 5ghzhigh: interface state COUNTRY_UPDATE->HT_SCAN
Sat May 11 17:34:09 2024 kern.info kernel: [168776.157101] device 5ghzhigh left promiscuous mode
Sat May 11 17:34:09 2024 kern.info kernel: [168776.157353] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:34:09 2024 kern.info kernel: [168776.202478] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 17:34:09 2024 kern.info kernel: [168776.202550] br-lan: port 4(5ghzhigh) entered disabled state
Sat May 11 17:34:09 2024 kern.info kernel: [168776.207876] device 5ghzhigh entered promiscuous mode
Sat May 11 17:34:09 2024 daemon.notice netifd: lan (9912): udhcpc: sending renew to server 192.168.2.1
Sat May 11 17:34:09 2024 daemon.notice netifd: Interface 'lan' has lost the connection
Sat May 11 17:34:09 2024 daemon.notice netifd: Interface 'lan6' has lost the connection
Sat May 11 17:34:09 2024 daemon.notice netifd: lan (9912): udhcpc: broadcasting select for 192.168.2.80, server 192.168.2.1
Sat May 11 17:34:10 2024 daemon.notice netifd: lan (9912): udhcpc: lease of 192.168.2.80 obtained from 192.168.2.1, lease time 86400
Sat May 11 17:34:10 2024 daemon.notice netifd: Interface 'lan' is now up
Sat May 11 17:34:10 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat May 11 17:34:11 2024 daemon.warn odhcp6c[9481]: Server returned message status 'Success (success)'
Sat May 11 17:34:14 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:34:21 2024 daemon.notice netifd: Interface 'lan6' is now up
Sat May 11 17:34:21 2024 user.notice firewall: Reloading firewall due to ifup of lan6 (br-lan)
Sat May 11 17:34:24 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:34:25 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:34:33 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)
Sat May 11 17:34:35 2024 daemon.notice mesh11sd[22246]: 5ghzlow is not up - giving up for now.
Sat May 11 17:34:37 2024 daemon.notice netifd: radio0 (27867): Command failed: ubus call hostapd config_set { "phy": "phy0", "config":"/var/run/hostapd-phy0.conf", "prev_config": "/var/run/hostapd-phy0.conf.prev"} (Request timed out)
Sat May 11 17:34:37 2024 daemon.notice netifd: radio0 (27867): Device setup failed: HOSTAPD_START_FAILED
Sat May 11 17:34:37 2024 daemon.notice netifd: Wireless device 'radio0' set retry=0
Sat May 11 17:34:38 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat May 11 17:34:38 2024 kern.info kernel: [168805.186249] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzhigh: link becomes ready
Sat May 11 17:34:38 2024 kern.info kernel: [168805.186538] br-lan: port 4(5ghzhigh) entered blocking state
Sat May 11 17:34:38 2024 kern.info kernel: [168805.192069] br-lan: port 4(5ghzhigh) entered listening state
Sat May 11 17:34:38 2024 daemon.notice netifd: Network device '5ghzhigh' link is up
Sat May 11 17:34:38 2024 daemon.notice hostapd: 5ghzhigh: interface state HT_SCAN->ENABLED
Sat May 11 17:34:38 2024 daemon.notice hostapd: 5ghzhigh: AP-ENABLED
Sat May 11 17:34:38 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: interface state UNINITIALIZED->ENABLED
Sat May 11 17:34:38 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: AP-ENABLED
Sat May 11 17:34:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: joining mesh meshdwardo_5GHz
Sat May 11 17:34:39 2024 daemon.notice netifd: Network device '5ghzlow' link is up
Sat May 11 17:34:39 2024 kern.info kernel: [168805.890652] IPv6: ADDRCONF(NETDEV_CHANGE): 5ghzlow: link becomes ready
Sat May 11 17:34:39 2024 kern.info kernel: [168805.890996] br-lan: port 3(5ghzlow) entered blocking state
Sat May 11 17:34:39 2024 kern.info kernel: [168805.896169] br-lan: port 3(5ghzlow) entered listening state
Sat May 11 17:34:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=94 id_str=]
Sat May 11 17:34:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=94
Sat May 11 17:34:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 17:34:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 17:34:39 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 17:34:40 2024 daemon.info mesh11sd[22246]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 17:34:40 2024 daemon.info mesh11sd[22246]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 17:34:40 2024 daemon.info mesh11sd[22246]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 17:34:40 2024 daemon.info mesh11sd[22246]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 17:34:40 2024 daemon.info mesh11sd[22246]: Path to station [ 30:23:03:99:bd:7d ] is stable
Sat May 11 17:34:40 2024 daemon.debug mesh11sd[22246]: checkinterval 10 seconds
Sat May 11 17:34:42 2024 daemon.err dawn: connect_cb()=tcpsocket.c@319 Connection failed (ERROR)

Got it to work (once at least...) I was getting the feeling that

the connection was just not getting enough time to establish
the checkinterval were coming up to quick and generating the restart_mesh from all_nodes_rssi_update ... so I increased checkinterval to 300 and interface_timeout to 60.

Now I need to figure out more reasonable values and if/how they interact...

@dwardor What do you have in the mesh11sd config? If the value of mesh_rssi_threshold is different in the wireless config to that in the mesh11sd config, the mesh gets reset to ensure all nodes use the value. It applies only at connection time.

The mesh_rssi_threshold parameter is one of the very few settable from the wireless config, so remove it from mesh11sd.

interface_timeout 10 & checkinterval 300 works... but the first time interval restart_mesh is called by all_nodes_rssi_update because mesh_rssi_threshold needs to be changed... instead of just

Sat May 11 18:17:49 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=128 id_str=]
Sat May 11 18:17:49 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-GROUP-STARTED ssid="meshdwardo_5GHz" id=128
Sat May 11 18:17:49 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: new peer notification for 30:23:03:99:bd:7d
Sat May 11 18:17:50 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: mesh plink with 30:23:03:99:bd:7d established
Sat May 11 18:17:50 2024 daemon.notice wpa_supplicant[1044]: 5ghzlow: MESH-PEER-CONNECTED 30:23:03:99:bd:7d
Sat May 11 18:17:57 2024 kern.info kernel: [171403.800513] br-lan: port 4(5ghzhigh) entered learning state
Sat May 11 18:17:57 2024 kern.info kernel: [171404.440528] br-lan: port 3(5ghzlow) entered learning state
Sat May 11 18:18:05 2024 kern.info kernel: [171412.120458] br-lan: port 4(5ghzhigh) entered forwarding state
Sat May 11 18:18:05 2024 kern.info kernel: [171412.120534] br-lan: topology change detected, propagating
Sat May 11 18:18:06 2024 kern.info kernel: [171412.760470] br-lan: port 3(5ghzlow) entered forwarding state
Sat May 11 18:18:06 2024 kern.info kernel: [171412.760560] br-lan: topology change detected, propagating
Sat May 11 18:22:14 2024 daemon.debug mesh11sd[12715]: interface 5ghzlow is up
Sat May 11 18:22:14 2024 daemon.info mesh11sd[12715]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16
Sat May 11 18:22:15 2024 daemon.info mesh11sd[12715]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=4
Sat May 11 18:22:15 2024 daemon.info mesh11sd[12715]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1
Sat May 11 18:22:15 2024 daemon.info mesh11sd[12715]: Old value:mesh_rssi_threshold=-79, Setting new value:mesh_rssi_threshold=-80
Sat May 11 18:22:15 2024 daemon.debug mesh11sd[12715]: Disconnecting nodes
Sat May 11 18:22:15 2024 daemon.info sh[12715]: 'radio1' is disabled
Sat May 11 18:22:15 2024 daemon.info sh[12715]: 'radio1' is disabled
Sat May 11 18:22:15 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat May 11 18:22:15 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat May 11 18:22:15 2024 daemon.notice hostapd: 5ghzhigh: interface state ENABLED->DISABLED
Sat May 11 18:22:15 2024 daemon.notice hostapd: 5ghzhigh: AP-DISABLED
Sat May 11 18:22:15 2024 daemon.notice hostapd: 5ghzhigh: CTRL-EVENT-TERMINATING
Sat May 11 18:22:15 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat May 11 18:22:15 2024 daemon.notice hostapd: nl80211: deinit ifname=5ghzhigh disabled_11b_rates=0

The issue I think is that mesh_rssi_treshhold is set both in

wireless.default_radio2.mesh_rssi_threshold='-79'
mesh11sd.mesh_params.mesh_rssi_threshold='-80' causing a restart_mesh at each checkinterval because

at mesh start it is set to -79 through wireless configuration paramaters
mesh11sd then checks it sees its not OK modifies it, calls all_nodes_rssi_update that calls and restarts_mesh --> and we go back to 1. and cycle... So when checkinterval is 10s... were are cycling the mesh_restart

--> Confirmed with the following test: if I set mesh11sd.mesh_params.mesh_rssi_threshold='79' and checkinterval='10' and interface_timeout='10' it works great !

Am I wrong in thinking:

we need to check/warn if mesh_rssi_threshold is set in both wireless.default_radio2 and mesh11sd.mesh_params and maybe use that from mesh11sd to overwrite that of wireless
all_nodes_rssi_update should only be called if auto_config -eq 1 because its playing with wireless.m11s$phyindex.mesh_rssi_threshold which exists only in auto_config -eq 1 mode

@dwardor What do you have in the mesh11sd config? If the value of mesh_rssi_threshold is different in the wireless config to that in the mesh11sd config, the mesh gets reset to ensure all nodes use the value. It applies only at connection time.

The mesh_rssi_threshold parameter is one of the very few settable from the wireless config, so remove it from mesh11sd.

Yes that is it... saw your comment after posting mine !!! Still think a small check and using that of mesh11sd (by overwriting that in wireless) if both are present is better !

@dwardor Sat May 11 17:34:40 2024 daemon.info mesh11sd[22246]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?

The next question is why is this happening?

You should get something like this in the nft ruleset (example from a running system here):

table bridge mesh11s {
    chain mesh_PRE {
        type filter hook prerouting priority -350; policy accept;
        iifname "phy0-ap0" ether saddr 94:83:c4:06:71:50 counter packets 0 bytes 0 drop
        iifname "phy0-ap0" counter packets 33676 bytes 4162392 accept
        iifname "eth0.1" ether saddr 94:83:c4:06:71:50 counter packets 0 bytes 0 drop
        iifname "eth0.1" counter packets 0 bytes 0 accept
        iifname "m-11s-0" ether saddr 94:83:c4:06:71:50 counter packets 0 bytes 0 drop
        iifname "m-11s-0" counter packets 67238 bytes 52750994 accept
    }
}

What happens if you do:

nft add table bridge mesh11s
nft add chain bridge mesh11s mesh_PRE { type filter hook prerouting priority -350\; }

root@a03_1:~# nft add table bridge mesh11s
root@a03_1:~# echo $?

root@a03_1:~# nft add chain bridge mesh11s mesh_PRE { type filter hook prerouting priority -350\; }
root@a03_1:~# echo $?
0

@dwardor

all_nodes_rssi_update should only be called if auto_config -eq 1 because its playing with wireless.m11s$phyindex.mesh_rssi_threshold which exists only in auto_config -eq 1 mode

It has to because when the mesh comes up it uses the value in wireless config. If wireless config was not overwritten, you would have a restart mesh loop.

It will have to be "ignore mesh_rssi_threshold in mesh11sd config if auto_config=0"

root@a03_1:~# nft list table bridge mesh11s
table bridge mesh11s {
        chain mesh_PRE {
                type filter hook prerouting priority -350; policy accept;
                iifname "lan" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop
                iifname "lan" counter packets 0 bytes 0 accept
                iifname "wan" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop
                iifname "wan" counter packets 13602 bytes 2004449 accept
        }
}

It has to because when the mesh comes up it uses the value in wireless config. If wireless config was not overwritten, you would have a restart mesh loop.

yes but setcion wireless.m11s$phyindex is created and used in if auto_config==1... so a if auto_config==1 is missing in all_nodes_rssi_update (or befoire calling it) in check_mesh_params

@dwardor root@a03_1:~# nft list table bridge mesh11s

So it is working now. You have mesh11sd running? As soon you created the table and chain mesh11sd added in the rules. So why is mesh11sd not adding the table and chain?

@dwardor This works for me but does not work for you:

    table_ruleset=$(nft -a list table bridge mesh11s 2> /dev/null)

    if [ "$?" -gt 0 ]; then
        # Create the table
        nft add table bridge mesh11s
        # Create the chain
        nft add chain bridge mesh11s mesh_PRE { type filter hook prerouting priority -350\; }
    fi

Hand typed commands worked, but what mesh11sd tries to do does not

Sat May 11 19:38:01 2024 daemon.info mesh11sd[6022]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 19:38:01 2024 daemon.info mesh11sd[6022]: ******* WARNING ******* Unable to add nftables rule(s) - error code [ 1 ]. Is the kmod-nft-bridge package installed?
Sat May 11 19:38:01 2024 daemon.info mesh11sd[6022]: ******* WARNING ******* A severe mesh bridge-loop storm is likely to occur if any non-mesh backhaul segments are used!
Sat May 11 19:38:01 2024 daemon.info mesh11sd[6022]: -------------------------------------------------------------------------------------------------------------------------
Sat May 11 19:38:02 2024 daemon.debug mesh11sd[6022]: checkinterval 10 seconds

@dwardor

Hand typed commands worked, but what mesh11sd tries to do does not

It tries and succeeds on everything it has been tested on - except with your setup..... Why?

@dwardor Fix - If auto_config=0, then if mesh_rssi_threshold is in mesh11sd config, it is set set but will not apply to any already connected nodes: Beta 11 mesh11sd.tar.gz

@dwardor table_ruleset=$(nft -a list table bridge mesh11s 2> /dev/null) has exit code "1" if the table does not exist, or at least that is what happens here.....

beta11 looks good :-) !

on line 2917 meshconfig is used ouside the for loop (lines 2892-2903) that defined it... So using last value before llop exit... is this voluntary or a bug ?
looking into the nft issue

While mesh11sd is running...

service firewall status
active with no instances

nft -a list table bridge mesh11s
table bridge mesh11s { # handle 26
        chain mesh_PRE { # handle 1
                type filter hook prerouting priority -350; policy accept;
                iifname "lan" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop # handle 2
                iifname "lan" counter packets 0 bytes 0 accept # handle 3
                iifname "wan" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop # handle 4
                iifname "wan" counter packets 23503 bytes 3503024 accept # handle 5
        }
}

so lan and wan have their required 2 rules but 5ghzlow and 5ghzhigh don't (they have none) so those are the ones failing

root@a03_1:~# nft add rule bridge mesh11s mesh_PRE meta iifname { 5ghzlow } counter accept
Error: syntax error, unexpected string, expecting comma or '}'
add rule bridge mesh11s mesh_PRE meta iifname { 5ghzlow } counter accept

root@a03_1:~# nft add rule bridge mesh11s mesh_PRE meta iifname { 5ghzlow } ether saddr 30:23:03:2d:b0:85 counter drop
Error: syntax error, unexpected string, expecting comma or '}'
add rule bridge mesh11s mesh_PRE meta iifname { 5ghzlow } ether saddr 30:23:03:2d:b0:85 counter drop

@dwardor

on line 2917 meshconfig is used outside the for loop

This is intended as all mesh interfaces will be given the same locally administered mac, with only one interface enabled.

If at some stage mesh11sd auto_configure is extended to allow more than 1 active mesh interface, it might become problematic, so worth noting.

root@a03_1:~# nft add rule bridge mesh11s mesh_PRE meta iifname { \"5ghzlow\" } ether saddr 30:23:03:2d:b0:85 counter d
rop
root@a03_1:~# echo $?
0

root@a03_1:~# nft -a list table bridge mesh11s
table bridge mesh11s { # handle 26
        chain mesh_PRE { # handle 1
                type filter hook prerouting priority -350; policy accept;
                iifname "lan" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop # handle 2
                iifname "lan" counter packets 0 bytes 0 accept # handle 3
                iifname "wan" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop # handle 4
                iifname "wan" counter packets 117003 bytes 92251923 accept # handle 5
                iifname "5ghzlow" ether saddr 30:23:03:2d:b0:85 counter packets 0 bytes 0 drop # handle 6
        }
}

I'm guessing this is the first time you have someone with an iifname starting with a numeric :-)

so here is the patch that fixes it :-) !

--- /usr/sbin/mesh11sd.ori      2024-05-11 21:41:20.000000000 +0200
+++ /usr/sbin/mesh11sd  2024-05-11 21:42:20.000000000 +0200
@@ -1871,8 +1871,8 @@
                rulecount=$(nft -a list table bridge mesh11s 2> /dev/null | grep -w -c "$br_iface" | awk '{printf "%s", $1}')

                if [ "$rulecount" -lt 2 ]; then
-                       rule_status=$(nft add rule bridge mesh11s mesh_PRE meta iifname { $br_iface } ether saddr "\"$devicemac\"" counter drop 2> /dev/null; echo -n $?)
-                       rule_status=$(nft add rule bridge mesh11s mesh_PRE meta iifname { $br_iface } counter accept 2> /dev/null; echo -n $?)
+                       rule_status=$(nft add rule bridge mesh11s mesh_PRE meta iifname { "\"$br_iface\"" } ether saddr "\"$devicemac\"" counter drop 2> /dev/null; echo -n $?)
+                       rule_status=$(nft add rule bridge mesh11s mesh_PRE meta iifname { "\"$br_iface\"" } counter accept 2> /dev/null; echo -n $?)
                fi

                convert_to_la "$devicemac"

can you share a beta12 ;-) ?

@dwardor

I'm guessing this is the first time you have someone with an iifname starting with a numeric :-)

Well spotted! Of course, auto_config enforces a non-numeric start. ;-)

I propose you add this to the mesh_params section of the config file maybe with a warning that they are useful examples only in auto_config=0

        # For a Portal Node: having wired connectivity to upstream [and eventually downstream connectivity]
        #    option mesh_fwding '1'
        #    option mesh_connected_to_as '1' [if link is up or '0' when down]
        #    option mesh_hwmp_rootmode '4'
        #    option mesh_connected_to_gate '1' [if it also supports an AP or '0']

        # For a Gateway Node: offering downstream connectivity via AP or wired but no upstream connectivity
        #    option mesh_fwding '1'
        #    option mesh_connected_to_as '0'
        #    option mesh_hwmp_rootmode '2'
        #    option mesh_connected_to_gate '1'

        # For a Gateway Leach Node: a Gateway that doesn't contribute to the mesh just leaches off of it
        #    option mesh_fwding '0'
        #    option mesh_connected_to_as '0'
        #    option mesh_hwmp_rootmode '0'
        #    option mesh_connected_to_gate '1'

        # For a Peer Node: just connected to mesh offering nothing else
        #    option mesh_fwding '1'
        #    option mesh_connected_to_as '0'
        #    option mesh_hwmp_rootmode '2'
        #    option mesh_connected_to_gate '0'

@dwardor Beta 12: mesh11sd.tar.gz

@dwardor

I propose you add this to the mesh_params section of the config file maybe with a warning that they are useful examples only in auto_config=0

I disagree with your interpretation, which is naturally biassed towards your very unusual edge case scenario ;-)

I will rewrite this... using the definitions used by mesh11sd, in turn derived from the original 802.11s standard.

@dwardor Something like this:

        # The following options are recommended when auto_config = 0
        # A Portal Node: having an ip routed connectivity to an upstream feed [eg an Internet feed]
        #    option mesh_fwding '1'
        # 
        #    option mesh_connected_to_as '1' [if link is up]
        # or
        #    option mesh_connected_to_as '0' [if link is down]
        # 
        #    option mesh_hwmp_rootmode '4'
        # 
        #    option mesh_connected_to_gate '1' [if it also supports an AP]
        # or
        #    option mesh_connected_to_gate '0' [if it does not support an AP]
        # 
        #    option mesh_gate_announcements '1'  [if it also supports an AP]
        # or
        #    option mesh_gate_announcements '0'  [if it does not support an AP]

        # A Gateway Node: offering both backhaul and downstream infrastructure connectivity 
        #    option mesh_fwding '1'
        #    option mesh_connected_to_as '0'
        #    option mesh_hwmp_rootmode '2'
        #    option mesh_connected_to_gate '1'
        #    option mesh_gate_announcements '1' 

        # A Gateway Leech Node: a Gateway that doesn't contribute to the mesh backhaul, it just leeches off of it
        #    option mesh_fwding '0'
        #    option mesh_connected_to_as '0'
        #    option mesh_hwmp_rootmode '0'
        #    option mesh_connected_to_gate '1'
        #    option mesh_gate_announcements '0' 

        # A Peer Node: connected to mesh backhaul but no downstream infrastructure
        #    option mesh_fwding '1'
        #    option mesh_connected_to_as '0'
        #    option mesh_hwmp_rootmode '2'
        #    option mesh_connected_to_gate '0'
        #    option mesh_gate_announcements '0'

Fine by me ! Just remove the duplicates entrie for portal

        #    option mesh_connected_to_gate '1' [if it also supports an AP]
        #    option mesh_connected_to_gate '0' [if it does not support an AP]

@dwardor I edited it in place. How does it look now?

@dwardor How is Beta 12 working?

Ran all night without issue :1st_place_medal:

@dwardor An exercise well worth doing. I have some more tests to do with mt76 hardware where there are issues, particularly with kernel 6+ After that, update documentation then ready for release.

ThI deployed it yesterday on a 4 node mesh. This morning connectivity of certain nodes was bad... Trying to find the good mesh_rssi_threshold to avoid low speed extraneous links.

Do you confirm that if auto_config = 0 using the -ct ath10k driver and firmwares should not be an issue ?

@dwardor

Do you confirm that if auto_config = 0 using the -ct ath10k driver and firmwares should not be an issue ?

In my experience it is ALWAYS an issue and non-ct is required. There are various issues wit ct drivers including some or all of the following

mesh encryption does not work all the time
mesh interfaces take one of the limited connection number allowed with ct drivers leading to failures oof eithe mesh peer links or ap connections on a shared radio
ct drivers use a disproportionally large amount of memory for every connection, be it client/ap or mesh, leading to possible oom problems in devices with low resources.

I have not re-visited this recently so something may have been fixed, but I considered id a waste of time to try when the non-ct drivers are easy to install.

With regard to rssi_threshold, mesh11sd has some tools to help with this.

Look at: mesh11sd status

This will show all active peers. Look for the values of "hop_count", "path_change_count" and "metric"

When the "path_change_count" is incrementing with time, this means there are multiple paths active to the particular node. This can happen for many reasons, but the most common is actual reflections of the wireless microwave signals and can rapidly vary as weather changes, vehicles move around, trees wave in the wind, people and animals move around etc etc even inside a building. This is no problem for layer 2 packets to get through, but TCP-IP layer 3 will have big problems causing retries, dropped packets and even broken connections.

Status output example:

        "96:83:c4:06:71:50":{
          "next_hop":"96:83:c4:06:71:50"
          "hop_count":"1"
          "path_change_count":"7886"
          "metric":"796"
        },

In this example, the node 96:83:c4:29:f5:a4 is within the coverage area of two others including this one. The path_change_count is incrementing steadily and the link from this node is regarded as unstable from a layer 3 perspective.

If you do: mesh11sd debuglevel 3 followed by: logread -f -e mesh11sd

you will see something like:

Mon May 13 07:34:56 2024 daemon.warn mesh11sd[1763]: Warning! Station [ 96:83:c4:06:71:50 ] is [ 2 ] hops away and [ 7893 ] path_change(s) for station have been detected
Mon May 13 07:34:56 2024 daemon.warn mesh11sd[1763]: Warning! Station [ 96:83:c4:06:71:50 ], consider its location or adjust txpower and/or rssi_threshold
Mon May 13 07:34:56 2024 daemon.info mesh11sd[1763]: Path to station [ 96:83:c4:22:c6:c3 ] is stable

You can see the hop count has changed as well as the path changes count.

In a scenario like this there are 2 main options,

Adjust txpower and mesh_rssi_threshold
Change one of the nodes into a leech node

In my example there were 4 nodes spaced out to be within immediate peer range but outwith range of "2 hop" nodes. eg:

node1 ------------ node2 ------------ node3 ------------ node4

All was well, all links stable.

Then a fifth node was introduced and placed between node1 and node2 eg: node1 ---- node5 -------- node2 ------------ node3 ------------ node4

Now, node2 can peer with both node5 and node1 In itself this is fine, but we are talking about the physics of microwave propagation here. Tiny changes in reflections can have a large effect (that of course is how radar works). The result can be changes in the path taken by packets between node1 and node2

In the example, node 5 was set to leech mode. It can then connect to the portal (node1), but does not advertise itself as a peer in any way, so node2 does not forward packets to it, solving the problem.

This could have been solved with careful tuning of txpower and rssi threshold, but as node5 was quite close to node1, leech mode is a better solution as this was intended as a "fill in" for an area of low wifi signal for users.

@dwardor Another useful tool is: mesh11sd stations This lists all the nodes or " mesh stations" that are trying to connect or have achieved connection along with received signal strengths.

In my example there were 4 nodes spaced out to be within immediate peer range but outwith range of "2 hop" nodes. eg:

node1 ------------ node2 ------------ node3 ------------ node4

All was well, all links stable.

Then a fifth node was introduced and placed between node1 and node2 eg: node1 ---- node5 -------- node2 ------------ node3 ------------ node4

Now, node2 can peer with both node5 and node1 In itself this is fine, but we are talking about the physics of microwave propagation here. Tiny changes in reflections can have a large effect (that of course is how radar works). The result can be changes in the path taken by packets between node1 and node2

In the example, node 5 was set to leech mode. It can then connect to the portal (node1), but does not advertise itself as a peer in any way, so node2 does not forward packets to it, solving the problem.

I have a layout like so (node 1 is bridged portal and all other were gateways) with altitude effects (!= levels) on top... something like

           node 3 ------- node 4
            / \           /
          /     \       /
        /         \   /
node 1 ------ node 2

setting proper mesh_rssi_threshold '-68' I stopped the bad/weak link between node 1 and 4 (jumps from '-70' to '-80')... and just turned node 4 to gateway leech thanks to your explanations

however now node 2 tries but "fails" (0 badnwidth) to connect to node 4 (this is what node 3 show for its connected peers)... is this normal ? a leech only connects to its "best" peer' (node 3 in node 4's case ?)

node 4 doesn't even list node 2

@dwardor

altitude effects

Lol. Yes moving to a 2d diagram from my simple 1 dimensional version. Now lets see you do a 3d diagram ;-) Ha Ha!

You can see what is happening by looking at mesh11sd stations on each node. Setting mesh_rssithreshold on all nodes is desirable to tie down paths, not necessarily as far as blocking, but far enough to increase the metric for the link. Reducing txpower also helps with this. The first choice path will be the one with the lowest metric,_ falling back to a path with a higher metric (handled by HWMP).

however now node 2 tries but "fails" (0 badnwidth) to connect to node 4

This is normal, depending on how you have set rssi and txpower on 2 and 4. In addition, node 4 is set to leech mode so will indeed connect just to the lowest metric root node it can find. Node 2 can see node 4 but gets no response from the PREQs it sends, because 4 is a leech and is connected elsewhere at a lower metric.

Lol. Yes moving to a 2d diagram from my simple 1 dimensional version. Now lets see you do a 3d diagram ;-) Ha Ha!

Actually that diagram was in xy plane... the altitude effects I did not add are in z ;-) as I have 3 levels in the house. node 1 and 1 are on level 1, 3 is on level 2 and 4 is on level 3.

My Ap radios were "going down" [I'd have the radio say it was set at 0db power... and restarting the radio would do nothing... only changing channel or rebooting would bring it back...] so I decided to try the -ct drivers again because I didn't remember that happening with them...

To sum things up after this test:

-ct is more finecky on mesh_rssi_threshold
rssi are much lower (and decrease much faster)
but iperf3 measured transfer speeds are better

With non -ct drivers:

my setup used mesh_rssi_threshold = -68

the links were

       node 3 ------- node 4
        / \           /
      /     \       /
    /         \   /
node 1 ------ node 2

node 1 to node 3 or node 2 speeds were 200Mb/s
node1 to node4 speed was ~90Mb/s

With -ct drivers

my setup had to decrease the mesh_rssi_threshold to -73

the links are

       node 3 ------- node 4
        /
      /
    / 
node 1 ------ node 2

decreasing mesh_rssi_threshold to -78 lead to no topology change (did not go fiurther)...
node 1 to node 3 or node 2 speeds are 300Mb/s
node1-node4 speed is ~180Mb/s (a great improvement !)

So I'll test this some more to see if my APs are stable or not ! If yes I will stay with -ct drivers

Can confirm in auto_config=0 mode mesh11sd does not check/care if -ct drivers are used :-) !

@dwardor FYI: Version 4.0.0 is released https://github.com/openNDS/mesh11sd/releases/tag/v4.0.0

openNDS / mesh11sd

Improving Documentation and better understanding it #60