search

openNDS / mesh11sd

Mesh11sd is a dynamic parameter configuration daemon for 802.11s mesh networks.
GNU General Public License v2.0
28 stars 4 forks source link

kernel 6.6: mesh11d crashes network after 1 minute (from fresh/reset config) #51

Closed AcidSlide closed 1 month ago

AcidSlide commented 2 months ago

Hi,

As most are already transitioning to kernel 6.6, mesh11d crashes the network upon reset or new config. This has happened on. my rampis devices (reset config). At first I thought it was due to the kernel 6.6 having issue but after updating my test router using a qualcommax/ipq60xx profile, that is when I found what the issue was via UART console.

The issue is triggered with the following scenario:

Note: WAN is connected to my primary router with internet connection available. LAN1 connected to my compputer.

Things to notices, LAN connection to the router keeps resetting (I can see via my network details in computer, the LAN connection keeps on disconnecting and reconnecting every 5 to 10 seconds). And after a minute, almost disables the network layer and wrecks havocs to the devices that are connected to the eth ports including the WAN port which also somehow temporarily affects my primary router when it happens.

Below is the log coming from my test router

[   16.716438] br-lan: port 1(lan1) entered blocking state
[   16.716482] br-lan: port 1(lan1) entered disabled state
[   16.720526] nss-dp 3a001000.dp1 lan1: entered allmulticast mode
[   16.726042] nss-dp 3a001000.dp1 lan1: entered promiscuous mode
[   16.751408] br-lan: port 2(lan2) entered blocking state
[   16.751463] br-lan: port 2(lan2) entered disabled state
[   16.755608] nss-dp 3a001200.dp2 lan2: entered allmulticast mode
[   16.760923] nss-dp 3a001200.dp2 lan2: entered promiscuous mode
[   16.778006] br-lan: port 3(lan3) entered blocking state
[   16.778055] br-lan: port 3(lan3) entered disabled state
[   16.782178] nss-dp 3a001400.dp3 lan3: entered allmulticast mode
[   16.787542] nss-dp 3a001400.dp3 lan3: entered promiscuous mode
[   16.799948] br-lan: port 4(lan4) entered blocking state
[   16.799998] br-lan: port 4(lan4) entered disabled state
[   16.804317] nss-dp 3a001600.dp4 lan4: entered allmulticast mode
[   16.809809] nss-dp 3a001600.dp4 lan4: entered promiscuous mode
[   19.400942] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   19.810923] nss-dp 3a001000.dp1 lan1: PHY Link up speed: 1000
[   19.811004] br-lan: port 1(lan1) entered blocking state
[   19.815662] br-lan: port 1(lan1) entered forwarding state
[   19.938914] nss-dp 3a001800.dp5 wan: PHY Link up speed: 1000
[   34.227728] br-lan: port 5(phy0-ap0) entered blocking state
[   34.227766] br-lan: port 5(phy0-ap0) entered disabled state
[   34.232169] ath11k c000000.wifi phy0-ap0: entered allmulticast mode
[   34.237953] ath11k c000000.wifi phy0-ap0: entered promiscuous mode
[   34.295299] br-lan: port 6(m-11s-1) entered blocking state
[   34.295354] br-lan: port 6(m-11s-1) entered disabled state
[   34.299865] ath11k c000000.wifi m-11s-1: entered allmulticast mode
[   34.305511] ath11k c000000.wifi m-11s-1: entered promiscuous mode
[   34.311697] br-lan: port 6(m-11s-1) entered blocking state
[   34.317539] br-lan: port 6(m-11s-1) entered forwarding state
[   34.328752] br-lan: port 6(m-11s-1) entered disabled state
[   34.747754] br-lan: port 5(phy0-ap0) entered blocking state
[   34.747810] br-lan: port 5(phy0-ap0) entered forwarding state
[   47.625753] ath11k c000000.wifi m-11s-1: left allmulticast mode
[   47.625815] ath11k c000000.wifi m-11s-1: left promiscuous mode
[   47.630654] br-lan: port 6(m-11s-1) entered disabled state
[   64.900421] br-lan: port 6(phy1-ap0) entered blocking state
[   64.900471] br-lan: port 6(phy1-ap0) entered disabled state
[   64.904969] ath11k c000000.wifi phy1-ap0: entered allmulticast mode
[   64.910721] ath11k c000000.wifi phy1-ap0: entered promiscuous mode
[   64.992798] br-lan: port 6(phy1-ap0) entered blocking state
[   64.992861] br-lan: port 6(phy1-ap0) entered forwarding state
[   84.873352] br-lan: port 4(lan4) entered disabled state
[   84.939648] br-lan: port 2(lan2) entered disabled state
[   85.009121] br-lan: port 3(lan3) entered disabled state
[   85.077916] nss-dp 3a001000.dp1 lan1: PHY Link is down
[   85.078336] br-lan: port 1(lan1) entered disabled state
[   88.162801] nss-dp 3a001000.dp1 lan1: PHY Link up speed: 1000
[   88.162898] br-lan: port 1(lan1) entered blocking state
[   88.167544] br-lan: port 1(lan1) entered forwarding state
[  127.947092] br-lan: port 5(phy0-ap0) entered disabled state
[  127.948603] ath11k c000000.wifi phy0-ap0: left allmulticast mode
[  127.951500] ath11k c000000.wifi phy0-ap0: left promiscuous mode
[  127.957913] br-lan: port 5(phy0-ap0) entered disabled state

Only way to recover is switching to openwrt failover mode and manually disabling mesh11d from starting up. Even if you reset (power off/on), you won't have time to configure via luci or ssh because the connection on the LAN ports are also resetting.

AcidSlide commented 2 months ago

I would like to note, that when I updated one of my primary routers using rampis/mt7621 using a build that uses the test kernel 6.6. I have observed the very similar lan ports disconnecting reconnecting every few seconds and after some time wrecks network havoc to all connected devices via lan.

Since I was testing the 6.6 kernal, during the sysupgrade I disabled the "Keep Settings" to reset the config.

bluewavenet commented 2 months ago

@AcidSlide

Thankyou for this.

As most are already transitioning to kernel 6.6

It is the OpenWrt project plan to move to kernel 6.6 wherever possible before the next major release (ie 24.x.0 or 25.x.0).

Yes I have seen work starting on this and people can indeed build some architectures as a test of the work in progress. It is a little premature to say "most are transitioning", but yes this is very interesting.

Are there any official releases on master/snapshot yet? I am running master/snapshot here on mt7621 with no problems - but it is not kernel 6.6 either. For now it is difficult to sensibly look at the issue.

I will reflash the mt7621 device I have in my test network with the latest snapshot to see what has changed.

AcidSlide commented 2 months ago

Thanks @bluewavenet .. so far I'm only observing the issue when using k6.6

bluewavenet commented 2 months ago

@AcidSlide I reflashed a gl-inet mt1300 (mt7621) with current master/snapshot and can confirm the problem. The previous kernel was 5.something, I forgot to check the exact version. Now the kernel is 6.1.82. Pre 6.x, but after dsa, many devices seemed to duplicate mac addresses for interfaces. In turn many wireless drivers would fail to either bring up a mesh interface, or drop the ap interface on the same physical radio. Mesh11sd fixed this giving locally administered mac addresses in place of duplicates.

