Using wrtmerlin 384.19 on an RT-AC68P with two AImesh nodes also running 384.19. Root node also running...
Diversion v4.1.12 with pixelsrv-tls and Medium blocking list and no custom blocked sites or ranges
Skynet v7.2.2
connmon v2.7.0
While our system can access the Internet most of the time, our web management UI shows two odd symptoms I'm not savvy enough to resolve.
General - Network Map: Internet status shows as Disconnected (again, despite Internet access working in general)
Administration - System: Router can't synchronize to NTP server pool.ntp.org or time.nist.gov. I can't ping either address from the router's shell, so am not surprised by this, just wondering what's blocking something so essential. I _can_ reach time.google.com, so switched to using that for NTP. While this is a workaround, I'd rather use one of the others.
Could Diversion be blocking something needed to show Internet status as connected and allow me to NTP sync? If so, I'm not sure where else to check, since I don't use a custom block list.
Could Diversion be blocking something needed to show Internet status as connected and allow me to NTP sync? If so, I'm not sure where else to check, since I don't use a custom block list.
I would rule Diversion out. Unless it indeed blocks the domain that Asus uses to determine the connectivity status.
Just disable Diversion and reboot, then look at the routers Syslog how soon NTP synced while it booted.
@MWGlidden
Are you on custom DNS, check under the "Advanced Settings" on the lefthand side, the click WAN. I usually get this if i'm running Non-ISP DNS then it will grab my external IP etc. But since i switched to continous mode in the WAN settings and custom DNS i rarely get this and when i do it resolves itself.
@muffintastic No custom DNS settings that I can see at the moment. These screenshots show my current settings, other than a cloned MAC that I obscured.
@thelonelycoder I disabled Diversion and rebooted, without a clear change in behavior. That was using Google as my NTP. Will try again later today with the original NTP addresses.
As Mentioned a few post up by Calkuling, I had the same problem for a couple of months ago. It turned out that my router from factory was set to be in developer mode. So I changed a 1 to a 0 and it was all goid after that.
The problem occured when I upgraded my firmware to a new one. I tried both stoch and merlin. The router it happened on is Ac 66u b1.
So, two question' did you just upgrade firmware? If so, what version did you come from?
Thanks all! I made the ATEMODE change to 1 and will be able to factory reset the router later this week as part of the testing. (Three different schedules in our house to work around.)
Also changed the DHCP frequency to "Continuous" per @muffintastic. Something must be better, because the Network Map's Internet Status now _alternates_ between (sometimes) Connected and (most of the time) Disconnected. This implies it's not a Skynet or Diversion issue, since I shouldn't get Connected at all if they're a culprit.
@jonasitanga I first noticed the "Internet Disconnected" status several months ago, perhaps Mar/Apr, and have updated firmware each time a new wrtmerlin comes out. If the ATEMODE change to 1 is a permanent fix, sounds like I'll see that once I can reset the router later this week?
P.S. While my AiMesh has three nodes right now, all three are different Asus hardware. I'm thinking of changing the root node to AC66U_B1 or AC1900 to see if it makes the whole system more reliable. Any opinion if using a particular root node will make a difference?
Tested the Connected / Disconnected frequency by watching the Network Map page. It will show "Connected" for perhaps 20 seconds, as on the screenshot, and then return to "Disconnected" for a minute or more. The timing seems consistent.
My mistake on the number, it was ATEMODE 0 (ssh command removed, apologies)
When I web searched for a similar solution, another forum recommended factory resetting the router after making the ATEMODE change to be sure it "took." That might or might not be relevant to my current situation. I'll go and check out the thread you linked now.
My mistake on the number, it was ATEMODE 0. Here's the exact ssh I ran via router shell:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
When I web searched for a similar solution, another forum recommended factory resetting the router after making the ATEMODE change to be sure it "took." That might or might not be relevant to my current situation. I'll go and check out the thread you linked now.
You have to remove those commands immediately. It´s against forum rules to write that info here. I think it´s in some way illegal and against Asus rules.
What was ATEMODE originaly set to before your tinkering?
You have to remove those commands immediately. It´s against forum rules to write that info here. I think it´s in some way illegal and against Asus rules.
What was ATEMODE originaly set to before your tinkering?
Not certain of the original ATEMODE setting. It's now 0 when I check it.
I _do_ know that another change appears to have resolved my connection problem. By disabling "DNS" monitoring and just using "ping," as on the screenshot, I'm now reliably "connected" from the Network Map's perspective. While I'm not sure why DNS would be the issue, that change made a difference.
I recently upgraded to Merlin for my RT-AC86U. Immediately after doing so I get this message mentioned previously, every 30seconds:
WARNING - router is in manufacturing mode, and can behave unexpectedly (did you mess with your bootloader?)
I have tried the Nvram commands with reboot that have been referred to previously but it does not stop the message, either before or after the reboot. It reports ATEMODE being 1 after reboot always, although after running the commands before reboot it does report that as 0 after running the commands to reset it to 0.
Has anyone experienced the same problem after upgrading to merlin? Do i need to factory reset and start from scratch.
As an aside I upgraded to merlin in frustration with the default ASUS firmware as I could not get dual wan or 4G/Android working. Upgrading to merlin fixed that immediately as well as fixing another bug that has been present in the ASUS firmware for years whereby the router does not detect that it is online.
This router is Awful & Awesome at the same time. Awful because of the top 2 bugs as well as the wifi frequently needing to be reset (will have to wait to see if Merlin fixed that too). Awesome because there are very few with dual wan, 2x USB and 4x lan ports.
All in all I'd stick with merlin and just ignore the message if I need to, but even better if someone has fixed this before and can share how they solved it.
I recently upgraded to Merlin for my RT-AC86U. Immediately after doing so I get this message mentioned previously, every 30seconds:
WARNING - router is in manufacturing mode, and can behave unexpectedly (did you mess with your bootloader?)
I have tried the Nvram commands with reboot that have been referred to previously but it does not stop the message, either before or after the reboot. It reports ATEMODE being 1 after reboot always, although after running the commands before reboot it does report that as 0 after running the commands to reset it to 0.
Has anyone experienced the same problem after upgrading to merlin? Do i need to factory reset and start from scratch.
As an aside I upgraded to merlin in frustration with the default ASUS firmware as I could not get dual wan or 4G/Android working. Upgrading to merlin fixed that immediately as well as fixing another bug that has been present in the ASUS firmware for years whereby the router does not detect that it is online.
This router is Awful & Awesome at the same time. Awful because of the top 2 bugs as well as the wifi frequently needing to be reset (will have to wait to see if Merlin fixed that too). Awesome because there are very few with dual wan, 2x USB and 4x lan ports.
All in all I'd stick with merlin and just ignore the message if I need to, but even better if someone has fixed this before and can share how they solved it.
I'm facing the same problem. In my case the router is GT-AX6000, firmware Asus Merlin 3004.388.8_2_rog.
The error "wanduck: WARNING - router is in manufacturing mode and can behave unexpectedly (did you mess with your bootloader?)" started appearing -or not noticed before- at the beginning of this week, after a router reboot. Although the error is persistent, as said before every 30 seconds aprox., I' haven't noticed any problem regarding to connectivity/performance issues, or unexpected behaviors, on any of my devices.
Since then, I've tried to move ATEMODE to 0, as noted on
My RT-AX86U-PRO [recently purchased] has gone decidedly "wobbly" all of a sudden [it was running Merlinware 388.5 at the time - not that that has anything to do with it]. Began with some WIFI connectivity issues - noticed the the AiMesh node was no longer connected. I tried to login to webui...
www.snbforums.com
Those commands (may be my fault?), just add a new line to nvram settings, and not modifies ATEMODE value. In order to modify ATEMODE you have to adjust the statement by using ATEMODE command and not a*****eATEMODE. For the commit statement, apparently, there is no difference using one or other.
After playing a while with nvram and achieving to modify ATEMODE value, I realizad that:
1.- Setting ATEMODE to 0 is temporary, when rebooting, or factory resetting, these statement in nvram appears again.
2.- If use a*****eATEMODE commands the only thing that occurs is you add a new line in NVRAM while old ATEMODE still persists.
3.- There is one difference, the a*****eATEMODE entry and its value persists after a reboot or resetting to factory defaults.
Also, I've been checking if with ASUS Stock firmware it does happen again and:
.- You don't get the wanduck error.
.- In its place you get a "Not Connected" warning on WAN interface, this error avoids NTP protocol to work and the router system time is incorrect.
.- "Not Connected" warning is a false warning, because, in fact all is running fine and you are connected to internet, as all of your devices, without any problem, or not noticed any problem during the tests.
.- Nvram contains the ATEMODE to 1 statement too. I guess the wanduck error is related to the wan connection and, if this connection isn't reporting as connected wanduck does not report the problem.
I'm lost (and tired... ), there is not much info about this problem, as my router is on warranty I think I'll be waiting for new firmware for some weeks. If new firmware does not resolve the problem, I will go for an RMA.
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!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
), there is not much info about this problem, as my router is on warranty I think I'll be waiting for new firmware for some weeks. If new firmware does not resolve the problem, I will go for an RMA.
