Question Need help figuring out why the internet drops randomly

[WrongRookie]

I got an RT-AX3000 router but occasionally i get internet cutting briefly and then connecting it again. Can anyone help?

This is the log incase it helps with the issue.

Apr 20 13:42:58 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.

Apr 20 13:43:07 WAN(0) Connection: Fail to connect with some issues.

Apr 20 13:43:17 WAN(0) Connection: WAN(0) link down.

Apr 20 13:43:27 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex

Apr 20 13:43:28 WAN(0) Connection: WAN(0) link up.

Apr 20 13:43:28 rc_service: wanduck 1422:notify_rc restart_wan_if 0

Apr 20 13:43:32 pppd[29866]: pppd 2.4.7 started by admin, uid 0

Apr 20 13:43:37 WAN(0) Connection: Fail to connect with some issues.

Apr 20 13:43:41 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.

Apr 20 13:43:43 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex

Apr 20 13:43:53 zcip client: configured 169.254.16.97

Apr 20 13:43:57 dhcp client: bound 192.168.1.2/255.255.255.0 via 192.168.1.1 for 259200 seconds.

Apr 20 13:44:01 roamast: sta[66:7D:73:1F:77:BD] on ap[04:42:1A:60:E2:10], rcpi is 107 and rssi is -57

|
|
|

[Moderator edit to remove lengthy log entries.]

|
|
|

(Also..is there a way that I can just edit the log to make it that you can only scroll the log code in its own dialogue box and not scrolling on the actual post?)

 

[bill001g]

If you can ping by IP address but not by name it means there is some kind of DNS issue.

The default method commonly used is your router acts as a cache to the ISP DNS server. So it could be a issue with the router or it can be a issue with the ISP DNS.

I would try the command

nslookup www.google.com

Then try
nslookup www.google.com 1.1.1.1

What you are mostly looking for is a error message in the first case. It could be it thinks the dns server is 10.0.0.1 or it might resolve to 10.0.0.1

The second one should show you multiple IP addresses that are used by www.google.com.

You can manually set the dns in the IPv4 setting on your pc but it has become very messy with the ability to set the DNS in the browsers also so it is not as simple as it once was to be sure what dns you are actually using.

 

[WrongRookie]

If you can ping by IP address but not by name it means there is some kind of DNS issue.

The default method commonly used is your router acts as a cache to the ISP DNS server. So it could be a issue with the router or it can be a issue with the ISP DNS.

I would try the command

nslookup www.google.com

Then try
nslookup www.google.com 1.1.1.1

What you are mostly looking for is a error message in the first case. It could be it thinks the dns server is 10.0.0.1 or it might resolve to 10.0.0.1

The second one should show you multiple IP addresses that are used by www.google.com.

You can manually set the dns in the IPv4 setting on your pc but it has become very messy with the ability to set the DNS in the browsers also so it is not as simple as it once was to be sure what dns you are actually using.

C:\Windows\System32>nslookup www.google.com
Server: RT-AX3000-E210
Address: 192.168.50.1

Non-authoritative answer:
Name: www.google.com
Addresses: 2404:6800:4007:820::2004
142.250.193.132


C:\Windows\System32>nslookup www.google.com 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: www.google.com
Addresses: 2404:6800:4007:829::2004
172.217.160.132

Is it expected that it should show my router as the server?

 

[kanewolf]

C:\Windows\System32>nslookup www.google.com
Server: RT-AX3000-E210
Address: 192.168.50.1

Non-authoritative answer:
Name: www.google.com
Addresses: 2404:6800:4007:820::2004
142.250.193.132


C:\Windows\System32>nslookup www.google.com 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: www.google.com
Addresses: 2404:6800:4007:829::2004
172.217.160.132

Is it expected that it should show my router as the server?

It is not uncommon for home routers to cache DNS. This speeds up repeated access to a single IP address. Your DNS traffic stays on the LAN and the router requests DNS only when it can't resolve with the cache. The DNS server IP address is passed to the client (your PC) as part of the DHCP traffic when your PC boots (or wakes up). You can override this in Windows in the properties of your LAN hardware.

 

[WrongRookie]

A quick update on the situation.

Apparently the modem stopped working and the ISP just changed the power adaptor to fix it. Since then there has been no issues with the internet disconnecting.

If this is really the case then I want to apologize you all for wasting your time with my problem as it's pretty embarassing how the power adaptor was the main problem.

That said it is odd that they didn't replace the modem itself but the adapter instead. I do wonder what would have happened if the modem stopped working if it was sabotaged or if the power fluctuation causes it to fail.