华硕网络产品技术交流平台

 找回密码
 立即注册

QQ登录

只需一步,快速开始

手机号码,快捷登录

查看: 29387|回复: 14

[求助] RT-AC66U B1定时断网问题

[复制链接]

1

主题

8

回帖

36

积分

新手上路

Rank: 1

积分
36
发表于 2017-1-23 20:39:19 | 显示全部楼层 |阅读模式
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[694]: shutting down MiniUPnPd
Jan 19 21:51:34 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jan 19 21:51:34 miniupnpd[712]: version 1.9 started
Jan 19 21:51:34 miniupnpd[712]: HTTP listening on port 53037
Jan 19 21:51:34 miniupnpd[712]: 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[712]: 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[808]: version 1.9 started
Jan 19 21:51:42 miniupnpd[808]: HTTP listening on port 39816
Jan 19 21:51:42 miniupnpd[808]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:04 crond[429]: 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[808]: shutting down MiniUPnPd
Jan 19 21:52:14 pppd[477]: 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[949]: pppd 2.4.7 started by admin, uid 0
Jan 19 21:52:20 pppd[949]: Connected to 54:39:df:d4:be:cc via interface eth0
Jan 19 21:52:20 pppd[949]: 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[949]: PAP authentication succeeded
Jan 19 21:52:24 pppd[949]: peer from calling number 54:39F4:BE:CC authorized
Jan 19 21:52:24 pppd[949]: local  IP address  ****************
Jan 19 21:52:24 pppd[949]: remote IP address ****************
Jan 19 21:52:24 pppd[949]: primary   DNS address ****************
Jan 19 21:52:24 pppd[949]: 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[978]: version 1.9 started
Jan 19 21:52:26 miniupnpd[978]: HTTP listening on port 39030
Jan 19 21:52:26 miniupnpd[978]: 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[978]: 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[1035]: version 1.9 started
Jan 19 21:52:29 miniupnpd[1035]: HTTP listening on port 33338
Jan 19 21:52:29 miniupnpd[1035]: 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[1035]: 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[1043]: version 1.9 started
Jan 19 21:52:31 miniupnpd[1043]: HTTP listening on port 47552
Jan 19 21:52:31 miniupnpd[1043]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 19 21:52:31 miniupnpd[1043]: 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[1075]: version 1.9 started
Jan 19 21:52:33 miniupnpd[1075]: HTTP listening on port 41393
Jan 19 21:52:33 miniupnpd[1075]: 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[1075]: 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[1131]: version 1.9 started
Jan 19 21:52:38 miniupnpd[1131]: HTTP listening on port 43535
Jan 19 21:52:38 miniupnpd[1131]: 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[949]: Connection terminated.
Jan 21 09:52:26 pppd[949]: 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[949]: Connected to 54:39:df:d4:be:cc via interface eth0
Jan 21 09:52:36 pppd[949]: Connect: ppp0 <--> eth0
Jan 21 09:52:39 pppd[949]: PAP authentication succeeded
Jan 21 09:52:39 pppd[949]: peer from calling number 54:39F4:BE:CC authorized
Jan 21 09:52:39 pppd[949]: local  IP address ****************
Jan 21 09:52:39 pppd[949]: remote IP address ****************
Jan 21 09:52:39 pppd[949]: primary   DNS address ****************
Jan 21 09:52:39 pppd[949]: secondary DNS address ****************
Jan 21 09:52:39 rc_service: ip-up 1558:notify_rc start_firewall
Jan 21 09:52:40 miniupnpd[1131]: 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[1592]: version 1.9 started
Jan 21 09:52:41 miniupnpd[1592]: HTTP listening on port 33229
Jan 21 09:52:41 miniupnpd[1592]: 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[1592]: shutting down MiniUPnPd
Jan 21 09:52:42 ntp: start NTP update
Jan 21 09:52:43 miniupnpd[1596]: version 1.9 started
Jan 21 09:52:43 miniupnpd[1596]: HTTP listening on port 54966
Jan 21 09:52:43 miniupnpd[1596]: 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[1596]: 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[1666]: version 1.9 started
Jan 21 09:52:48 miniupnpd[1666]: HTTP listening on port 57246
Jan 21 09:52:48 miniupnpd[1666]: 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=[wan], wan1=[none]
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[949]: Connection terminated.
Jan 22 21:52:42 pppd[949]: 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[949]: Connected to 54:39:df:d4:be:cc via interface eth0
Jan 22 21:52:52 pppd[949]: Connect: ppp0 <--> eth0
Jan 22 21:52:56 pppd[949]: PAP authentication succeeded
Jan 22 21:52:56 pppd[949]: peer from calling number 54:39F4:BE:CC authorized
Jan 22 21:52:56 pppd[949]: local  IP address ****************
Jan 22 21:52:56 pppd[949]: remote IP address ****************
Jan 22 21:52:56 pppd[949]: primary   DNS address ****************
Jan 22 21:52:56 pppd[949]: secondary DNS address ****************
Jan 22 21:52:56 rc_service: ip-up 2052:notify_rc start_firewall
Jan 22 21:52:56 miniupnpd[1666]: 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[2087]: version 1.9 started
Jan 22 21:52:57 miniupnpd[2087]: HTTP listening on port 40776
Jan 22 21:52:57 miniupnpd[2087]: 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[2087]: 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[2093]: version 1.9 started
Jan 22 21:52:59 miniupnpd[2093]: HTTP listening on port 57250
Jan 22 21:52:59 miniupnpd[2093]: 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[2093]: 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[2160]: version 1.9 started
Jan 22 21:53:04 miniupnpd[2160]: HTTP listening on port 46443
Jan 22 21:53:04 miniupnpd[2160]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 23 09:52:59 ntp: start NTP update
(系统记录中的本地IP和远程IP被我用*号替代了)


