RT-AX88U No Internet red light on reboot

Swindiff

Occasional Visitor
My router used to reboot fine and reconnect to the internet on reboot. However, now every time I reboot the router I just get the red light on the router and no internet connection. I can easily fix it by logging onto the router from the LAN and turning the internet switch off and back on again in the GUI. This is a bit of a PITA though and means I need to be at home to be able to do this. I was hoping that the firmware update I just performed (3.0.0.4.388_20558-g9ebe4e1) might fix this issue but it still occurs. Is this a known issue with a simple fix?
Cheers
 

ColinTaylor

Part of the Furniture
Check the router's System Log. It should indicate the reason it can't initially connect to the internet.

What is your "WAN Connection Type" set to? Automatic IP, PPPoE, etc?
 

L&LD

Part of the Furniture
Are you using LAN Ports 5-8 on your router? If so, don't.

The use of those ports can cause many issues, (including what you're reporting). Buy a cheap $20 8 Port switch instead and only use Ports 1-4.

You can try to fully power down the router (not a reboot). Pull the power plug from both the router and the wall plug, and wait for a few minutes. Then, power it on again. Note this will only be a temporary fix though (if it works).
 

Swindiff

Occasional Visitor
Hi
Thanks for your replies. WAN Connection is PPPoE, I am only using ports 1,2 and 3 on the router.
What should I be looking for in the log?
 

ColinTaylor

Part of the Furniture
What should I be looking for in the log?
I don't have a PPPoE connection so can't give precise examples. But look for messages at startup that mention "wan" and "ppp" (both upper and lower case text).
 

Swindiff

Occasional Visitor
Even though I cleared the log and then rebooted, the new log shows a load of entries from yesterday, then a load from 5th May, then the entries from today. Confused.
 

ColinTaylor

Part of the Furniture
This is normal. When your router starts up during the reboot process it doesn't know the correct date or time so it defaults to 5th May. So by looking for this date it is easy to spot the reboot messages. Once the router has connected to the internet it will correct the date and time.
 

dosborne

Very Senior Member
Are you using LAN Ports 5-8 on your router? If so, don't.
Strange. I specifically chose this model to do away with the extra switches I had. I have been using all 8 ports for 3+(?) years now with no apparent issues. Maybe I just don't use the "correct" combination of things to trigger it, or it isn't that common am issue.
 

L&LD

Part of the Furniture
Consider yourself lucky then. If/when the router's symptoms seem to send you on wild troubleshooting goose chases, be sure to test for the problem ports, first. ;)
 

Swindiff

Occasional Visitor
May 5 06:05:14 pppd[1607]: Connected to ******** via interface eth0
May 5 06:05:14 pppd[1607]: Connect: ppp0 <--> eth0
May 5 06:05:14 pppd[1607]: CHAP authentication succeeded
May 5 06:05:14 pppd[1607]: peer from calling number ******** authorized
May 5 06:05:14 pppd[1607]: local IP address ********
May 5 06:05:14 pppd[1607]: remote IP address ********
May 5 06:05:14 pppd[1607]: primary DNS address ********
May 5 06:05:14 pppd[1607]: secondary DNS address ********
May 5 06:05:14 kernel: netdev path : wds0.0.1.0 -> wds0.0.1
May 5 06:05:14 kernel: BCMVLAN : wds0.0.1 mode was set to RG
May 5 06:05:14 kernel: netdev path : wds0.0.1.501 -> wds0.0.1
May 5 06:05:14 kernel: BCMVLAN : wds0.0.1 mode was set to RG
May 5 06:05:14 kernel: netdev path : wds0.0.1.502 -> wds0.0.1
May 5 06:05:14 kernel: BCMVLAN : wds0.0.1 mode was set to RG
May 5 06:05:14 miniupnpd[1469]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 06:05:14 wan: finish adding multi routes
May 5 06:05:14 miniupnpd[1469]: shutting down MiniUPnPd
May 5 06:05:14 miniupnpd: it is advised to use network interface name instead of 192.168.1.1/255.255.255.0

Does this help at all?
 

Swindiff

Occasional Visitor
This started after we had out electric meter changed, so effectively a power cut. When the power was restored the router did not connect to the internet (I needed to turn the internet off and back on again in the GUI and that fixed it). It now does this every time the router is rebooted. I don't know if this is relevant or just a coincidence.
 

ColinTaylor

Part of the Furniture
May 5 06:05:14 pppd[1607]: Connected to ******** via interface eth0
May 5 06:05:14 pppd[1607]: Connect: ppp0 <--> eth0
May 5 06:05:14 pppd[1607]: CHAP authentication succeeded
May 5 06:05:14 pppd[1607]: peer from calling number ******** authorized
May 5 06:05:14 pppd[1607]: local IP address ********
May 5 06:05:14 pppd[1607]: remote IP address ********
May 5 06:05:14 pppd[1607]: primary DNS address ********
May 5 06:05:14 pppd[1607]: secondary DNS address ********
May 5 06:05:14 kernel: netdev path : wds0.0.1.0 -> wds0.0.1
May 5 06:05:14 kernel: BCMVLAN : wds0.0.1 mode was set to RG
May 5 06:05:14 kernel: netdev path : wds0.0.1.501 -> wds0.0.1
May 5 06:05:14 kernel: BCMVLAN : wds0.0.1 mode was set to RG
May 5 06:05:14 kernel: netdev path : wds0.0.1.502 -> wds0.0.1
May 5 06:05:14 kernel: BCMVLAN : wds0.0.1 mode was set to RG
May 5 06:05:14 miniupnpd[1469]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 06:05:14 wan: finish adding multi routes
May 5 06:05:14 miniupnpd[1469]: shutting down MiniUPnPd
May 5 06:05:14 miniupnpd: it is advised to use network interface name instead of 192.168.1.1/255.255.255.0

Does this help at all?
That all looks normal. If there are other problems they would show up further down the log. If you want us to investigate it post the complete log on pastebin.com and provide a link to it.
 

ColinTaylor

Part of the Furniture
Is it safe to post my entire log online?
Redact any occurrences of your public IP address and any other personal information that might be included (e.g. your email or DDNS address). Other stuff like MAC addresses and private IP addresses (e.g. 192.168.x.y) can be left in to aid debugging.
 

dosborne

Very Senior Member
(I needed to turn the internet off and back on again in the GUI and that fixed it).
Please let the rest of us know next time before you turn "the internet" off and on again. I was using it at the time :) :)
 

