What's new

[RT-AC86U] Internet connection keeps dropping

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

seldg

New Around Here
My internet status on the Network Map section intermittently goes from connected, to network cable is unplugged, to disconnected, to your ISP's DHCP does not function properly. This happens every few seconds or minutes. I've already called my ISP to ask if anything was wrong but historically they take a while to offer any support at all, so I want to make sure that there's nothing wrong with the router at least. Current firmware version is 384.19.

Here's what the most recent entries from the system log look like:

Code:
Sep 21 00:45:52 WAN_Connection: WAN was restored
Sep 21 00:45:53 BWDPI: fun bitmap = 50b
Sep 21 00:45:54 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Sep 21 00:45:54 dhcp_client: bound 192.168.100.10/255.255.255.0 via 192.168.100.1 for 86400 seconds.
Sep 21 00:48:28 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 21 00:48:28 WAN_Connection: ISP's DHCP did not function properly.
Sep 21 00:48:28 DualWAN: skip single wan wan_led_control - WANRED off
Sep 21 00:48:30 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 21 00:48:33 WAN_Connection: Ethernet link up.
Sep 21 00:48:33 rc_service: wanduck 1184:notify_rc restart_wan_if 0
Sep 21 00:48:33 wsdd2[1317]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Sep 21 00:48:38 wsdd2[1317]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Sep 21 00:48:38 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Sep 21 00:48:38 wan: finish adding multi routes
Sep 21 00:48:38 miniupnpd[8927]: shutting down MiniUPnPd
Sep 21 00:48:38 miniupnpd[9891]: HTTP listening on port 46881
Sep 21 00:48:38 miniupnpd[9891]: Listening for NAT-PMP/PCP traffic on port 5351
Sep 21 00:48:41 WAN_Connection: WAN was restored.

Other settings which I've tried out based on other fixes online:
1. DHCP query frequency is in normal mode
2. Tried Cloudflare and Google DNS
3. Enable WAN down browser redirect notice set to no

Initially with these settings I thought I fixed it momentarily but a few minutes after I noticed the disconnections again.

I'm a beginner here so I'm not sure what other information I have to provide. Any help would be appreciated!
 
Last edited:
I'd have to see the complete log to be sure but the part you have shown is typical of what you see when the cable modem is rebooted. The giveaway is this line:
Code:
Sep 21 00:45:54 dhcp_client: bound 192.168.100.10/255.255.255.0 via 192.168.100.1 for 86400 seconds.
Log into your cable modem at look at its log file (if it has one). When there are ISP issues you often see "partial service" messages and the modem constantly rebooting itself.
 
I'd have to see the complete log to be sure but the part you have shown is typical of what you see when the cable modem is rebooted. The giveaway is this line:
Code:
Sep 21 00:45:54 dhcp_client: bound 192.168.100.10/255.255.255.0 via 192.168.100.1 for 86400 seconds.
Log into your cable modem at look at its log file (if it has one). When there are ISP issues you often see "partial service" messages and the modem constantly rebooting itself.

Here's the log! It's pretty late where I am so I'll check the modem's log first thing tomorrow morning.
 

Attachments

  • syslog.txt
    272.1 KB · Views: 163
There is definitely something wrong with the modem connection. When it does connect it is only at 100 Mbps (I'm assuming your cable modem has a gigabit socket?). That might imply that there is a fault with the Ethernet cable between the router and modem. Try changing it with another known working Cat5e cable.
Code:
Sep 20 18:51:21 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:51:24 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:52:52 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:52:55 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:53:16 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:53:19 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:54:02 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:54:05 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:54:36 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:54:39 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:55:25 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:55:28 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
 
I'm following this, I've been having similar issues recently. I have none of the log entries that indicate the same issues here though.
 
There is definitely something wrong with the modem connection. When it does connect it is only at 100 Mbps (I'm assuming your cable modem has a gigabit socket?). That might imply that there is a fault with the Ethernet cable between the router and modem. Try changing it with another known working Cat5e cable.
Code:
Sep 20 18:51:21 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:51:24 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:52:52 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:52:55 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:53:16 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:53:19 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:54:02 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:54:05 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:54:36 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:54:39 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Sep 20 18:55:25 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Sep 20 18:55:28 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex

Thank you! Just checked out the modem this morning which is placed in my dad's room. He has the modem plus another hub for other LAN cables. The cable that connected to the router was connected to the hub not to the modem itself and the light assigned to it would blink on and off periodically. Since rewiring it directly into the modem the WAN port status now displays 1 Gbps. I'll monitor the disconnection status to see if it solves it, but hopefully that was it!

It does display this though not sure if it still pertains to some form of disconnection:
Code:
Sep 21 09:30:19 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth A6:6C:ED:6F:98:C1, status: Successful (0)
Sep 21 09:30:19 wlceventd: WLCEVENTD wlceventd_proc_event(510): eth5: ReAssoc A6:6C:ED:6F:98:C1, status: Successful (0)
Sep 21 09:30:19 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth6: Disassoc A6:6C:ED:6F:98:C1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 21 09:30:19 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth6: Disassoc A6:6C:ED:6F:98:C1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)

Here's the modem log from this morning and the most recent router log:
 

Attachments

  • hwontlog.txt
    9 KB · Views: 1,306
  • syslog (1).txt
    452.5 KB · Views: 148
Last edited:
@seldg There doesn't appear to be any problems reported in that log file, which is good. Your device appears to be a HG8245Q2 which is a GPON/router and not a modem at all. That would explain the strange IP address you were getting.

Hopefully your rewiring will solve the problem.
 
@ColinTaylor seems to be working fine now! No drops observed. Thank you so much! It was such a simple solution, but I wasn't able to pinpoint that the issue was from the source of the internet that kept rebooting itself.
 

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