Recent content by gk802

Note that it is possible to retain system logs indefinitely. I run a script every 3 hours that copies both /tmp/syslog.log and /tmp/syslog.log-1 to the USB. Before copying, it first checks the timestamp on the -1 log vs the last saved copy. If the timestamp is changed, it archives the saved...

Perfect! Thank you!

Point of clarification... is the format of the saved Traffic Monitor history file (.gz file) changing or just the display generated from the data? I currently read daily totals from the history file with a script...just assessing whether I've got a re-write forthcoming.

Agree. I do the nvram backup as well at the same time. Didn't include that part here. It's part of a script that runs every 3 hours to take care of that, copy system logs and do several other housekeeping things.

I've had a few instances in the past where a brief power blip has resulted in a complete loss of everything in /jffs. In no case did it brick the router, but it did take a while to figure out what was lost and how to restore it. As a result of that, I run a script that does a backup of /jffs...

I've been seeing something very similar...basically a "mass reconnection event" that occurs a few times a day. Looking back in the logs, for me, it began roughly concurrent with version 10_0 (1H October). I haven't spent much time investigating it because I haven't seen any negative effects...

Dirty upgrade on RT-AX86U from 3004.388.9_2 to 3004.388.10. No issues whatsoever.

If you're running the Wireguard client under windows, this may help: I had to manually change Wireguard to a private network (while keeping the overlying WiFi network defined as a public network) before I could access my intranet. After making that change, I was able to access intranet devices...

I can't speak to the experiences of others, but I've been using both the Samba and media server functionality for years without issue. I've never seen a RAM spike or high CPU usage. RAM usage is about 40% and stable. CPU usage only runs high when the media server is indexing after a reboot...

Sorry to resurrect an old thread, but I gave this a try. Samba threw a warning in the log that the command was in the wrong section of the .conf file. I used this .postconf script that cleared the warning and put the command in the [global] section where it wanted it: #!/bin/sh CONFIG=$1 if...

I'm running the Wireguard VPN server on an RT-AX86U. I use 3 clients: 1 android, 1 Win 10 and 1 Win 11 client. Config files are identical except for the address and keys. I can access my LAN devices and Samba shares without issue on the android and the Win 10 clients. I cannot access...

Just brainstorming....things that I would do to further diagnose: - is your media server visible to Windows (explorer network page) as a media device? - if you activate your Windows Media Server on your PC, do your Roku clients see it? - is the miniDLNA process running on your router ("top n 1"...

Google "ssh to asus router" for instructions on how to access router files. This video: is a good reference also. Note that, once you log on, commands are Linux commands... forward slash vs. backslash, cp to copy, ls to list files, rm to delete a file, etc. You log in using the same...

An additional test that can be run is to turn off and on the media server via the GUI without rebooting the router (be sure "rebuild database at start" set to "yes"). As both devices remain mounted through that step, that would either suggest or eliminate any sequential mounting effect on the...

If you find that it's an indexing issue, one of the problems that arises when media files are spread across multiple physical devices is that miniDLNA restarts every time a device is mounted, and the indexing process gets interrupted. This comes into play when the router is started or rebooted...