RT-AC68P Disconnection Issue (PPPoE)

[Zahidur Abedin]

I recently bought the RT-AC68P to upgrade. However the router seems to be constantly disconnecting and re-connecting to the internet. I tried downgrading the firmware and even installing RMerlin's firmware without any luck. However, my old router, a TrendNet TEW-652BRP seems to be working fine with the internet connection. I posted the syslog text below for convenience. Any help would be appreciated! Thank you.

Jan 1 00:00:20 stop_nat_rules: apply the redirect_rules!
Jan 1 00:00:20 WAN Connection: ISP's DHCP did not function properly.
Jan 1 00:00:20 dnsmasq[562]: warning: interface ppp1* does not currently exist
Jan 1 00:00:20 RT-AC68P: start httpd
Jan 1 00:00:20 disk monitor: be idle
Jan 1 00:00:20 miniupnpd[591]: HTTP listening on port 43192
Jan 1 00:00:20 miniupnpd[591]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:00:20 syslog: Generating SSL certificate...
Jan 1 00:00:24 kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:24 kernel: wl_module_init: txworkq set to 0x1
Jan 1 00:00:24 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Jan 1 00:00:24 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Jan 1 00:01:22 rc_service: httpd 568:notify_rc start_autodet
Jan 1 00:01:25 rc_service: httpd 568:notify_rc start_autodet
Jan 1 00:01:27 rc_service: autodet 729:notify_rc restart_wan
Jan 1 00:01:28 kernel: Attempt to kill tasklet from interrupt
Jan 1 00:01:31 rc_service: httpd 568:notify_rc start_autodet
Jan 1 00:01:31 rc_service: skip the event: start_autodet.
Jan 1 00:01:32 kernel: Attempt to kill tasklet from interrupt
Jan 1 00:01:37 rc_service: httpd 568:notify_rc start_autodet
Jan 1 00:01:53 rc_service: httpd 568:notify_rc restart_wan_if 0
Jan 1 00:01:53 kernel: Attempt to kill tasklet from interrupt
Jan 1 00:01:56 kernel: Attempt to kill tasklet from interrupt
Jan 1 00:01:58 rc_service: httpd 568:notify_rc start_autodet
Jan 1 00:01:58 rc_service: skip the event: start_autodet.
Jan 1 00:02:06 pppd[761]: pppd 2.4.7 started by admin, uid 0
Jan 1 00:02:06 pppd[761]: Connected to d4:ca:6d:ae:71:53 via interface eth0
Jan 1 00:02:06 pppd[761]: Connect: ppp0 <--> eth0
Jan 1 00:02:09 WAN Connection: Fail to connect with some issues.
Jan 1 00:02:10 pppd[761]: PAP authentication succeeded
Jan 1 00:02:10 pppd[761]: peer from calling number D4:CA:6D:AE:71:53 authorized
Jan 1 00:02:12 pppd[761]: local IP address 103.40.227.35
Jan 1 00:02:12 pppd[761]: remote IP address 103.40.227.1
Jan 1 00:02:12 pppd[761]: primary DNS address 113.21.228.1
Jan 1 00:02:12 pppd[761]: secondary DNS address 8.8.8.8
Jan 1 00:02:12 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 1 00:02:13 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 00:02:13 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 00:02:13 wan: finish adding multi routes
Jan 1 00:02:13 rc_service: ip-up 768:notify_rc stop_upnp
Jan 1 00:02:13 miniupnpd[591]: received signal 15, good-bye
Jan 1 00:02:14 rc_service: ip-up 768:notify_rc start_upnp
Jan 1 00:02:14 WAN Connection: WAN was restored.
Jan 1 00:02:14 miniupnpd[821]: HTTP listening on port 52681
Jan 1 00:02:14 miniupnpd[821]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:02:16 ntp: start NTP update
Jun 2 10:05:24 rc_service: ntp 824:notify_rc restart_upnp
Jun 2 10:05:24 miniupnpd[821]: received signal 15, good-bye
Jun 2 10:05:24 miniupnpd[834]: HTTP listening on port 46732
Jun 2 10:05:24 miniupnpd[834]: Listening for NAT-PMP traffic on port 5351
Jun 2 10:05:25 rc_service: ntp 824:notify_rc restart_diskmon
Jun 2 10:05:26 rc_service: httpd 568:notify_rc start_autodet
Jun 2 10:05:27 disk monitor: be idle
Jun 2 10:06:04 rc_service: httpd 568:notify_rc restart_wan_if 0
Jun 2 10:06:05 pppd[761]: Connection terminated.
Jun 2 10:06:06 kernel: Attempt to kill tasklet from interrupt
Jun 2 10:06:09 crond[570]: time disparity of 219484 minutes detected
Jun 2 10:06:09 rc_service: httpd 568:notify_rc start_autodet
Jun 2 10:06:09 rc_service: skip the event: start_autodet.
Jun 2 10:06:15 pppd[866]: pppd 2.4.7 started by admin, uid 0
Jun 2 10:06:15 pppd[866]: Connected to d4:ca:6d:ae:71:53 via interface eth0
Jun 2 10:06:15 pppd[866]: Connect: ppp0 <--> eth0
Jun 2 10:06:15 pppd[866]: PAP authentication succeeded
Jun 2 10:06:15 pppd[866]: peer from calling number D4:CA:6D:AE:71:53 authorized
Jun 2 10:06:16 pppd[866]: local IP address 103.40.227.35
Jun 2 10:06:16 pppd[866]: remote IP address 103.40.227.1
Jun 2 10:06:16 pppd[866]: primary DNS address 113.21.228.1
Jun 2 10:06:16 pppd[866]: secondary DNS address 8.8.8.8
Jun 2 10:06:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 2 10:06:17 wan: finish adding multi routes
Jun 2 10:06:17 rc_service: ip-up 873:notify_rc stop_upnp
Jun 2 10:06:17 miniupnpd[834]: received signal 15, good-bye
Jun 2 10:06:18 rc_service: ip-up 873:notify_rc start_upnp
Jun 2 10:06:18 miniupnpd[909]: HTTP listening on port 48839
Jun 2 10:06:18 miniupnpd[909]: Listening for NAT-PMP traffic on port 5351
Jun 2 10:06:19 ntp: start NTP update
Jun 2 10:06:34 rc_service: httpd 568:notify_rc restart_wireless
Jun 2 10:06:40 kernel: wl_module_init: passivemode set to 0x0
Jun 2 10:06:40 kernel: wl_module_init: txworkq set to 0x1
Jun 2 10:06:41 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Jun 2 10:06:41 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Jun 2 10:07:02 WAN Connection: Ethernet link down.
Jun 2 10:07:02 stop_nat_rules: apply the redirect_rules!
Jun 2 10:07:08 WAN Connection: WAN was restored.
Jun 2 10:07:08 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 2 10:07:37 miniupnpd[909]: recv (state0): Connection reset by peer
Jun 2 10:07:52 pppd[866]: Serial link appears to be disconnected.
Jun 2 10:07:53 WAN Connection: Fail to connect with some issues.
Jun 2 10:07:53 stop_nat_rules: apply the redirect_rules!
Jun 2 10:07:53 miniupnpd[909]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jun 2 10:07:53 miniupnpd[909]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jun 2 10:07:58 pppd[866]: Connection terminated.
Jun 2 10:07:58 pppd[866]: Modem hangup
Jun 2 10:08:13 pppd[866]: Connected to d4:ca:6d:ae:71:53 via interface eth0
Jun 2 10:08:13 pppd[866]: Connect: ppp0 <--> eth0
Jun 2 10:08:13 pppd[866]: PAP authentication succeeded
Jun 2 10:08:13 pppd[866]: peer from calling number D4:CA:6D:AE:71:53 authorized
Jun 2 10:08:13 pppd[866]: local IP address 103.40.227.35
Jun 2 10:08:13 pppd[866]: remote IP address 103.40.227.1
Jun 2 10:08:13 pppd[866]: primary DNS address 113.21.228.1
Jun 2 10:08:13 pppd[866]: secondary DNS address 8.8.8.8
Jun 2 10:08:13 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 2 10:08:14 wan: finish adding multi routes
Jun 2 10:08:14 rc_service: ip-up 1170:notify_rc stop_upnp
Jun 2 10:08:14 miniupnpd[909]: received signal 15, good-bye
Jun 2 10:08:14 WAN Connection: WAN was restored.
Jun 2 10:08:15 rc_service: ip-up 1170:notify_rc start_upnp
Jun 2 10:08:15 miniupnpd[1206]: HTTP listening on port 46514
Jun 2 10:08:15 miniupnpd[1206]: Listening for NAT-PMP traffic on port 5351
Jun 2 10:08:16 ntp: start NTP update
Jun 2 10:08:29 WAN Connection: Ethernet link down.
Jun 2 10:08:29 stop_nat_rules: apply the redirect_rules!
Jun 2 10:08:39 WAN Connection: WAN was restored.
Jun 2 10:08:39 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 2 10:08:46 ntp: start NTP update
Jun 2 10:08:49 WAN Connection: Ethernet link down.
Jun 2 10:08:49 stop_nat_rules: apply the redirect_rules!
Jun 2 10:08:54 WAN Connection: WAN was restored.
Jun 2 10:08:54 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 2 10:08:56 ntp: start NTP update
Jun 2 10:09:09 WAN Connection: Ethernet link down.
Jun 2 10:09:09 stop_nat_rules: apply the redirect_rules!
Jun 2 10:09:19 WAN Connection: WAN was restored.
Jun 2 10:09:19 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 2 10:09:39 WAN Connection: Ethernet link down.
Jun 2 10:09:39 stop_nat_rules: apply the redirect_rules!
Jun 2 10:09:44 WAN Connection: WAN was restored.
Jun 2 10:09:44 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!

 

[RMerlin]

You have many of these:

Jun 2 10:07:02 WAN Connection: Ethernet link down.

Your modem is either crashing/rebooting, or otherwise disappearing. I'd start by trying another Ethernet cable between the modem and the router, or then to replace the modem.

 

[L&LD]

You may want to power down the modem when switching between routers. This will reset the connection to your ISP and your new router.

I would suggest at least 10 minutes and even 30 minutes or more may be required (depending on how long your ISP would take to recognize the new connection). Good luck.

 

[Zahidur Abedin]

Rmerlin : I tried with a new cable, but it still does the same thing. I am just confused cause it works fine with the old Trendnet router.

L&LD: Should I ask my Isp to reset the connection?

 

[L&LD]

No, all you need to reset the connection is to leave the modem unplugged for some amount of time (depends on the ISP). 10 to 30 minutes is usually sufficient, but I have left modems unplugged for an hour or more and that solved issues for some customers.