微信扫一扫,阅读更方便^_^

639

主题

6305

回帖

1万

积分

管理员

正品行货

Rank: 9Rank: 9Rank: 9

积分
17269

RT-AC88URT-AX68U

发表于 2017-1-24 08:21:55 | 显示全部楼层
pppd[949]: Connection terminated.
pppd[949]: Modem hangup
WAN Connection: Fail to connect with some issues.
-- 有些ISP会隔一段时间,主动把PPP链接断开的,然后你的路由器必须重新发送一次连接请求。

256

主题

3734

回帖

9243

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
9243

RT-AX86U

发表于 2017-1-24 10:38:34 | 显示全部楼层
固定时间重连,那就是你的运营商主动的事了,你这时候会出现断网现象吗?
一般这时候重新发IP是无感的,不会出现明显的断线现象.log只是表示重新去要IP了
Using wireless to connect to life

1

主题

8

回帖

36

积分

新手上路

Rank: 1

积分
36
 楼主| 发表于 2017-1-24 18:46:30 | 显示全部楼层
Master 发表于 2017-1-24 08:21
pppd[949]: Connection terminated.
pppd[949]: Modem hangup
WAN Connection: Fail to connect with some  ...

嗯,我家里用的联通,感觉36小时就主动断开有点坑,到时打个电话给ISP确认下。

1

主题

8

回帖

36

积分

新手上路

Rank: 1

积分
36
 楼主| 发表于 2017-1-24 18:54:28 | 显示全部楼层
zfwaitingforyou 发表于 2017-1-24 10:38
固定时间重连,那就是你的运营商主动的事了,你这时候会出现断网现象吗?
一般这时候重新发IP是无感的,不会出 ...

还是有感觉的,偶尔刚好遇到断开的时候我在玩网游,会提示游戏断开正在重连。

1

主题

8

回帖

36

积分

新手上路

Rank: 1

积分
36
 楼主| 发表于 2017-2-3 11:31:06 | 显示全部楼层
zfwaitingforyou 发表于 2017-1-24 10:38
固定时间重连,那就是你的运营商主动的事了,你这时候会出现断网现象吗?
一般这时候重新发IP是无感的,不会出 ...

有个问题还得请教下版主,最近把路由换回老的TP-LINK,发现还是一样隔一段时间就会断网重连,然后IP也随之改变。后来发现ISP给我的是内网IP,打给客服反映情况,客服说只要不连路由就没这问题……想问下是否换公网IP就不会出现这问题?

1

主题

8

回帖

36

积分

新手上路

Rank: 1

积分
36
 楼主| 发表于 2017-2-3 11:39:56 | 显示全部楼层
Master 发表于 2017-1-24 08:21
pppd[949]: Connection terminated.
pppd[949]: Modem hangup
WAN Connection: Fail to connect with some  ...

有个问题还得请教下管理员,最近把路由换回老的TP-LINK,发现还是一样隔一段时间就会断网重连,然后IP也随之改变。后来发现ISP给我的是内网IP,打给客服反映情况,客服说只要不连路由就没这问题……想问下是否换公网IP就不会出现这问题?

639

主题

6305

回帖

1万

积分

管理员

正品行货

Rank: 9Rank: 9Rank: 9

积分
17269

RT-AC88URT-AX68U

发表于 2017-2-6 10:24:40 | 显示全部楼层
Shinn 发表于 2017-2-3 11:39
有个问题还得请教下管理员,最近把路由换回老的TP-LINK,发现还是一样隔一段时间就会断网重连,然后IP也 ...

不是的,根据你的描述,断网重连,是ISP Server端控制的,和内外网IP没关系。

1

主题

8

回帖

36

积分

新手上路

Rank: 1

积分
36
 楼主| 发表于 2017-2-6 20:50:24 | 显示全部楼层
Master 发表于 2017-2-6 10:24
不是的,根据你的描述,断网重连,是ISP Server端控制的,和内外网IP没关系。 ...

好的,谢谢

256

主题

3734

回帖

9243

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
9243

RT-AX86U

发表于 2017-2-7 13:51:28 | 显示全部楼层
Shinn 发表于 2017-2-3 11:39
有个问题还得请教下管理员,最近把路由换回老的TP-LINK,发现还是一样隔一段时间就会断网重连,然后IP也 ...

看来就是ISP在作怪了 定期给你断线 你可以投诉他
Using wireless to connect to life
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

站长推荐上一条 /1 下一条

快速回复 返回列表 搜索 官方QQ群
×

秒后自动关闭

小黑屋|手机版|Archiver|华硕网络产品技术交流平台 ( 苏ICP备16010857号-1 )苏公网安备 32050502000499号

GMT+8, 2024-10-7 09:16 , Processed in 0.044174 second(s), 31 queries .

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

快速回复 返回顶部 返回列表