In the system log page.
I run scribe & uiScribe, is that why I do not see it?
In the system log page.
I run scribe & uiScribe, is that why I do not see it?
I know. We already have a thread for it. I didn't talk much either. Just letting him know that a simple fan fixes itThat why I didn't talk much.
Buy USB laptop cooling pad. I use one for my RT-AC5300; the temp keps steady @60CGot a cheap chinese usb fans kit. They have those air filters. Replaceable too it seems like. With the filters it's only pushing like a very small amount of air. I thought it wouldn't be enough. But yes it was more than enough.
From the lowest 80C and normally at 90C (and more if on load) . To about 50C on the lowest and 60C on load . Pretty big difference right there.
The lowest without fan I could get before 386 was 70C and about 69C (nice)
No. This is the compromise for me supporting the ROG models - I won't be using the ROG UI.
Yes, that's the reason. The entire page (https://router.asus.com:8443/Main_LogStatus_Content.asp) has been replaced by uiScribe, along with the option to set the log level, I supposeI run scribe & uiScribe, is that why I do not see it?
@JohnD5000 - You can still change the log level - first uninstall uiScribe [but keep data] - then go to System Log page - change level - reinstall uiScribe ... sorted.Yes, that's the reason. The entire page (https://router.asus.com:8443/Main_LogStatus_Content.asp) has been replaced by uiScribe, along with the option to set the log level, I suppose
If you don't want to see those messages, just write a filter and direct them to /opt/var/log/garbage.log. That's my digital trash can for everything I don't want to see in my logs.
@JohnD5000 - You can still change the log level - first uninstall uiScribe [but keep data] - then go to System Log page - change level - reinstall uiScribe ... sorted.
nvram get log_level
nvram set log_level=5
nvram commit
the log levels don't really make much sense for syslog-ng (scribe), as they apply to what the built-in syslog is doing rather than syslog-ng@JohnD5000 - You can still change the log level - first uninstall uiScribe [but keep data] - then go to System Log page - change level - reinstall uiScribe ... sorted.
Thanks for that - understood. seemed to make a difference to my logs after I spotted the suggestion elsewhere and gave it a whirl - but imagination is a powerful thing .the log levels don't really make much sense for syslog-ng (scribe), as they apply to what the built-in syslog is doing rather than syslog-ng
i think it will work for what entries are actually generated by klogd, but the "messages to show" wouldn't take effect. or something like thatThanks for that - understood. seemed to make a difference to my logs after I spotted the suggestion elsewhere and gave it a whirl - but imagination is a powerful thing .
Which modules are these?@RMerlin
EDIT: For the next Beta, is there any possibility you could investigate the inclusion of kernel netlink attributes/modules
for the recent v386.2Code:FRA_SPORT_RANGE FRA_DPORT_RANGE
iproute2
v5.11.0 HND models upgrade?
Many thanks
SorryWhich modules are these?
It will have to wait until 386.3, 386.2 will not receive any further change beyond bugfixes this late in the development cycle.
ip rule help
Usage: ip rule { add | del } SELECTOR ACTION
ip rule { flush | save | restore }
ip rule [ list [ SELECTOR ]]
SELECTOR := [ not ] [ from PREFIX ] [ to PREFIX ] [ tos TOS ] [ fwmark FWMARK[/MASK] ]
[ iif STRING ] [ oif STRING ] [ pref NUMBER ] [ l3mdev ]
[ uidrange NUMBER-NUMBER ]
[ ipproto PROTOCOL ]
[ sport [ NUMBER | NUMBER-NUMBER ]
[ dport [ NUMBER | NUMBER-NUMBER ] ]
ip rule add sport 12345 table 300
ip rule
0: from all lookup local
9809: from all lookup 300
9810: from all fwmark 0xd2 lookup 210
9820: from all fwmark 0xdc lookup 220
32766: from all lookup main
32767: from all lookup default
No idea. Note that some features in iproute2 may possibly require a specific kernel version (for example, Cake required a specific kernel version, or a manual backport).A quick Goggle found the references, so I blindly assumed they were kernel module compile/include flags?
Apr 1 09:15:18 vpn: + 597c4d91b055409f9dbaa3dc128391e2 10.10.10.1/32 == 50.211.2.169 -- 75.165.xx.xxx == 0.0.0.0/0
May 5 01:05:08 syslogd started: BusyBox v1.25.1
May 5 01:05:08 crashlog: LOG
May 5 01:05:08 crashlog: <6>mod epilog takes 0 jiffies
May 5 01:05:08 crashlog: <6>IDPfw: Exit IDPfw
May 5 01:05:08 crashlog: <6>CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -1
May 5 01:05:08 crashlog: <4>dhd_os_stop_wd_thread(): thread:dhd_watchdog_thread:2ee terminated OK
May 5 01:05:08 crashlog: <6>CFG80211-ERROR) wl_add_remove_eventmsg : Get event_msgs error (-1)
May 5 01:05:08 crashlog: <6>br0: received packet on eth6 with own address as source address
May 5 01:05:08 crashlog: <6>br0: received packet on eth6 with own address as source address
May 5 01:05:08 crashlog: <0>NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [pdc_rx:268]
May 5 01:05:08 crashlog: <4>Modules linked in: tun init_addr( (null) - (null)), core_addr(ffffffbffc168000 - ffffffbffc16b54c)
May 5 01:05:08 crashlog: <4> sch_cake init_addr( (null) - (null)), core_addr(ffffffbffc18d000 - ffffffbffc191fb8)
May 5 01:05:08 crashlog: <4> tdts_udbfw(O-) init_addr( (null) - (null)), core_addr(ffffffbffc15b000 - ffffffbffc160500)
May 5 01:05:08 crashlog: <4> tdts_udb(PO) init_addr( (null) - (null)), core_addr(ffffffbffc357000 - ffffffbffc37a054)
May 5 01:05:08 crashlog: <4> tdts(PO) init_addr( (null) - (null)), core_addr(ffffffbffd20a000 - ffffffbffd245de8)
May 5 01:05:08 crashlog: <4> sr_mod init_addr( (null) - (null)), core_addr(ffffffbffd202000 - ffffffbffd204308)
May 5 01:05:08 crashlog: <4> cdrom init_addr( (null) - (null)), core_addr(ffffffbffd1f5000 - ffffffbffd1f9cb0)
May 5 01:05:08 crashlog: <4> thfsplus(O) init_addr( (null) - (null)), core_addr(ffffffbffd1d3000 - ffffffbffd1e0084)
May 5 01:05:08 crashlog: <4> tntfs(PO) init_addr( (null) - (null)), core_addr(ffffffbffd146000 - ffffffbffd192438)
May 5 01:05:08 crashlog: <4> tfat(PO) init_addr( (null) - (null)), core_addr(ffffffbffd0f1000 - ffffffbffd122368)
May 5 01:05:08 crashlog: <4> uas init_addr( (null) - (null)), core_addr(ffffffbffd0e8000 - ffffffbffd0ea140)
May 5 01:05:08 crashlog: <4> usb_storage init_addr( (null) - (null)), core_addr(ffffffbffd0cf000 - ffffffbffd0d2c20)
May 5 01:05:08 crashlog: <4> sg init_addr( (null) - (null)), core_addr(ffffffbffd0c1000 - ffffffbffd0c55d0)
May 5 01:05:08 crashlog: <4> sd_mod init_addr( (null) - (null)), core_addr(ffffffbffd0b3000 - ffffffbffd0b7bd8)
May 5 01:05:08 crashlog: <4> scsi_mod init_addr( (null) - (null)), core_addr(ffffffbffd075000 - ffffffbffd085960)
May 5 01:05:08 crashlog: <4> nf_nat_sip init_addr( (null) - (null)), core_addr(ffffffbffd06e000 - ffffffbffd06f998)
May 5 01:05:08 crashlog: <4> nf_conntrack_sip init_addr( (null) - (null)), core_addr(ffffffbffd063000 - ffffffbffd066108)
May 5 01:05:08 crashlog: <4> nf_nat_h323 init_addr( (null) - (null)), core_addr(ffffffbffd05d000 - ffffffbffd05e0e8)
May 5 01:05:08 crashlog: <4> nf_conntrack_h323 init_addr( (null) - (null)), core_addr(ffffffbffd04b000 - ffffffbffd04ea00)
May 5 01:05:08 kernel: klogd started: BusyBox v1.25.1 (2021-03-28 13:47:46 EDT)
May 5 01:05:08 crashlog: <4> nf_nat_rtsp init_addr( (null) - (null)), core_addr(ffffffbffd046000 - ffffffbffd0469f0)
May 5 01:05:08 crashlog: <4> nf_conntrack_rtsp init_addr( (null) - (null)), core_addr(ffffffbffd040000 - ffffffbffd041188)
May 5 01:05:08 kernel: rdd_init_params.runner_nat_cache_key_ptr=0xffffffc00bd00000
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!