A quick look at what happens with kernel 6.x snapshots is the logic fails somewhere resulting in various symptoms similar to what you have found. Kernel is updated but also dsa is probably fixed also. I will look closer but I guess it will be a fairly simple patch to fix this... ;-)

bluewavenet commented 2 months ago

@AcidSlide I have worked out a patch that seems to fix this. It needs more testing and a tidy up, so a job for the weekend. It needs to check for major kernel version, ie 5 or 6.

I also need to test with different hardware.

Can I assume you would be interested in testing the completed patch?

AcidSlide commented 2 months ago

Can I assume you would be interested in testing the completed patch?

Yes, I would help in testing it.

AcidSlide commented 2 months ago

@bluewavenet by the way.. I know you are testing the fixes for kernel 6.x but I would like to inform you that on my routers running kernel 6.1.82 no issues yet with mesh11d so it seems kernel versions above this are having the issues.

bluewavenet commented 2 months ago

@AcidSlide The issue seems to be wireless driver/kernel 6+ combinations.

The new release is going to be a new major version as there are incompatibilities when upgrading from v3.x.x ie v4.0.0

Are you willing to test it? Can you package from source or would you like an ipk to install?

AcidSlide commented 2 months ago

Are you willing to test it? Can you package from source or would you like an ipk to install?

Yes I can test.. i'll try building from source.. just need to update my local build

I will give you feedback once I am able to do some test @bluewavenet

AcidSlide commented 2 months ago

@bluewavenet

Can you help me? Got confused on the Makefile.. what values should I use?

include $(TOPDIR)/rules.mk

PKG_NAME:=mesh11sd
PKG_VERSION:=3.1.1
PKG_RELEASE:=1

PKG_MAINTAINER:=Rob White <rob@blue-wave.net>
PKG_LICENSE:=GPL-2.0-or-later
PKG_LICENSE_FILES:=LICENSE

PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://codeload.github.com/opennds/mesh11sd/tar.gz/v$(PKG_VERSION)?
PKG_HASH:=98f6c00a510dc102822a75916eb9fbbf97008e34f7226e8d555bc31c46fba187
PKG_BUILD_DIR:=$(BUILD_DIR)/mesh11sd-$(PKG_VERSION)

include $(INCLUDE_DIR)/package.mk

or if it would be faster, and IPK for aarch64_cortex-a53?

bluewavenet commented 2 months ago

@AcidSlide Here it is: (Edit: file deleted - replaced with new version - see below)

The documentation is not updated yet. The main difference is that auto_config is disabled by default.

I think if you install on top of v3.1.x it will keep and try to use the existing /etc/config/mesh11sd This will be ok but start in manual config mode. If you want auto_config do:

service mesh11sd stop
uci set mesh11sd.setup.auto_config='1'
uci commit mesh11sd
service mesh11sd start
AcidSlide commented 2 months ago

Here it is:

thanks.. i'll try it out in a couple of hours

AcidSlide commented 2 months ago

@bluewavenet initial test still borks my network when upstream is connected after a reboot/restart.. i'll re-test after a few hours and do more checking and testing

by the way below is my test setup

laptop (via LAN) -->> TEST ROUTER (via WAN) -->> (via LAN) Primary Network/Router (WAN) -->> ISP Modem

bluewavenet commented 2 months ago

What was the existing config?

Do you have mesh config in /etc/config/wireless ?

Please show the output of uci show wireless

and

uci show mesh11sd

If you have auto_config turned on AND have a wireless config containing mesh options then very likely you will "bork" your network.

bluewavenet commented 2 months ago

Note also that when mesh11sd is in auto_config mode, Luci will NOT show any signs of the mesh11sd config under wireless config and Luci cannot be used to configure mesh11sd mesh. This is because Luci is only concerned with static configurations, whereas mesh11sd is a dynamic configuration daemon. From v4.0.0 onwards, mesh11sd defaults to manual configuration and you have to enable it in the config. BUT as I mentioned earlier, if any existing mesh11sd config before installing 4.0.0 will remain active.

bluewavenet commented 2 months ago

@AcidSlide

laptop (via LAN) -->> TEST ROUTER (via WAN) -->> (via LAN) Primary Network/Router (WAN) -->> ISP Modem

Just to clarify:

  1. Your laptop is connected via ethernet to a lan port of your test router.
  2. Your test router routes, with nat, dhcp and dns, to a different subnet, from its wan port to your Primary router.
  3. Your test router is running mesh11sd.
  4. You do not yet have any mesh peer nodes.

Is this correct?

Is your laptop using dhcp to get an ipv4 address? If it does, or if it has a static ip address, then with mesh11sd v4.0.0 whether in auto or manual mode, the laptop will not loose its connection.

The previous 3.x.x version changed the mac address of br-lan to a locally administered address, so any connections would be lost until arp re-established the link. This happened regardless of auto or manual mode.

This is fixed in 4.0.0.

AcidSlide commented 2 months ago

Just to clarify:

  1. Your laptop is connected via ethernet to a lan port of your test router.

Yes and it's also connected to the main router via wifi. On my test, my primary connection is the wifi and the secondary is the LAN (to the TEST ROUTER). I mentioned this because my laptop gets disconnected to the primary router also when the TEST ROUTER is starting and also is connected to the PRIMARY router.

  1. Your test router routes, with nat, dhcp and dns, to a different subnet, from its wan port to your Primary router.

Yes, it has it's own DHCP and DNS and using different subnet from my primary router. Primary Router: 10.0.0.1/24 Test Router: 192.168.100.1/24

  1. Your test router is running mesh11sd.

Yes, it's running mesh11sd (installed the 4.0.0-beta)

  1. You do not yet have any mesh peer nodes.

Yes, no mesh peer nodes.

For the config, work week has started so I might take a while to do my test again. I'll update you when I can.

bluewavenet commented 2 months ago

@AcidSlide I have fixed a few things - one in particular where development/testing code was left in - probably borked your router ;-)

Here is the second beta: Edit - Sorry, 3rd beta ready...

bluewavenet commented 2 months ago

@AcidSlide 3rd beta: Edit: removed as next beta available

bluewavenet commented 2 months ago

@AcidSlide Beta 5 Edit: Removed as next beta available

AcidSlide commented 2 months ago

Beta 5

I will try to do test this weekend

bluewavenet commented 2 months ago

@AcidSlide There will probably be another beta by the weekend ;-)

bluewavenet commented 2 months ago

@AcidSlide Beta 6 Edit: Removed as yet another beta available.

bluewavenet commented 2 months ago

@AcidSlide Beta 7 Edit: Removed as beta 8 available

AcidSlide commented 1 month ago

@bluewavenet I have an extreme scenario and it's making me scratch my head

Ok still the same test setup

The issue happens right after mesh11sd starts. All the devices connected to the primary network suddenly can't see each other (tested via PING). Again this happens when all the conditions mentioned above is met.

I've tested with the laptop not connected to the primary network and this doesn't happen. Really really weird.

I have reproduced the issue multiple times.

And.. Test Router even if connected via WAN the DNSMasq I think gets disabled. I can ping internet IP (ex 8.8.8.8), but dns lookup doesn't work.

