Recent content by roboots21

This command has worked for me: /usr/sbin/ntp -t -S /sbin/ntpd_synced -p pool.ntp.org .. but now that I compare, it doesn't seem to be working for you. That being said, this NEVER happened to me until 386.2 beta 1 on my main router RT-AX88U, and then on the beta 2 update, it happened on both...

I'm glad I wasn't the only one seeing this behavior. Mine was happening every 12 hours to the minute, and ONLY when connected via wireless backhaul. Not seen over Ethernet backhaul.

This was one of the things I wanted to do with scribe, so thank you for that! Also, I can't quite figure out how to set the logging level properly and where with the level() function. Any thoughts on where I'd insert that function call to only log specific levels (I know the function arguments...

It has worked for me on the 386 releases. Never saw it work prior to that either.

I was able to get this working using your method, albeit manual terminal commands. What is the best way to enable custom scripts on the node? Only way I know of is to use nvram variables to enable remote access via the GUI, but I don't want to change anything while in there risking messing...

Ended up being the wireles backhaul to my second node (that really wasn't needed). Removed the node, strictly wired backhaul to my other node (and switched to ethernet backhaul in the GUI). No more random unregistrations.

Replying to myself .. I had a second node (AX58U) in wireless backhaul. Something with this device was causing my deregistrations as once I removed the node (as it really wasn't needed), all issues and logs went away.

I'm seeing the same logging messages on my AX88U in exactly 12 hour intervals. I rebooted this morning at 0704 and I watched the syslog at 1904 to see both my 2.4G band and 5G band unregister/register themselves on the main router. This drops the connection to the wireless node for a split...

So did you reset prior to upgrading the firmware? The proper method to ensure no residuals from previous firmware versions is to reset the router AFTER you flash the updated firmware to ensure the cleanest baseline.

Hmmm .. I have been interested in seeing the logs on my AiMesh nodes and this may just be the ticket. That being said, this would be a great addition to the scribe!

Let me rephrase my initial request lol .. I was hoping to better understand what the subject log entries were. I have no hair to waste, so that valuable resource has been fully depleted. :D

I did a search prior, yes. One thing that may have behooved my search was I specified the AX88U in the search which likely narrowed my results. I don't think my 'issue' is the same, as my router doesn't crash and I see no real oddball behavior other than those noted occurrences in the log file...

Folks, I'm seeing some weirdness in my system log file of my main router (AX88U) that impacts the wireless backhaul to one of my AiMesh nodes (one is wireless - second floor, other is wired - first floor other side of house) as well as some of my other devices that drop connection, but some...

Before you roll back, perhaps a reset is in order. If you're having unexplained issues (which this sounds like), a full reset will likely remedy.

I'm not sure. That's a question the dev will have to answer.