For a quick update, going on 12 days full stability on the BE88U after addressing the autowan restarts. Not sure why the attempted restarts continue to occur, though they are ignored at the moment and not causing any issues.
The only issue I have seen at all is related to instability with my...
Not sure if this is just me or if others see the same, however the wanduck/rc check keeps running and tries restarting autowan, even though everything shows connected and that it shouldn't need to:
Nov 26 16:10:47 RT-BE88U svc_event: ARGS: restart autowan | PPID=1 | PARENT=
Nov 26 16:10:47...
I’ve been troubleshooting frequent dnsmasq restarts and traced them back to autowan attempting to restart, which cascades into restart firewall and restart dnsmasq. Under default behavior, these restart attempts were doubling and flooding logs.
Even after disabling wandog and confirming WAN...
Still stable, though seeing something that I was seeing on the betas as well. My messages log growth is higher than expected due to dnsmasq restarts. I put a monitoring script to check this and see 80 restarts with no apparent trigger since the router came back up following the update. The...
Installed on the BE86U AiMesh node first and everything came up fine, then just completed the BE88U router and things look good so far. 9 minutes of uptime and counting :).
Not sure if related or arbitrary, however with my BE86U AiMesh node running beta 2, one of my IoT networks stopped functioning. All other networks worked fine and I only had to restart wireless from SSH on the node to restore connectivity.
Digging through the logs with some Copilot help, since...
I'll have to parse the large log file that I save before clearing as since restarting with this update to the dnsmasq.postconf, I have only had 5 dnsmasq restarts in several hours, which were all at the start and likely just related to start behavior.
I have been using Unbound for years with dnsmasq disabled (so it acts as a recursive DNS server for clients on my network) with Adblock handled by Unbound. This has been great, though since upgrading to Pro/BE series routers (BE88U/BE86U/BE82U), I have been fighting some client instability and...
I see them as well as of this morning, which was a fun goose egg when working on finding out why dnsmasq restarted over 60K times overnight o_O and has been a persistent issue causing my messages log to grow to several hundred MB and the router to go haywire. It would be very helpful to have...
One observation I had is that my System Message log was growing absurdly fast, with logrotate not even able to keep up. I found that the primary culprit was kernel messages relating to Smart Connect and Roaming Assist and client connections and disconnections. This to the tune of millions of...
I had several IoT devices with stable connection issues. The one setting change with the biggest effect was disabling 11b support in Wireless \ Professional. If you are able to, and most people should be unless you have extremely old devices, I would try disabling 11b and see if connection...
I added spdMerlin and hostapd, along with corresponding log rotate items and see them functioning as expected:
Nov 20 10:52:41 RT-BE88U logrotate: logrotate state -- version 2
Nov 20 10:52:41 RT-BE88U logrotate: "/opt/var/log/wlceventd.log" 2025-11-16-0:5:0
Nov 20 10:52:41 RT-BE88U logrotate...
While I know it does log rotate by default, I believe, per the readme, that you have to give the guidance for which logs should be rotated.
Some of the files in this directory may be copied to /opt/etc/syslog-ng.d/
to filter common messages from the default messages file to their own
log files...
Beta 2 updated on my BE86U Mesh node and running for 9 hours with no issues. After about ~15 minutes post update, Smart Connect and Roaming Assistant moved clients to the updated mesh node automatically and as of this morning it is perfectly balanced across nodes as expected.
All of this sounds excellent!
Following your feedback earlier, I read the information and examples of Scribe, which I will look into setting up something for hostapd logs similar to what you helped with for DomainVPNRouting. One thing I noticed is the potential need and separate steps required...