Anyway, I need to do more test. Due to busy scheds, I'm only able to do testing on the weekends 1-2hrs only.

bluewavenet commented 1 month ago

@AcidSlide Did you reflash the test router to your basic build? Who knows what residual stuff is left over from previous tests. For testing we need to start in a clean state. Make sure for the initial tests that no configuration has been done, not even enabling wifi ;-)

I will post the latest beta for you .....

bluewavenet commented 1 month ago

@AcidSlide Beta 8 mesh11sd.tar.gz

flipy commented 1 month ago

I am testing mesh11sd and found this same behaviour. Building my own from the openwrt 23.05 branch on a Linksys WHW03 (IPQ4019 -- armv7l). mesh11sd version is 3.1, kernel version is 5.15.155. Willing to try the new beta. Where can I get the source code to compile and test myself the latest beta?

bluewavenet commented 1 month ago

@flipy The current 4.0.0beta has been merged into master at https://github.com/openNDS/mesh11sd

It does not need to be compiled as it is all ash script, so the package "Beta 8" I posted above will work on any target. If installing, first opkg remove mesh11sd to get rid of any old version and also you have to delete the /etc/config/mesh11sd file. Previous configs may not be compatible.

You do not have to install kmod-nft-bridge unless you expect to have some ethernet segments in the mesh backhaul, but it will complain in the system log as it comes up if you don't.

This version defaults to "manual mode" ie auto_config is switched off. For testing I recommend a plain untouched basic flash image with even the wireless still disabled. Install the mesh11sd package 4.0.0beta. Then run:

service mesh11sd stop
uci set mesh11sd.setup.debuglevel='3'
uci set mesh11sd.setup.auto_config='1'
uci commit mesh11sd

Then do: service mesh11sd start; logread -f

and watch.

IMPORTANT 1: You must have an upstream connection on your mesh router wan port. IMPORTANT 2: Make sure the OpenWrt default ipv4 subnet (192.168.1.x) does not clash with the subnet of your upstream connection.

flipy commented 1 month ago

Installed mesh11sd 4.0-b8 on a test device. Device is a dummy clean openwrt installation with no internet (so no portal or gateway detected I assume). After starting mesh11sd I lost ethernet connectivity to the device when the following debug message was printed: Wed May 1 13:51:13 2024 daemon.debug mesh11sd[1637]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ]

Adding logging of the device after starting mesh11sd.

Details

```Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option enabled [ 1 ] Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option debuglevel [ 3 ] Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option checkinterval [ 10 ] Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option portal_detect [ 1 ] Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option portal_channel [ default ] Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option mesh_path_cost [ 10 ] Wed May 1 13:50:40 2024 daemon.info mesh11sd[3753]: option interface_timeout [ 10 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option auto_config [ 1 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: auto_mesh_id hash [ 92d490daf46cfe534c56ddd669297e ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option auto_mesh_band [ 2g40 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option auto_mesh_key [ 78c8068012f8481fec118451e1041b3751801a24ab3e222643a0a6a4424b82a1 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option auto_mesh_network [ lan ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option auto_mesh_network [ lan ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option mesh_basename [ m-11s- ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option mesh_gate_encryption [ 0 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option mesh_gate_key [ ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option mesh_gate_enable [ 1 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option mesh_gate_only [ 0 ] Wed May 1 13:50:41 2024 daemon.info mesh11sd[3753]: option ssid_suffix_enable [ 1 ] Wed May 1 13:50:41 2024 daemon.notice mesh11sd[3753]: mesh11sd is in startup Wed May 1 13:50:41 2024 daemon.debug mesh11sd[3753]: Kernel version: Major [ 5 ], Minor [ 15 ], Patch [ 155 ] Wed May 1 13:50:41 2024 daemon.info sh[3753]: 'radio0' is disabled Wed May 1 13:50:41 2024 daemon.info sh[3753]: 'radio1' is disabled Wed May 1 13:50:41 2024 daemon.info sh[3753]: 'radio2' is disabled Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'lan' is now down [ 194.072036] br-lan: port 1(lan) entered disabled state [ 194.081558] br-lan: port 1(lan) entered disabled state Wed May 1 13:50:41 2024 kern.info kernel: [ 194.072036] br-lan: port 1(lan) entered disabled state Wed May 1 13:50:41 2024 kern.info kernel: [ 194.075681] device lan left promiscuous mode Wed May 1 13:50:41 2024 kern.info kernel: [ 194.081558] br-lan: port 1(lan) entered disabled state [ 194.139175] qca8k-ipq4019 c000000.switch lan: Link is Down Wed May 1 13:50:41 2024 daemon.warn odhcpd[1279]: No default route present, overriding ra_lifetime![ 194.142146] device eth0 left promiscuous mode Wed May 1 13:50:41 2024 daemon.err odhcpd[1279]: Failed to send to ff02::1%lan@br-lan (Network unreachable) Wed May 1 13:50:41 2024 kern.info kernel: [ 194.139175] qca8k-ipq4019 c000000.switch lan: Link is Down Wed May 1 13:50:41 2024 kern.info kernel: [ 194.142146] device eth0 left promiscuous mode Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'lan' is disabled Wed May 1 13:50:41 2024 daemon.notice netifd: bridge 'br-lan' link is down Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'lan' has link connectivity loss Wed May 1 13:50:41 2024 daemon.notice netifd: Network device 'lan' link is down Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'loopback' is now down Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'loopback' is disabled Wed May 1 13:50:41 2024 daemon.notice netifd: Network device 'lo' link is down [ 194.303557] ipqess-edma c080000.ethernet eth0: Link is Downback' has link connectivity loss Wed May 1 13:50:41 2024 kern.info kernel: [ 194.303557] ipqess-edma c080000.ethernet eth0: Link is Down Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'wan' is disabled Wed May 1 13:50:41 2024 daemon.notice netifd: Interface 'wan6' is disabled Wed May 1 13:50:41 2024 daemon.notice netifd: Network device 'eth0' link is down Wed May 1 13:50:43 2024 user.notice : Added device handler type: bonding Wed May 1 13:50:43 2024 user.notice : Added device handler type: 8021ad Wed May 1 13:50:43 2024 user.notice : Added device handler type: 8021q Wed May 1 13:50:43 2024 user.notice : Added device handler type: macvlan Wed May 1 13:50:43 2024 user.notice : Added device handler type: veth Wed May 1 13:50:43 2024 user.notice : Added device handler type: bridge Wed May 1 13:50:43 2024 user.notice : Added device handler type: Network device Wed May 1 13:50:43 2024 user.notice : Added device handler type: tunnel Wed May 1 13:50:43 2024 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM [ 197.176351] ipqess-edma c080000.ethernet eth0: configuring for fixed/internal link mode [ 197.176635] ipqess-edma c080000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 197.181959] qca8k-ipq4019 c000000.switch lan: configuring for phy/psgmii link mode [ 197.193386] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 197.199824] br-lan: port 1(lan) entered blocking state [ 197.205334] br-lan: port 1(lan) entered disabled state [ 197.211125] device lan entered promiscuous mode [ 197.215650] device eth0 entered promiscuous mode Wed May 1 13:50:44 2024 kern.info kernel: [ 197.176351] ipqess-edma c080000.ethernet eth0: configuring for fixed/internal link mode Wed May 1 13:50:44 2024 kern.info kernel: [ 197.176635] ipqess-edma c080000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx Wed May 1 13:50:44 2024 kern.info kernel: [ 197.181959] qca8k-ipq4019 c000000.switch lan: configuring for phy/psgmii link mode Wed May 1 13:50:44 2024 kern.info kernel: [ 197.193386] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes read[ 197.237729] qca8k-ipq4019 c000000.switch wan: configuring for phy/psgmii link mode y Wed May 1 13:50:44 2024 kern.info kernel: [ 197.199824] br-lan: port 1(lan) entered blocking state Wed May 1 13:50:44 2024 kern.info kernel: [ 197.205334] br-lan: port 1(lan) entered disabled state Wed May 1 13:50:44 2024 kern.info kernel: [ 197.211125] device lan entered promiscuous mode Wed May 1 13:50:44 2024 kern.info kernel: [ 197.215650] device eth0 entered promiscuous mode Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'lan' is enabled Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'lan' is setting up now Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'lan' is now up Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'loopback' is enabled Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'loopback' is setting up now Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'loopback' is now up Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'wan' is enabled Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'wan6' is enabled Wed May 1 13:50:44 2024 daemon.notice netifd: Network device 'eth0' link is up Wed May 1 13:50:44 2024 kern.info kernel: [ 197.237729] qca8k-ipq4019 c000000.switch wan: configuring for phy/psgmii link mode Wed May 1 13:50:44 2024 daemon.notice netifd: Network device 'lo' link is up Wed May 1 13:50:44 2024 daemon.notice netifd: Interface 'loopback' has link connectivity Wed May 1 13:50:44 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan) [ 200.319379] qca8k-ipq4019 c000000.switch lan: Link is Up - 1Gbps/Full - flow control rx/tx [ 200.319475] br-lan: port 1(lan) entered blocking state [ 200.326567] br-lan: port 1(lan) entered forwarding state [ 200.331963] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready Wed May 1 13:50:47 2024 kern.info kernel: [ 200.319379] qca8k-ipq4019 c000000.switch lan: Link is Up - 1Gbps/Full - flow control rx/tx Wed May 1 13:50:47 2024 kern.info kernel: [ 200.319475] br-lan: port 1(lan) entered blocking state Wed May 1 13:50:47 2024 kern.info kernel: [ 200.326567] br-lan: port 1(lan) entered forwarding state Wed May 1 13:50:47 2024 kern.info kernel: [ 200.331963] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready Wed May 1 13:50:47 2024 daemon.notice netifd: Network device 'lan' link is up Wed May 1 13:50:47 2024 daemon.notice netifd: bridge 'br-lan' link is up Wed May 1 13:50:47 2024 daemon.notice netifd: Interface 'lan' has link connectivity Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: started, version 2.90 cachesize 1000 Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: DNS service limited to local subnets Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus Wed May 1 13:50:48 2024 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for test Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for onion Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for local Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for bind Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: using only locally-known addresses for lan Wed May 1 13:50:48 2024 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 names Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names Wed May 1 13:50:48 2024 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 0 names Wed May 1 13:50:48 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses Wed May 1 13:50:53 2024 daemon.info sh[3753]: 'radio0' is disabled Wed May 1 13:50:53 2024 daemon.info sh[3753]: 'radio1' is disabled Wed May 1 13:50:53 2024 daemon.info sh[3753]: 'radio2' is disabled Wed May 1 13:50:53 2024 daemon.debug mesh11sd[3753]: dsa_mesh_maclist [ 30:23:03:33:18:73 30:23:03:33:18:71 30:23:03:33:18:72 ] Wed May 1 13:50:53 2024 daemon.info mesh11sd[3753]: option mesh_fwding [ 1 ] Wed May 1 13:50:53 2024 daemon.info mesh11sd[3753]: option mesh_rssi_threshold [ -65 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_gate_announcements [ 1 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_hwmp_rootmode [ 4 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_hwmp_rann_interval [ 5000 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_hwmp_root_interval [ 5000 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_hwmp_active_path_timeout [ 5000 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_hwmp_active_path_to_root_timeout [ 6000 ] Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: option mesh_max_peer_links [ 16 ] Wed May 1 13:50:54 2024 daemon.notice mesh11sd[3753]: mesh11sd v4.0.0beta has started: mesh management mode 1 Wed May 1 13:50:54 2024 daemon.info mesh11sd[3753]: No mesh interfaces detected yet.... Attempting auto configure Wed May 1 13:50:54 2024 daemon.debug mesh11sd[3753]: Entering auto config.... Wed May 1 13:50:54 2024 daemon.warn mesh11sd[3753]: WARNING - country code not set - interoperability with other mesh nodes may be compromised or fail altogether.... Wed May 1 13:50:54 2024 daemon.warn mesh11sd[3753]: WARNING - country code defaulting to [ DFS-ETSI ].... Wed May 1 13:50:54 2024 daemon.warn mesh11sd[3753]: WARNING - country code not set - interoperability with other mesh nodes may be compromised or fail altogether.... Wed May 1 13:50:54 2024 daemon.warn mesh11sd[3753]: WARNING - country code defaulting to [ DFS-ETSI ].... Wed May 1 13:50:54 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=1... Wed May 1 13:50:54 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 1 ] .... Wed May 1 13:50:55 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 2 ] .... Wed May 1 13:50:56 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 3 ] .... Wed May 1 13:50:57 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 4 ] .... Wed May 1 13:50:58 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 5 ] .... Wed May 1 13:50:59 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 6 ] .... Wed May 1 13:51:00 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 7 ] .... Wed May 1 13:51:01 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 8 ] .... Wed May 1 13:51:02 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 9 ] .... Wed May 1 13:51:03 2024 daemon.debug mesh11sd[3753]: In Startup - portal upstream link check - iteration [ 10 ] .... Wed May 1 13:51:04 2024 daemon.warn odhcpd[1279]: No default route present, overriding ra_lifetime! Wed May 1 13:51:04 2024 daemon.debug mesh11sd[3753]: default_gw=.... Wed May 1 13:51:04 2024 daemon.debug mesh11sd[3753]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ] Wed May 1 13:51:10 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ br-lan ] server not found Wed May 1 13:51:10 2024 daemon.debug mesh11sd[3753]: leaving get_portal_state - is_portal=.. gwstatus=.. gw_ip=.. Wed May 1 13:51:11 2024 daemon.warn mesh11sd[3753]: WARNING - country code not set - interoperability with other mesh nodes may be compromised or fail altogether.... Wed May 1 13:51:11 2024 daemon.warn mesh11sd[3753]: WARNING - country code defaulting to [ DFS-ETSI ].... Wed May 1 13:51:11 2024 daemon.debug mesh11sd[3753]: auto config complete.... Wed May 1 13:51:11 2024 daemon.notice mesh11sd[3753]: Setting mac address of mesh interface m-11s-0 to [ 32:23:03:33:18:70 ] Wed May 1 13:51:11 2024 daemon.notice mesh11sd[3753]: Setting mac address of mesh interface m-11s-1 to [ 32:23:03:33:18:70 ] Wed May 1 13:51:11 2024 daemon.notice mesh11sd[3753]: Setting mac address of mesh interface m-11s-2 to [ 32:23:03:33:18:70 ] Wed May 1 13:51:11 2024 daemon.debug mesh11sd[3753]: Disconnecting nodes Wed May 1 13:51:12 2024 daemon.notice netifd: radio0 (5372): WARNING: Variable 'data' does not exist or is not an array/object Wed May 1 13:51:12 2024 daemon.notice netifd: radio2 (5374): WARNING: Variable 'data' does not exist or is not an array/object Wed May 1 13:51:12 2024 daemon.notice netifd: radio1 (5373): WARNING: Variable 'data' does not exist or is not an array/object Wed May 1 13:51:12 2024 daemon.debug mesh11sd[3753]: Entering check portal.... lan Wed May 1 13:51:12 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=0... Wed May 1 13:51:12 2024 daemon.notice hostapd: Set new config for phy phy0: Wed May 1 13:51:12 2024 daemon.notice hostapd: Set new config for phy phy2: Wed May 1 13:51:12 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy0 Wed May 1 13:51:12 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy2 Wed May 1 13:51:12 2024 daemon.notice hostapd: Set new config for phy phy1: Wed May 1 13:51:12 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy1 Wed May 1 13:51:12 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy0 Wed May 1 13:51:12 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy2 Wed May 1 13:51:13 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf Wed May 1 13:51:13 2024 daemon.notice hostapd: Restart interface for phy phy0 Wed May 1 13:51:13 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=GB ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 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=phy0-ap0 bssid=32:23:03:34:18:70 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 auth_algs=1 wpa=0 ssid=OpenWrt-5g- Wed May 1 13:51:13 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy1 [ 228.096559] ath10k_pci 0000:01:00.0: Unknown eventid: 36933 Wed May 1 13:51:15 2024 kern.warn kernel: [ 228.096559] ath10k_pci 0000:01:00.0: Unknown eventid: 3693[ 228.104051] br-lan: port 2(phy0-ap0) entered blocking state 3 [ 228.117146] device phy0-ap0 entered promiscuous mode Wed May 1 13:51:15 2024 daemon.warn hostapd: nl80211: Failed to add interface phy0-ap0 into bridge br-lan: Resource busy Wed May 1 13:51:15 2024 kern.info kernel: [ 228.104051] br-lan: port 2(phy0-ap0) entered blocking state Wed May 1 13:51:15 2024 kern.info kernel: [ 228.110054] br-lan: port 2(phy0-ap0) entered disabled state Wed May 1 13:51:15 2024 kern.info kernel: [ 228.117146] device phy0-ap0 entered promiscuous mode Wed May 1 13:51:15 2024 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE Wed May 1 13:51:15 2024 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->HT_SCAN Wed May 1 13:51:15 2024 daemon.notice hostapd: Set new config for phy phy2: /var/run/hostapd-phy2.conf Wed May 1 13:51:15 2024 daemon.notice hostapd: Restart interface for phy phy2 Wed May 1 13:51:15 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=GB ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=36 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=42 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-3][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=36 interface=phy2-ap0 bssid=32:23:03:36:18:70 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 auth_algs=1 wpa=0 ssid=OpenWrt-5g-187 [ 229.885931] br-lan: port 3(phy2-ap0) entered blocking state [ 229.885990] br-lan: port 3(phy2-ap0) entered disabled state [ 229.890736] device phy2-ap0 entered promiscuous mode Wed May 1 13:51:17 2024 kern.info kernel: [ 229.885931] br-lan: port 3(phy2-ap0) entered blocking state Wed May 1 13:51:17 2024 kern.info kernel: [ 229.885990] br-lan: port 3(phy2-ap0) entered disabled state Wed May 1 13:51:17 2024 kern.info kernel: [ 229.890736] device phy2-ap0 entered promiscuous mode Wed May 1 13:51:17 2024 daemon.notice hostapd: phy2-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE Wed May 1 13:51:17 2024 daemon.notice hostapd: phy2-ap0: interface state COUNTRY_UPDATE->HT_SCAN Wed May 1 13:51:17 2024 daemon.notice hostapd: Set new config for phy phy1: /var/run/hostapd-phy1.conf Wed May 1 13:51:17 2024 daemon.notice hostapd: Restart interface for phy phy1 Wed May 1 13:51:17 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=GB ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 chanlist=1 noscan=1 #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] channel=1 interface=phy1-ap0 bssid=32:23:03:35:18:70 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 auth_algs=1 wpa=0 ssid=OpenWrt-2g-1870 bridge=br-lan wds_bridge= snoop_iface=br-lan qos_map_set=0,0,2,16,1,1,255,255,18,22,24,38,40,40,44,46,48,56 nas_identifier=322303351870 (phy phy1) --> new PHY Wed May 1 13:51:18 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ wan ] server not found [ 231.648953] br-lan: port 4(phy1-ap0) entered blocking state [ 231.649013] br-lan: port 4(phy1-ap0) entered disabled state [ 231.653762] device phy1-ap0 entered promiscuous mode Wed May 1 13:51:19 2024 kern.info kernel: [ 231.648953] br-lan: port 4(phy1-ap0) entered blocking state Wed May 1 13:51:19 2024 kern.info kernel: [ 231.649013] br-lan: port 4(phy1-ap0) entered disabled state Wed May 1 13:51:19 2024 kern.info kernel: [ 231.653762] device phy1-ap0 entered promiscuous mode[ 231.661316] device phy1-ap0 left promiscuous mode Wed May 1 13:51:19 2024 daemon.debug mesh11sd[3753]: default_gw=.... Wed May 1 13:51:19 2024 daemon.notice hostapd: phy1-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE Wed May 1 13:51:19 2024 kern.info kernel: [ 231.661316] device phy1-ap0 left promiscuous mode Wed May 1 13:51:19 2024 kern.info kernel: [ 231.691223] br-lan: port 4(phy1-ap0) entered disabled state Wed May 1 13:51:19 2024 daemon.debug mesh11sd[3753]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ] [ 231.760478] br-lan: port 4(phy1-ap0) entered blocking state [ 231.760541] br-lan: port 4(phy1-ap0) entered disabled state [ 231.765220] device phy1-ap0 entered promiscuous mode Wed May 1 13:51:19 2024 kern.info kernel: [ 231.760478] br-lan: port 4(phy1-ap0) entered blocking state Wed May 1 13:51:19 2024 kern.info kernel: [ 231.760541] br-lan: port 4(phy1-ap0) entered disabled state Wed May 1 13:51:19 2024 kern.info kernel: [ 231.765220] device phy1-ap0 entered promiscuous mode [ 231.963668] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready [ 231.963955] br-lan: port 4(phy1-ap0) entered blocking state [ 231.969182] br-lan: port 4(phy1-ap0) entered forwarding state Wed May 1 13:51:19 2024 kern.info kernel: [ 231.963668] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready Wed May 1 13:51:19 2024 kern.info kernel: [ 231.963955] br-lan: port 4(phy1-ap0) entered blocking state Wed May 1 13:51:19 2024 kern.info kernel: [ 231.969182] br-lan: port 4(phy1-ap0) entered forwarding state Wed May 1 13:51:19 2024 daemon.notice netifd: Network device 'phy1-ap0' link is up Wed May 1 13:51:19 2024 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->ENABLED Wed May 1 13:51:19 2024 daemon.notice hostapd: phy1-ap0: AP-ENABLED [ 232.043087] br-lan: port 5(m-11s-1) entered blocking state [ 232.043162] br-lan: port 5(m-11s-1) entered disabled state [ 232.048136] device m-11s-1 entered promiscuous mode [ 232.053374] br-lan: port 5(m-11s-1) entered blocking state [ 232.057785] br-lan: port 5(m-11s-1) entered forwarding state Wed May 1 13:51:19 2024 kern.info kernel: [ 232.043087] br-lan: port 5(m-11s-1) entered blocking state Wed May 1 13:51:19 2024 kern.info kernel: [ 232.043162] br-lan: port 5(m-11s-1) entered disabled state Wed May 1 13:51:19 2024 kern.info kernel: [ 232.048136] device m-11s-1 entered promiscuous mode Wed May 1 13:51:19 2024 kern.info kernel: [ 232.053374] br-lan: port 5(m-11s-1) entered blocking state [ 232.071382] br-lan: port 5(m-11s-1) entered disabled statelan: port 5(m-11s-1) entered forwarding state Wed May 1 13:51:19 2024 kern.info kernel: [ 232.071382] br-lan: port 5(m-11s-1) entered disabled state Wed May 1 13:51:19 2024 daemon.notice hostapd: phy0-ap0: interface state HT_SCAN->DFS Wed May 1 13:51:19 2024 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5500 chan=100 sec_chan=1, width=1, seg0=106, seg1=0, cac_time=60s Wed May 1 13:51:19 2024 daemon.notice netifd: Wireless device 'radio2' is now up Wed May 1 13:51:19 2024 daemon.notice netifd: Wireless device 'radio0' is now up Wed May 1 13:51:19 2024 daemon.notice wpa_supplicant[1074]: Set new config for phy phy1 Wed May 1 13:51:19 2024 daemon.notice netifd: Wireless device 'radio1' is now up [ 232.542847] IPv6: ADDRCONF(NETDEV_CHANGE): phy2-ap0: link becomes ready [ 232.543134] br-lan: port 3(phy2-ap0) entered blocking state [ 232.548340] br-lan: port 3(phy2-ap0) entered forwarding state Wed May 1 13:51:19 2024 kern.info kernel: [ 232.542847] IPv6: ADDRCONF(NETDEV_CHANGE): phy2-ap0: link becomes ready Wed May 1 13:51:19 2024 kern.info kernel: [ 232.543134] br-lan: port 3(phy2-ap0) entered blocking state Wed May 1 13:51:19 2024 kern.info kernel: [ 232.548340] br-lan: port 3(phy2-ap0) entered forwarding state Wed May 1 13:51:19 2024 daemon.notice netifd: Network device 'phy2-ap0' link is up Wed May 1 13:51:19 2024 daemon.notice hostapd: phy2-ap0: interface state HT_SCAN->ENABLED Wed May 1 13:51:19 2024 daemon.notice hostapd: phy2-ap0: AP-ENABLED [ 232.648910] br-lan: port 4(phy1-ap0) entered disabled state Wed May 1 13:51:20 2024 daemon.notice netifd: Network device 'phy1-ap0' link is down Wed May 1 13:51:20 2024 kern.info kernel: [ 232.648910] br-lan: port 4(phy1-ap0) entered disabled state Wed May 1 13:51:20 2024 daemon.warn odhcpd[1279]: No default route present, overriding ra_lifetime! Wed May 1 13:51:20 2024 daemon.notice wpa_supplicant[1074]: m-11s-1: interface state UNINITIALIZED->ENABLED Wed May 1 13:51:20 2024 daemon.notice wpa_supplicant[1074]: m-11s-1: AP-ENABLED Wed May 1 13:51:20 2024 daemon.notice wpa_supplicant[1074]: m-11s-1: joining mesh 92d490daf46cfe534c56ddd669297e Wed May 1 13:51:20 2024 daemon.notice wpa_supplicant[1074]: m-11s-1: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=[ 233.469729] br-lan: port 4(phy1-ap0) entered blocking state ] Wed May 1 13:51:20 2024 daemon.notice netifd: Network device 'm-11s-1' link is u[ 233.482137] IPv6: ADDRCONF(NETDEV_CHANGE): m-11s-1: link becomes ready p Wed May 1 13:51:20 2024 kern.info kernel: [ 233.469729] br-lan: port 4(phy1-ap0) entered blocking state Wed May 1 13:51:20 2024 kern.info kernel: [ 233.472359] br-lan: port 4(phy1-ap0) entered forwarding state Wed May 1 13:51:20 2024 daemon.notice netifd: Network device 'phy1-ap0' link is up [ 233.493099] br-lan: port 5(m-11s-1) entered forwarding state11s-1: MESH-GROUP-STARTED ssid="92d490daf46cfe534c56ddd669297e" id=0 Wed May 1 13:51:20 2024 kern.info kernel: [ 233.482137] IPv6: ADDRCONF(NETDEV_CHANGE): m-11s-1: link becomes ready Wed May 1 13:51:20 2024 kern.info kernel: [ 233.485496] br-lan: port 5(m-11s-1) entered blocking state Wed May 1 13:51:20 2024 kern.info kernel: [ 233.493099] br-lan: port 5(m-11s-1) entered forwarding state Wed May 1 13:51:25 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ br-lan ] server not found Wed May 1 13:51:25 2024 daemon.debug mesh11sd[3753]: leaving get_portal_state - is_portal=.. gwstatus=.. gw_ip=.. Wed May 1 13:51:25 2024 daemon.debug mesh11sd[3753]: This meshnode is NOT a portal Wed May 1 13:51:34 2024 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM Wed May 1 13:51:35 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 1 ] .... Wed May 1 13:51:36 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 2 ] .... Wed May 1 13:51:37 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 3 ] .... Wed May 1 13:51:38 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 4 ] .... Wed May 1 13:51:39 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 5 ] .... Wed May 1 13:51:40 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 6 ] .... Wed May 1 13:51:41 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 7 ] .... Wed May 1 13:51:42 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 8 ] .... Wed May 1 13:51:43 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 9 ] .... Wed May 1 13:51:44 2024 daemon.debug mesh11sd[3753]: Waiting for ipv4 default gateway - iteration [ 10 ] .... Wed May 1 13:51:46 2024 daemon.debug mesh11sd[3753]: checking for working channel.... Wed May 1 13:51:46 2024 daemon.debug mesh11sd[3753]: Leaving check portal.... Wed May 1 13:51:47 2024 daemon.debug mesh11sd[3753]: checkinterval 10 seconds Wed May 1 13:51:58 2024 daemon.debug mesh11sd[3753]: interface m-11s-1 is up Wed May 1 13:51:58 2024 daemon.info mesh11sd[3753]: Old value:mesh_max_peer_links=99, Setting new value:mesh_max_peer_links=16 Wed May 1 13:51:58 2024 daemon.info mesh11sd[3753]: Old value:mesh_hwmp_rootmode=0, Setting new value:mesh_hwmp_rootmode=2 Wed May 1 13:51:58 2024 daemon.info mesh11sd[3753]: Old value:mesh_gate_announcements=0, Setting new value:mesh_gate_announcements=1 Wed May 1 13:51:58 2024 daemon.info mesh11sd[3753]: Old value:mesh_connected_to_gate=0, Setting new value:mesh_connected_to_gate=1 Wed May 1 13:51:58 2024 daemon.debug mesh11sd[3753]: node [DEST,ADDR] Wed May 1 13:51:58 2024 daemon.debug mesh11sd[3753]: Entering check portal.... lan Wed May 1 13:51:58 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=0... Wed May 1 13:52:04 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ wan ] server not found Wed May 1 13:52:05 2024 daemon.debug mesh11sd[3753]: default_gw=.... Wed May 1 13:52:05 2024 daemon.debug mesh11sd[3753]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ] Wed May 1 13:52:11 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ br-lan ] server not found Wed May 1 13:52:11 2024 daemon.debug mesh11sd[3753]: leaving get_portal_state - is_portal=.. gwstatus=.. gw_ip=.. Wed May 1 13:52:11 2024 daemon.debug mesh11sd[3753]: checking for working channel.... Wed May 1 13:52:11 2024 daemon.notice odhcp6c[6912]: (re)starting transaction on br-lan Wed May 1 13:52:11 2024 daemon.notice odhcp6c[6912]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Wed May 1 13:52:15 2024 daemon.debug mesh11sd[3753]: portal not detected Wed May 1 13:52:15 2024 daemon.debug mesh11sd[3753]: Entering scan channel.... Wed May 1 13:52:17 2024 daemon.notice odhcp6c[6981]: (re)starting transaction on br-lan Wed May 1 13:52:17 2024 daemon.notice odhcp6c[6981]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Wed May 1 13:52:21 2024 daemon.debug mesh11sd[3753]: portal not detected Wed May 1 13:52:21 2024 daemon.debug mesh11sd[3753]: Entering scan channel.... Wed May 1 13:52:22 2024 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5500 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0 [ 294.882135] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready [ 294.900359] br-lan: port 2(phy0-ap0) entered listening state Wed May 1 13:52:22 2024 kern.info kernel: [ 294.882135] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready Wed May 1 13:52:22 2024 kern.info kernel: [ 294.892791] br-lan: port 2(phy0-ap0) entered blocking state Wed May 1 13:52:22 2024 kern.info kernel: [ 294.900359] br-lan: port 2(phy0-ap0) entered listening state Wed May 1 13:52:22 2024 daemon.notice netifd: Network device 'phy0-ap0' link is up Wed May 1 13:52:22 2024 daemon.notice hostapd: phy0-ap0: interface state DFS->ENABLED Wed May 1 13:52:22 2024 daemon.notice hostapd: phy0-ap0: AP-ENABLED Wed May 1 13:52:22 2024 daemon.notice hostapd: phy2-ap0: DFS-CAC-COMPLETED success=1 freq=5500 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0 Wed May 1 13:52:22 2024 daemon.notice odhcp6c[7050]: (re)starting transaction on br-lan Wed May 1 13:52:23 2024 daemon.notice odhcp6c[7050]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Wed May 1 13:52:26 2024 daemon.debug mesh11sd[3753]: portal not detected Wed May 1 13:52:26 2024 daemon.debug mesh11sd[3753]: Entering scan channel.... Wed May 1 13:52:28 2024 daemon.debug mesh11sd[3753]: Leaving check portal.... Wed May 1 13:52:29 2024 daemon.debug mesh11sd[3753]: checkinterval 10 seconds [ 303.198253] br-lan: port 2(phy0-ap0) entered learning state Wed May 1 13:52:30 2024 kern.info kernel: [ 303.198253] br-lan: port 2(phy0-ap0) entered learning state [ 311.518238] br-lan: port 2(phy0-ap0) entered forwarding state [ 311.518312] br-lan: topology change detected, propagating Wed May 1 13:52:38 2024 kern.info kernel: [ 311.518238] br-lan: port 2(phy0-ap0) entered forwarding state Wed May 1 13:52:38 2024 kern.info kernel: [ 311.518312] br-lan: topology change detected, propagating Wed May 1 13:52:39 2024 daemon.debug mesh11sd[3753]: interface m-11s-1 is up Wed May 1 13:52:40 2024 daemon.debug mesh11sd[3753]: node [DEST,ADDR] Wed May 1 13:52:40 2024 daemon.debug mesh11sd[3753]: Entering check portal.... lan Wed May 1 13:52:40 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=0... Wed May 1 13:52:46 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ wan ] server not found Wed May 1 13:52:46 2024 daemon.debug mesh11sd[3753]: default_gw=.... Wed May 1 13:52:46 2024 daemon.debug mesh11sd[3753]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ] Wed May 1 13:52:52 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ br-lan ] server not found Wed May 1 13:52:52 2024 daemon.debug mesh11sd[3753]: leaving get_portal_state - is_portal=.. gwstatus=.. gw_ip=.. Wed May 1 13:52:52 2024 daemon.debug mesh11sd[3753]: checking for working channel.... Wed May 1 13:52:52 2024 daemon.debug mesh11sd[3753]: Leaving check portal.... Wed May 1 13:52:53 2024 daemon.debug mesh11sd[3753]: checkinterval 10 seconds Wed May 1 13:53:03 2024 daemon.debug mesh11sd[3753]: interface m-11s-1 is up Wed May 1 13:53:04 2024 daemon.debug mesh11sd[3753]: node [DEST,ADDR] Wed May 1 13:53:04 2024 daemon.debug mesh11sd[3753]: Entering check portal.... lan Wed May 1 13:53:04 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=0... Wed May 1 13:53:10 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ wan ] server not found Wed May 1 13:53:10 2024 daemon.debug mesh11sd[3753]: default_gw=.... Wed May 1 13:53:10 2024 daemon.debug mesh11sd[3753]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ] Wed May 1 13:53:16 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ br-lan ] server not found Wed May 1 13:53:16 2024 daemon.debug mesh11sd[3753]: leaving get_portal_state - is_portal=.. gwstatus=.. gw_ip=.. Wed May 1 13:53:16 2024 daemon.debug mesh11sd[3753]: checking for working channel.... Wed May 1 13:53:17 2024 daemon.notice odhcp6c[8294]: (re)starting transaction on br-lan Wed May 1 13:53:17 2024 daemon.notice odhcp6c[8294]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Wed May 1 13:53:21 2024 daemon.debug mesh11sd[3753]: portal not detected Wed May 1 13:53:21 2024 daemon.debug mesh11sd[3753]: Entering scan channel.... Wed May 1 13:53:22 2024 daemon.notice odhcp6c[8363]: (re)starting transaction on br-lan Wed May 1 13:53:22 2024 daemon.notice odhcp6c[8363]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Wed May 1 13:53:26 2024 daemon.debug mesh11sd[3753]: portal not detected Wed May 1 13:53:26 2024 daemon.debug mesh11sd[3753]: Entering scan channel.... Wed May 1 13:53:28 2024 daemon.notice odhcp6c[8432]: (re)starting transaction on br-lan Wed May 1 13:53:28 2024 daemon.notice odhcp6c[8432]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Wed May 1 13:53:32 2024 daemon.debug mesh11sd[3753]: portal not detected Wed May 1 13:53:32 2024 daemon.debug mesh11sd[3753]: Entering scan channel.... Wed May 1 13:53:34 2024 daemon.debug mesh11sd[3753]: Leaving check portal.... Wed May 1 13:53:35 2024 daemon.debug mesh11sd[3753]: checkinterval 10 seconds Wed May 1 13:53:45 2024 daemon.debug mesh11sd[3753]: interface m-11s-1 is up Wed May 1 13:53:46 2024 daemon.debug mesh11sd[3753]: node [DEST,ADDR] Wed May 1 13:53:46 2024 daemon.debug mesh11sd[3753]: Entering check portal.... lan Wed May 1 13:53:46 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=0... Wed May 1 13:53:52 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ wan ] server not found Wed May 1 13:53:52 2024 daemon.debug mesh11sd[3753]: default_gw=.... Wed May 1 13:53:52 2024 daemon.debug mesh11sd[3753]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ] Wed May 1 13:53:58 2024 daemon.debug mesh11sd[3753]: Killing dhcp client-renew as it failed on [ br-lan ] server not found Wed May 1 13:53:58 2024 daemon.debug mesh11sd[3753]: leaving get_portal_state - is_portal=.. gwstatus=.. gw_ip=.. Wed May 1 13:53:58 2024 daemon.debug mesh11sd[3753]: checking for working channel.... Wed May 1 13:53:58 2024 daemon.debug mesh11sd[3753]: Leaving check portal.... Wed May 1 13:53:59 2024 daemon.debug mesh11sd[3753]: checkinterval 10 seconds Wed May 1 13:54:09 2024 daemon.debug mesh11sd[3753]: interface m-11s-1 is up Wed May 1 13:54:10 2024 daemon.debug mesh11sd[3753]: node [DEST,ADDR] Wed May 1 13:54:10 2024 daemon.debug mesh11sd[3753]: Entering check portal.... lan Wed May 1 13:54:10 2024 daemon.debug mesh11sd[3753]: In get_portal_state. firstloop=0... ```

