Open lynxthecat opened 2 years ago
It seems that one of the extension nodes (i.e. nodes which connect to my main router acting as gateway) becomes inaccessible following a period of inactivity. Could this therefore be some kind of power saving or something?
I checked and whilst a node is inaccessible its AP SSID and mesh hidden SSID still show up on a WiFi analyzer.
The 'tx bytes' from a good node relating to the first inaccessible node shows very slow increase - does this help?
root@OpenWrt:~# iw dev wlan1 station dump |grep -i bytes
rx bytes: 24222245
tx bytes: 147301
rx bytes: 626904121
tx bytes: 372754833
root@OpenWrt:~# iw dev wlan1 station dump |grep -i bytes
rx bytes: 24224452
tx bytes: 147301
rx bytes: 626906328
tx bytes: 372754833
root@OpenWrt:~# iw dev wlan1 station dump |grep -i bytes
rx bytes: 24225989
tx bytes: 147301
rx bytes: 626908137
tx bytes: 372754919
root@OpenWrt:~# iw dev wlan1 station dump |grep -i bytes
rx bytes: 24372908
tx bytes: 147479
rx bytes: 627143495
tx bytes: 372823476
root@OpenWrt:~# iw dev wlan1 station dump |grep -i bytes
rx bytes: 24379516
tx bytes: 147538
rx bytes: 627150666
tx bytes: 372823844
Hello, Looks like the related patch was published for the mainline kernel.
The patch addresses the crash trace? That was always there, even when the mesh functionality worked well. But what is new is that nodes on the mesh become inaccessible. I presume that is not something that has been addressed by the patch? Or perhaps it might address both?
There was another patch that should improve mesh mode stability (allowing auth frames in blocked state). Please test the latest version
Presumably the recent mt76 feature updates are responsible for the reports surfacing of mesh having been broken in recent snapshots.
To elaborate, I have x3 RT3200's setup in an 802.11s mesh. For months it has been 100% stable, but now recently either one of my two extension nodes becomes inaccessible even though the other stations list the inaccessible node as still connected. Rebooting my main router restores connectivity, but then eventually one of the two extensions nodes will again become inaccessible. By inaccessible I mean I cannot access the web interface or ping the affected node.
I believe this issue has surfaced as a result of a change reflected in a fairly recent snapshot.
The receive and send packets seem to increase during the period of inaccessibility (which I don't understand)? See the first station (presently inaccessible) rx/tx packets increase:
Dmesg output: