Recent content by Zardoz

Anybody wondering how to get a text representation of the configuration? It's very easy to do if you can access the console of the router via SSH Etc. Just use the "nvram show" command.

Seems to be working here as well, in a AIMesh environment with AX86U as the master, and AX86S and AC86U as mesh nodes.

I'm still having issues when using an AC86U as a mesh node, with this firmware. From time to time, it seems to stop passing traffic, although the node remains online itself. I suspect this will never get fixed. I don't see the same sort of issues on my AX86U or AX86S SYSTEMS. Apart from that...

I'm not sure why it was still working in that case in my previous firmware version. That was, as far as I'm aware, only one revision earlier than this one. I have managed to get some of the functionality working using the post that you linked to but there is a timing issue which is causing me...

It's been working fine for me until this very last update, although I needed to make a minor change or two to the code, to fix that problem. I've done some more investigation and it seems that the code which used to invoke the command in the nvram variable "script_usbmount" just isn't running...

This update would appear to have broken Entware. As far as I can tell upon initial investigation it is no longer performing the function defined in the nvram variable "script_usbmount". It was working perfectly across reboots before I did the firmware update but now the mount that I was...

Given the history of updates for this device and the problems that they have caused, I am going to wait and see how people get on before updating. They managed to break AIMesh in the previous update to the one that I am currently running. I would not be totally surprised if they've done it again.

Seems that the AiMesh is working fine in the version.

-16°C here in Kitchener...

Just updated my AX86S AiMesh Node. No initial problems but I I'll keep an eye out for anything unusual.

The -GXXXXXXX value is the Github version number, and can be ignored by the end user. For software support, it identifies exactly which internal version is deployed.

Unfortunately, I have made significant changes to the main router configuration, including adding entware to it. While I absolutely agree that the RT-AX86S should be the master, it's a lot of effort to reconfigure the network. I'll do this when the RT-AC86U inevitably fails with the same...

It would appear that my questions/concerns were justified. https://www.snbforums.com/threads/rt-ac86u-aimesh-3-0-0-4-386_48260.81864/

I have a network consisting of a pair of RT-AC86U units. One is an AiMesh Router and the other is an AiMesh Node, connected by a 5GHz backhaul. They were both running on 3.0.0.4.386_46092. On Friday, the RT-AC86U AiMesh Node failed with the known issue of the step-down chip dying. I therefore...

Ah... The issue was reported using a wireless backhaul. I guess Ethernet was not impacted.