Just want to say
Apr 2 08:38:22 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Apr 2 08:38:24 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Apr 2 08:38:32 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Apr 2 08:38:42 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Apr 2 08:46:03 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Apr 2 08:46:05 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Apr 2 08:46:13 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Apr 2 08:46:23 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Confirming similar situation with stock ASUS firmware 3.0.0.4.386_46065 (2022/01/12) on RT-AX88U. Very vanilla setup, no VPNs, etc. with a 1Gb/s WAN connection to a fiber modem.It looks like that I figured out a solution/workaround...
Go to administration > system
At 'Network Monitoring' enable 'dns query'
Set 'Resolve Hostname' to 1.1.1.1
Set 'Resolved IP Addresses' to 1.1.1.1
Click 'Apply' on the bottom of the screen
At 'Network Monitoring' disable 'dns query'
Click 'Apply' on the bottom of the screen
Tick 'reboot' on top of the screen
Strange but true... Just enable 'dns query' and disable it again exactly like the above steps.. and the problem is gone... which is strange because according to GUI settings, all settings are turned back as they were before... so no changes should be expected in the behaviour of showing 'disconnected'...
Did you try any of the solutions mentioned in this thread?The thread is a week old but just noticed the same "Internet status - Disconnected" though working error message. Have a RT-AX86U. Any further info on this error or is everyone just ignoring it?
I believe the problem occurs when the router attempts to ping a DNS name to verify connectivity. The problem with this method is that it depends on DNS and internet access, rather than just internet access.I used iTyPsIDg's solution/suggestion (#15 message in this thread) and it has worked fine. Wasn't really worried about a solution but was rather quite interested in the causation. Thanks
That would make sense. It is interesting that, reflecting upon prior comments in this thread, the DNS names I'm using are NordVPN DNS servers.I believe the problem occurs when the router attempts to ping a DNS name to verify connectivity. The problem with this method is that it depends on DNS and internet access, rather than just internet access.
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!