You do know that there IS a log setting in the Merlin version for you to change what you see in the log. Click the dropdown where apparently it now says Debug and CHANGE it to Notice and you wont see hardly anything at all in the log...updated RT-AC86U from v384.19 to 386.1_2
some noticeable improvements that i like, but constant log spam as usual + A LOT of these messages:
nf_conntrack: expectation table full
(lots of these, every minute or so, non-stop)
net_ratelimit: 41 callbacks suppressed
(seems to occur after rebooting via web UI)
acsd adjusted channel spec
(i don't need to know everytime the channel changes!)
wlceventd_proc_event
(just insane)
... on and on, ad nauseam
i use a remote log server (Syslog Watcher on port 514) to receive log messages from several devices on our network, including the AC86U, so this ridiculous level of log spam is unacceptable. yeah i can create filters to hide some of the router spam (which i've done), but i shouldn't have to do this. debug logging should be disabled by default on the 86U, period.
i'd hoped to finally put my RT-AC86U into service (in router mode instead of an AP) after waiting so long for a solid-stable, reliable firmware revision, but it wasn't to be. i'm disappointed and fed up with Asus' flakey firmware, tbh. i don't know what all the 'nf_conntrack: expectation table full' messages mean, but there's a steady stream of them.
and before anyone asks, YES, I did hard-reset the router to factory defaults (several times) after updating it from Asuswrt-Merlin v384.19 to v386.1_2 and reconfiguring all settings by hand (no scripts or third-party software installed). i had been using the 86U as an access point with Merlin v384 before updating it to v386, but i really should've known better with this router. just no good, no joke.
so we're back to the 1900P running an outdated version Merlin (380.70), because i have no confidence in the AC86U at this point, if ever. at least our 1900P is reliable and doesn't spam me to death with utterly useless debugging info. how difficult can it be for Asus to simply turn OFF debug logging??
doesn't workYou do know that there IS a log setting in the Merlin version for you to change what you see in the log. Click the dropdown where apparently it now says Debug and CHANGE it to Notice and you wont see hardly anything at all in the log...
It does work. Hit apply after you change it and it'll refresh. Then hit cleardoesn't work
NO it does not work. the debug messages keep coming. this is a known issue. please keep up.It does work. Hit apply after you change it and it'll refresh. Then hit clear
Not a known issue. If that didn't work for you, you've got other issues.NO it does not work. the debug messages keep coming. this is a known issues. please keep up.
omg, just search this forum. even Merlin mentioned something about Asus leaving debug logging enabled for whatever reason, i don't remember exactly. in any case, the router log settings have no effect on the steady stream of debug messages.Not a known issue. If that didn't work for you, you've got other issues.
Yes they did leave debugging on which is why YOU CAN TURN IT OFF either by SSH or the drop down in Merlin fw. If that setting isn't working for you, then something else is wrong. The setting works along with the ability to SSH and disable it.omg, just search this forum. even Merlin mentioned something about Asus leaving debug logging enabled for whatever reason, i don't remember exactly. in any case, the router log settings have no effect on the steady stream of debug messages.
you're wrong, and we're done. ignored.Yes they did leave debugging on which is why YOU CAN TURN IT OFF either by SSH or the drop down in Merlin fw. If that setting isn't working for you, then something else is wrong. The setting works along with the ability to SSH and disable it.
Perfect. That remote log server is probably the issue...you're wrong, and we're done. ignored.
this seems resolved with 386.1_2. fingers crossedRT-AC68U:
- router homepage (index.asp) would randomly lock up/unresponsive after login, have to kill the tab and try again.
- this was during ~1 day uptime dirty upgrade, then ~2 days fact. reset. till now.
Hmm. Notice works for me!you're wrong, and we're done. ignored.
Node then router. Just do it now.Getting ready to upgrade from 386.1 to 386.1_2 on a two router AiMesh system. Is there a preferred order to apply the upgrades? i.e. should I do the main router first and the the node? Or should I do the node first and the the main router?
Also, should I wait a certain amount of time after doing one upgrade before upgrading the second router?
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!