Recent content by Ayitaka

You might also want to look into Synology Link Aggregation and also Asus Link Aggregation, if your NAS and router support them.

RT-AX86U from 386.7_beta to 386.7. JFFS lost again. My apologies, during the beta you asked for a log when jffs was suddenly not mounting, but I did not have one. This time, I do. I posted everything up to the last jffs message I found. If you need more please let me know. Also sorry, I...

That worked, thank you.

Dirty upgrade, 386.5_2 to 386.7_beta1 on AX86U jffs unmounted, had to reformat and restore backup web UI now showing all left-side navigation sub-links underneath the categories (did not do this until I reformatted and restored jffs)

AX86U - Dirty upgrades 386.4 -> 386.5 -> 386.5_2 up and running for 2+ days, no problems. Thanks again for all the work you put into this project!

Dirty upgrade from 386.3_2. An hour in and main+nodes all running smoothly with zero new log entries. Thank you again for all you do, and Happy New Year!

RT-AC5300, dirty upgrade from 384.19. Nothing out of the ordinary other than a couple known issues which were easily rectified: Web interface wouldn't load. Known issue, just waited. Clients on Guest Network 1 were switched to their own subnet. Known issue, switched settings over to Guest...

Just upgraded to 384.19 and was checking amtm for updates and got this error about "No such file or directory" with regards to an md5sum check for flexqos.sh, despite not having it installed. Since FreshJR_QoS is now deprecated in amtm, I have installed FlexQoS to replace it and so there is no...

RT-AC5300: Dirty upgrade from 384.18 to 384.19 went smoothly. No problems to report. Thanks again!

RT AC-5300, fw and scripts as listed in signature. CPU graph on the Network Map page bounces around and hits 100% a lot - back and forth between CPU 1 and CPU 2. Normally, once the router settles down after rebooting and with minimal network usage, the graph would show the CPUs mostly idle with...

For my RT AC5300, I use this (usually $20) laptop cooling pad underneath it: https://www.amazon.com/gp/product/B07HF7T637 Legend: 2.4 GHz - 5 GHz - CPU Current Temperatures: 43 °C - 48 °C - 54 °C

I think that code segment is missing another set of ( ) around the first "program" and the "uth" message. To get it to work on my RT AC5300 (no AiMesh) I had to use: filter f_wlceventd { ( ( program("WLCEVENTD") or program("wlceventd") ) and ( message("ssoc") or message("uth") )...

RT-AC5300, dirty upgrade from 384.16 to 384.17 went fine and everything is up and running. Thanks for all the work you do!

Confirmed that this change to the skynet syslog-ng filter worked and, so far, it is logging properly now with syslog-ng 3.23-1.1, including stat lines as well as not losing any BLOCKED messages while firewall save is run: user@router:/tmp/mnt/sda1/entware/var/log# cat skynet-0.log Oct 31...

Just to clarify something, that skynet stat line I posted was from /mnt/sd1/skynet/events.log, probably from when it was running without syslog-ng. Since skynet/syslog-ng was not adding the stat line to the skynet-0.log file, I grabbed that line to show as an example but it may be formatted...