bluewavenet commented 1 month ago

@flipy

with no internet (so no portal or gateway detected

After starting mesh11sd I lost ethernet connectivity to the device

So mesh11sd is working as expected in auto_config mode. As there is no uplink, auto_config will "configure" as a peer node. A peer node is equivalent to a "dumb ap" with a mesh backhaul connection and dhcp client enabled to get an ip address. So if your connection was by ipv4 (to 192.168.1.1 most likely) then your connection will indeed be lost.

Wed May  1 13:51:13 2024 daemon.debug mesh11sd[1637]: ipV4 link to portal fail, attempting to (re)establish via device [ br-lan ]

The phrase ipV4 link to portal fail tells all ;-)

You can set portal_detect to force portal mode by setting it to zero:

service mesh11sd stop
uci set mesh11sd.setup.portal_detect='0'
uci commit mesh11sd
service mesh11sd start
bluewavenet commented 1 month ago

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

AcidSlide commented 1 month ago

FYI: Version 4.0.0 is released

Thanks for the update.. on the openwrt feed it still says 3.1.1 hehehe

bluewavenet commented 1 month ago

@AcidSlide

Thanks for the update.. on the openwrt feed it still says 3.1.1

It will until I submit a PR there ;-)

AcidSlide commented 1 month ago

I'm currently disabling mesh11sd as it really is wrecking havoc on my setup.. older version was simpler to setup but not working on latest kernel 6.6.x

