RT-AC66U B1定时断网问题
1月初从某东入手了个RT-AC66U B1，用了一段时间后发现偶尔会自动断网重连，后来观察一段时间发现每36小时断一次，求大神看下路由器的系统记录，具体是路由器设置问题还是ISP的问题~固件版本是官方最新的3.0.0.4.380_4164。1月19日~1月23日的系统记录：
Jan 19 21:51:34 rc_service: ntp 693:notify_rc restart_upnp
Jan 19 21:51:34 miniupnpd: shutting down MiniUPnPd
Jan 19 21:51:34 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jan 19 21:51:34 miniupnpd: version 1.9 started
Jan 19 21:51:34 miniupnpd: HTTP listening on port 53037
Jan 19 21:51:34 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:51:35 rc_service: ntp 693:notify_rc restart_diskmon
Jan 19 21:51:35 disk_monitor: Finish
Jan 19 21:51:36 kernel: sizeof forward param = 160
Jan 19 21:51:37 disk monitor: be idle
Jan 19 21:51:40 rc_service: ip-up 542:notify_rc start_firewall
Jan 19 21:51:41 miniupnpd: shutting down MiniUPnPd
Jan 19 21:51:41 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 19 21:51:42 miniupnpd: version 1.9 started
Jan 19 21:51:42 miniupnpd: HTTP listening on port 39816
Jan 19 21:51:42 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:04 crond: time disparity of 774111 minutes detected
Jan 19 21:52:09 rc_service: httpd 427:notify_rc restart_net_and_phy
Jan 19 21:52:11 iTunes: daemon is stoped
Jan 19 21:52:11 FTP Server: daemon is stoped
Jan 19 21:52:12 Samba Server: smb daemon is stoped
Jan 19 21:52:12 kernel: gro disabled
Jan 19 21:52:13 miniupnpd: shutting down MiniUPnPd
Jan 19 21:52:14 pppd: Connection terminated.
Jan 19 21:52:15 kernel: Attempt to kill tasklet from interrupt
Jan 19 21:52:17 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 19 21:52:20 kernel: wl_module_init: passivemode set to 0x0
Jan 19 21:52:20 kernel: wl_module_init: igs set to 0x0
Jan 19 21:52:20 kernel: wl_module_init: txworkq set to 0x0
Jan 19 21:52:20 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Jan 19 21:52:20 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Jan 19 21:52:20 stop_nat_rules: apply the redirect_rules!
Jan 19 21:52:20 pppd: pppd 2.4.7 started by admin, uid 0
Jan 19 21:52:20 pppd: Connected to 54:39:df:d4:be:cc via interface eth0
Jan 19 21:52:20 pppd: Connect: ppp0 <--> eth0
Jan 19 21:52:21 rc_service: udhcpc 959:notify_rc start_firewall
Jan 19 21:52:21 rc_service: waitting "restart_net_and_phy" via...
Jan 19 21:52:22 watchdog: restart httpd
Jan 19 21:52:22 rc_service: watchdog 432:notify_rc stop_httpd
Jan 19 21:52:22 rc_service: waitting "restart_net_and_phy" via...
Jan 19 21:52:24 pppd: PAP authentication succeeded
Jan 19 21:52:24 pppd: peer from calling number 54:39:DF:D4:BE:CC authorized
Jan 19 21:52:24 pppd: localIP address****************
Jan 19 21:52:24 pppd: remote IP address ****************
Jan 19 21:52:24 pppd: primary DNS address ****************
Jan 19 21:52:24 pppd: secondary DNS address ****************
Jan 19 21:52:24 rc_service: ip-up 966:notify_rc start_firewall
Jan 19 21:52:24 rc_service: waitting "restart_net_and_phy" via...
Jan 19 21:52:25 RT-AC66U_B1: start httpd - SSL
Jan 19 21:52:25 RT-AC66U_B1: start httpd
Jan 19 21:52:26 miniupnpd: version 1.9 started
Jan 19 21:52:26 miniupnpd: HTTP listening on port 39030
Jan 19 21:52:26 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:28 rc_service: watchdog 432:notify_rc start_httpd
Jan 19 21:52:28 rc_service: waitting "start_firewall" via ip-up ...
Jan 19 21:52:28 miniupnpd: shutting down MiniUPnPd
Jan 19 21:52:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 19 21:52:28 wan: finish adding multi routes
Jan 19 21:52:29 rc_service: ip-up 966:notify_rc stop_upnp
Jan 19 21:52:29 rc_service: waitting "start_firewall" via ip-up ...
Jan 19 21:52:29 miniupnpd: version 1.9 started
Jan 19 21:52:29 miniupnpd: HTTP listening on port 33338
Jan 19 21:52:29 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:30 rc_service: ip-up 966:notify_rc start_upnp
Jan 19 21:52:30 rc_service: waitting "stop_upnp" via ip-up ...
Jan 19 21:52:30 miniupnpd: shutting down MiniUPnPd
Jan 19 21:52:30 RT-AC66U_B1: start httpd - SSL
Jan 19 21:52:30 RT-AC66U_B1: start httpd
Jan 19 21:52:31 dhcp client: bound 192.168.1.2 via 192.168.1.1 during 86400 seconds.
Jan 19 21:52:31 miniupnpd: version 1.9 started
Jan 19 21:52:31 miniupnpd: HTTP listening on port 47552
Jan 19 21:52:31 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:31 miniupnpd: shutting down MiniUPnPd
Jan 19 21:52:31 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 19 21:52:33 miniupnpd: version 1.9 started
Jan 19 21:52:33 miniupnpd: HTTP listening on port 41393
Jan 19 21:52:33 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:36 WAN Connection: WAN was restored.
Jan 19 21:52:37 ntp: start NTP update
Jan 19 21:52:37 rc_service: ip-up 966:notify_rc start_firewall
Jan 19 21:52:38 miniupnpd: shutting down MiniUPnPd
Jan 19 21:52:38 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 19 21:52:38 miniupnpd: version 1.9 started
Jan 19 21:52:38 miniupnpd: HTTP listening on port 43535
Jan 19 21:52:38 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 22:00:37 disk_monitor: Got SIGALRM...
Jan 19 23:00:37 disk_monitor: Got SIGALRM...
Jan 20 09:52:35 ntp: start NTP update
Jan 20 21:52:35 ntp: start NTP update
Jan 21 09:52:26 pppd: Connection terminated.
Jan 21 09:52:26 pppd: Modem hangup
Jan 21 09:52:27 WAN Connection: Fail to connect with some issues.
Jan 21 09:52:27 DualWAN: skip single wan wan_led_control - WANRED off
Jan 21 09:52:27 stop_nat_rules: apply the redirect_rules!
Jan 21 09:52:32 ntp: start NTP update
Jan 21 09:52:36 pppd: Connected to 54:39:df:d4:be:cc via interface eth0
Jan 21 09:52:36 pppd: Connect: ppp0 <--> eth0
Jan 21 09:52:39 pppd: PAP authentication succeeded
Jan 21 09:52:39 pppd: peer from calling number 54:39:DF:D4:BE:CC authorized
Jan 21 09:52:39 pppd: localIP address ****************
Jan 21 09:52:39 pppd: remote IP address ****************
Jan 21 09:52:39 pppd: primary DNS address ****************
Jan 21 09:52:39 pppd: secondary DNS address ****************
Jan 21 09:52:39 rc_service: ip-up 1558:notify_rc start_firewall
Jan 21 09:52:40 miniupnpd: shutting down MiniUPnPd
Jan 21 09:52:40 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 21 09:52:40 wan: finish adding multi routes
Jan 21 09:52:40 rc_service: ip-up 1558:notify_rc stop_upnp
Jan 21 09:52:40 rc_service: waitting "start_firewall" via ip-up ...
Jan 21 09:52:41 miniupnpd: version 1.9 started
Jan 21 09:52:41 miniupnpd: HTTP listening on port 33229
Jan 21 09:52:41 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 21 09:52:41 rc_service: ip-up 1558:notify_rc start_upnp
Jan 21 09:52:41 rc_service: waitting "stop_upnp" via ip-up ...
Jan 21 09:52:41 miniupnpd: shutting down MiniUPnPd
Jan 21 09:52:42 ntp: start NTP update
Jan 21 09:52:43 miniupnpd: version 1.9 started
Jan 21 09:52:43 miniupnpd: HTTP listening on port 54966
Jan 21 09:52:43 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 21 09:52:43 WAN Connection: WAN was restored.
Jan 21 09:52:47 rc_service: ip-up 1558:notify_rc start_firewall
Jan 21 09:52:47 miniupnpd: shutting down MiniUPnPd
Jan 21 09:52:47 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 21 09:52:48 miniupnpd: version 1.9 started
Jan 21 09:52:48 miniupnpd: HTTP listening on port 57246
Jan 21 09:52:48 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 21 12:14:48 rc_service: httpd 1037:notify_rc restart_sendmail
Jan 21 12:14:52 feedback: wan0=, wan1=
Jan 21 21:52:41 ntp: start NTP update
Jan 22 09:52:41 ntp: start NTP update
Jan 22 21:52:38 ntp: start NTP update
Jan 22 21:52:42 pppd: Connection terminated.
Jan 22 21:52:42 pppd: Modem hangup
Jan 22 21:52:43 WAN Connection: Fail to connect with some issues.
Jan 22 21:52:43 DualWAN: skip single wan wan_led_control - WANRED off
Jan 22 21:52:43 stop_nat_rules: apply the redirect_rules!
Jan 22 21:52:52 pppd: Connected to 54:39:df:d4:be:cc via interface eth0
Jan 22 21:52:52 pppd: Connect: ppp0 <--> eth0
Jan 22 21:52:56 pppd: PAP authentication succeeded
Jan 22 21:52:56 pppd: peer from calling number 54:39:DF:D4:BE:CC authorized
Jan 22 21:52:56 pppd: localIP address ****************
Jan 22 21:52:56 pppd: remote IP address ****************
Jan 22 21:52:56 pppd: primary DNS address ****************
Jan 22 21:52:56 pppd: secondary DNS address ****************
Jan 22 21:52:56 rc_service: ip-up 2052:notify_rc start_firewall
Jan 22 21:52:56 miniupnpd: shutting down MiniUPnPd
Jan 22 21:52:56 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 22 21:52:57 wan: finish adding multi routes
Jan 22 21:52:57 rc_service: ip-up 2052:notify_rc stop_upnp
Jan 22 21:52:57 rc_service: waitting "start_firewall" via ip-up ...
Jan 22 21:52:57 miniupnpd: version 1.9 started
Jan 22 21:52:57 miniupnpd: HTTP listening on port 40776
Jan 22 21:52:57 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 22 21:52:58 rc_service: ip-up 2052:notify_rc start_upnp
Jan 22 21:52:58 rc_service: waitting "stop_upnp" via ip-up ...
Jan 22 21:52:58 miniupnpd: shutting down MiniUPnPd
Jan 22 21:52:59 ntp: start NTP update
Jan 22 21:52:59 WAN Connection: WAN was restored.
Jan 22 21:52:59 miniupnpd: version 1.9 started
Jan 22 21:52:59 miniupnpd: HTTP listening on port 57250
Jan 22 21:52:59 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 22 21:53:03 rc_service: ip-up 2052:notify_rc start_firewall
Jan 22 21:53:04 miniupnpd: shutting down MiniUPnPd
Jan 22 21:53:04 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 22 21:53:04 miniupnpd: version 1.9 started
Jan 22 21:53:04 miniupnpd: HTTP listening on port 46443
Jan 22 21:53:04 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jan 23 09:52:59 ntp: start NTP update
（系统记录中的本地IP和远程IP被我用*号替代了）
pppd: Connection terminated.
pppd: Modem hangup
WAN Connection: Fail to connect with some issues.
-- 有些ISP会隔一段时间，主动把PPP链接断开的，然后你的路由器必须重新发送一次连接请求。
固定时间重连,那就是你的运营商主动的事了,你这时候会出现断网现象吗?
一般这时候重新发IP是无感的,不会出现明显的断线现象.log只是表示重新去要IP了 Master 发表于 2017-1-24 08:21
pppd: Connection terminated.
pppd: Modem hangup
WAN Connection: Fail to connect with some...
嗯，我家里用的联通，感觉36小时就主动断开有点坑，到时打个电话给ISP确认下。 zfwaitingforyou 发表于 2017-1-24 10:38
固定时间重连,那就是你的运营商主动的事了,你这时候会出现断网现象吗?
一般这时候重新发IP是无感的,不会出 ...
还是有感觉的，偶尔刚好遇到断开的时候我在玩网游，会提示游戏断开正在重连。 zfwaitingforyou 发表于 2017-1-24 10:38
固定时间重连,那就是你的运营商主动的事了,你这时候会出现断网现象吗?
一般这时候重新发IP是无感的,不会出 ...
有个问题还得请教下版主，最近把路由换回老的TP-LINK，发现还是一样隔一段时间就会断网重连，然后IP也随之改变。后来发现ISP给我的是内网IP，打给客服反映情况，客服说只要不连路由就没这问题……想问下是否换公网IP就不会出现这问题？ Master 发表于 2017-1-24 08:21
pppd: Connection terminated.
pppd: Modem hangup
WAN Connection: Fail to connect with some...
有个问题还得请教下管理员，最近把路由换回老的TP-LINK，发现还是一样隔一段时间就会断网重连，然后IP也随之改变。后来发现ISP给我的是内网IP，打给客服反映情况，客服说只要不连路由就没这问题……想问下是否换公网IP就不会出现这问题？ Shinn 发表于 2017-2-3 11:39
有个问题还得请教下管理员，最近把路由换回老的TP-LINK，发现还是一样隔一段时间就会断网重连，然后IP也 ...
不是的，根据你的描述，断网重连，是ISP Server端控制的，和内外网IP没关系。 Master 发表于 2017-2-6 10:24
不是的，根据你的描述，断网重连，是ISP Server端控制的，和内外网IP没关系。 ...
好的，谢谢 {:2_27:} Shinn 发表于 2017-2-3 11:39
有个问题还得请教下管理员，最近把路由换回老的TP-LINK，发现还是一样隔一段时间就会断网重连，然后IP也 ...
看来就是ISP在作怪了 定期给你断线 你可以投诉他
页:
[1]
2