Hawk
Very Senior Member
Majority of code is closed source, rest of it is scatter to much to make sense.Is the Dual-WAN code still closed-source?
Majority of code is closed source, rest of it is scatter to much to make sense.Is the Dual-WAN code still closed-source?
When applying update to my 86U, as soon as I selected the file for upload, I saw Applying Settings, Please Wait. Didn't have to choose apply or anything.
Nothing more, so I waited until I saw the LEDs return to normal then refreshed the browser to get the router login page.
If this is the intended result, I vote for the old progress info to return.
Is the Dual-WAN code still closed-source?
Nov 8 00:04:41 kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
When applying update to my 86U, as soon as I selected the file for upload, I saw Applying Settings, Please Wait. Didn't have to choose apply or anything.
Nothing more, so I waited until I saw the LEDs return to normal then refreshed the browser to get the router login page.
Updated my AC86U and everything is working fine.
When I look at Tools/Sysinfo HW acceleration, runner and flow-cache are now enabled, but before on 384.13 only flow-cache was enabled without changing any settings.
384.13 to 384.14 (dirty). Working nicely on the ax88. I know this is not Merlin code specific, but I had some problems getting AImesh back on line. What is the proper upgrade sequence? I did:
1. Update main router (Merlin code - 384.14 beta ).
2. Update AImesh router (Asus equivalent code -384_81116).
Had a heck of a time getting the mesh back on-line. Had to reset the mesh unit several times, and move the unit closer to the main router. Should I have done this in the opposite order?
everything working fine. DCD tainted crash is still there, I guess asus has still not fixed it>
everything working fine. DCD tainted crash is still there, I guess asus has still not fixed it>
I have AiProtection OFF and I get DCD tainted crashes constantly.I found that it happens when virtual network interface is created (pixelserv-tls which comes with Diversion Standard creates one ) and AiProtection is ON .
There are two workarounds.I have AiProtection OFF and I get DCD tainted crashes constantly.
It is also caused by enabling Traffic Analyzer - Statistic. When I turn that and AiProtection off, no more crashes cluttering up the log.I have AiProtection OFF and I get DCD tainted crashes constantly.
There are two workarounds.
Easier
https://www.snbforums.com/threads/script-to-remove-dcd-crashes-from-system-log.54734/
More powerful with enhanced logging.
https://www.snbforums.com/threads/scribe-syslog-ng-and-logrotate-installer.55853/
It is also caused by enabling Traffic Analyzer - Statistic. When I turn that and AiProtection off, no more crashes cluttering up the log.
everything working fine. DCD tainted crash is still there, I guess asus has still not fixed it>
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!