Question: Should the main node/primary also converts to a mesh even though it has an upstream (wan) connection?

bluewavenet commented 1 month ago

@AcidSlide

I'm currently disabling mesh11sd as it really is wrecking havoc on my setup..

Have you tried v4.0.1? https://github.com/openNDS/mesh11sd/releases/download/v4.0.1/mesh11sd_4.0.1-1_all.ipk

Should the main node/primary also converts to a mesh even though it has an upstream (wan) connection?

I don't understand what you mean by that.

A node connected to an upstream wan should always be a portal node.

By default, v4.0.1 starts with auto_config disabled ie manual mode, and if you leave it disabled, you must do all the mesh configuration yourself.

If you turn on auto_config, mesh11sd will "auto config".... ie if there is no mesh config it will create one and "portal detect", meaning it will either be a portal node if wan is connected on the node, or a peer if wan is not detected.

In auto_config mode, if a mesh config is pre-existing, mesh11sd will attempt to use it but this could conflict with what you wanted to achieve with that pre-existing mesh config.

What exactly do you mean by "wrecking havoc"?

AcidSlide commented 1 month ago

Have you tried v4.0.1?

Yup, that's what I tried on my meshed network.

If you turn on auto_config, mesh11sd will "auto config".... ie if there is no mesh config it will create one and "portal detect", meaning it will either be a portal node if wan is connected on the node, or a peer if wan is not detected.