Log

New Around Here
Please let the rest of us know next time before you turn "the internet" off and on again. I was using it at the time :) :)
hahaha. but seriously guys there is something going on with latest set of firmwares. I do frequent updates as they come out for last 10 years AC68U and now AX86U but latest versions (in last 4 weeks) have be PIA. I have tried every textbook fix, resets etc, and have finally settled with 386.5_2 to be stable (last 24 hours). fingers crossed, I am sure it will get figured out as more and more do a fw update and start reporting this reboot issue 4-6 times a day with a crashlog that's doesn't indicate anything meaningful.
 

dosborne

Very Senior Member
I did say in the GUI ;)
Still funny :) So your GUI controls the entire internet :) :) I wish mine had such power.

Looks to me like something went bad around here.
Sep 25 17:47:05
When was the last time you reset and reconfigured manually from scratch? It seems to start a cascade of things starting with the ddns stuff. May be worth disabling that as a test. My next guess would be ppoe related as that is often a problem area.

If would think the initial supposition that it was related to the swap of your hydro meter is not accurate and it was just coincidental, or simply due to the reboot, but not more than that.
 

ColinTaylor

Part of the Furniture
Sorry for the delay in replying
I have posted my log here
Your log doesn't show any obvious problem with your internet connection. It looks to be working fine after the reboot but perhaps you can add some context to what you may have been seeing or doing.

As far as I can see you rebooted the router from the GUI at 17:48:01. The router came back up as normal and connected to the internet successfully at about 17:48:48. We know this because it was able to set its clock using NTP 7 seconds later at 17:48:55.

The only potentially odd thing that happens is between 17:52:05 and 17:52:10 where it restarts the WAN connection twice in a row. I don't know whether it was you that did this, I suspect not. It think this is linked to the automatic firmware update process. In any case it would have only caused a brief interruption to the internet of 5 seconds.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top