I've tried both manual and auto config. And both leads to problematic network on my setup. The main node is acting is the internet gateway. Setup is similar to my test network. It's connected to my upstream router and somehow even other devices connected to the same upstream router gets disconnected to that network.

ISP Modem <-- LAN to WAN --> Primary Router (not meshed, acting as primary firewall and main gateway to the rest of my downstream network)

Now from my Primary Router I have other computers and devices connected here directly. And this also acting as the upstream internet for the rest of my network which is the one that is using mesh.

Primary Router <-- LAN to WAN --> Primary Node (acting as a gateway also, this is also acting as the local network for the rest of my home network)

I've got 3 other routers acting as mesh nodes connected to the Primary Node via Wifi. And they are having issues connecting to the Primary Node from time to time. Seeing repeating logs and warnings for kmod-nft-bridge on the mesh nodes.

Just booting the Primary Node (and if mesh11sd is enabled), somehow also affects all the other devices connected on the Primary Router. It seems the routing gets borked on the primary node and devices there can't see each other for a couple of mins.

I'm really at a lost here. But I think it's somehow related on how my network is configured and interconnected. So for now, until I have really a free (very long) time to assess what is happening and get correct configurations for mesh11sd to work, I'm disabling it for now. Basic mesh config of openwrt works anyway.

Anyway, thanks for the latest update.

bluewavenet commented 1 month ago

@AcidSlide

Seeing repeating logs and warnings for kmod-nft-bridge on the mesh nodes.

In some of the beta versions you tried, if you had a bridge name beginning with a numeric character this would happen. It was fixed.

Did you install 4.0.1 on all the nodes?

Primary Router <-- LAN to WAN --> Primary Node (acting as a gateway also, this is also acting as the local network for the rest of my home network)

Whatever is upstream is irrelevant. Your "Primary Node", properly known as the "Portal Node" should be the router for the home network. Do you have it configured as a bridge? If so then that is the only way I can think of how it can effect the primary router. You would have to force it into "peer mode" (portal_detect='2') and connect using a lan port, or have auto_config='0' and do all the config yourself.