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

 找回密码
 立即注册

QQ登录

只需一步,快速开始

手机号码,快捷登录

查看: 23620|回复: 21

[求助] RT-AC68U间歇性断网!

[复制链接]

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
发表于 2018-5-13 01:13:53 | 显示全部楼层 |阅读模式
2月份吧大概发过一贴,这次还是间歇性断网,不过不同的是断开以后会自动连接了。现在差不多每天2次左右断网,猫会亮红灯,过了2分多钟会自动连接上,但是确实很恼火这个问题!固件是官方的,版本 384_20308,拜托了!

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

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
 楼主| 发表于 2018-5-13 01:17:56 | 显示全部楼层
本帖最后由 YULVKK 于 2018-5-13 01:27 编辑

May 12 18:06:09 roamast: eth1: add client [d0:ff:98:af:95:b6] to monitor list
May 12 19:19:17 miniupnpd[583]: recv (state0): Connection reset by peer
May 12 19:27:22 ntp: start NTP update
May 12 22:02:04 roamast: eth1: add client [d0:ff:98:af:95:b6] to monitor list
May 12 23:00:26 disk_monitor: Got SIGALRM...
May 13 00:59:20 WAN Connection: Fail to connect with some issues.
May 13 00:59:21 nat: apply redirect rules
May 13 00:59:25 WAN Connection: Ethernet link down.
May 13 00:59:30 WAN Connection: Ethernet link up.
May 13 00:59:30 rc_service: wanduck 221:notify_rc restart_wan_if 0
May 13 00:59:32 wan: [deconfig] udhcpc done[286]
May 13 00:59:32 kernel: Attempt to kill tasklet from interrupt
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 9 for vlan1 mvlan_en 0
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 2 for vlan1 mvlan_en 0
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 13 for vlan1 mvlan_en 0
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 1 for vlan1 mvlan_en 0
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 13 for vlan2 mvlan_en 0
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 1 for vlan2 mvlan_en 0
May 13 00:59:32 kernel: et0: et_mvlan_netdev_event: event 4 for vlan1 mvlan_en 0
May 13 00:59:35 wan: [deconfig] udhcpc done[286]
May 13 00:59:35 pppd[24658]: pppd 2.4.7 started by Sakura, uid 0
May 13 00:59:35 WAN Connection: Fail to connect with some issues.
May 13 00:59:40 pppd[24658]: Connected to 4c:09:b4:f6:db:10 via interface eth0
May 13 00:59:40 pppd[24658]: Connect: ppp0 <--> eth0
May 13 00:59:40 pppd[24658]: CHAP authentication succeeded
May 13 00:59:40 pppd[24658]: peer from calling number 4C:09:B4:F6B:10 authorized
May 13 00:59:40 pppd[24658]: local  IP address 100.80.144.212
May 13 00:59:40 pppd[24658]: remote IP address 100.80.128.1
May 13 00:59:40 pppd[24658]: primary   DNS address 218.2.2.2
May 13 00:59:40 pppd[24658]: secondary DNS address 218.4.4.4
May 13 00:59:40 rc_service: ip-up 24664:notify_rc start_firewall
May 13 00:59:41 miniupnpd[583]: shutting down MiniUPnPd
May 13 00:59:41 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 13 00:59:41 wan: finish adding multi routes
May 13 00:59:41 rc_service: ip-up 24664:notify_rc stop_upnp
May 13 00:59:41 rc_service: waitting "start_firewall" via ip-up ...
May 13 00:59:42 miniupnpd[24699]: version 1.9 started
May 13 00:59:42 miniupnpd[24699]: HTTP listening on port 41023
May 13 00:59:42 miniupnpd[24699]: Listening for NAT-PMP/PCP traffic on port 5351
May 13 00:59:42 rc_service: ip-up 24664:notify_rc start_upnp
May 13 00:59:42 rc_service: waitting "stop_upnp" via ip-up ...
May 13 00:59:42 miniupnpd[24699]: shutting down MiniUPnPd
May 13 00:59:44 miniupnpd[24703]: version 1.9 started
May 13 00:59:44 miniupnpd[24703]: HTTP listening on port 46022
May 13 00:59:44 miniupnpd[24703]: Listening for NAT-PMP/PCP traffic on port 5351
May 13 00:59:45 WAN Connection: WAN was restored.
May 13 00:59:47 ntp: start NTP update
May 13 00:59:57 rc_service: zcip 24740:notify_rc start_firewall
May 13 00:59:57 zcip client: configured 169.254.46.1
May 13 00:59:57 miniupnpd[24703]: shutting down MiniUPnPd
May 13 00:59:57 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 13 00:59:58 miniupnpd[24759]: version 1.9 started
May 13 00:59:58 miniupnpd[24759]: HTTP listening on port 56422
May 13 00:59:58 miniupnpd[24759]: Listening for NAT-PMP/PCP traffic on port 5351
May 13 01:00:08 rc_service: udhcpc 24763:notify_rc start_firewall
May 13 01:00:08 dhcp client: bound 192.168.1.111 via 192.168.1.1 during 604800 seconds.
May 13 01:00:08 miniupnpd[24759]: shutting down MiniUPnPd
May 13 01:00:08 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 13 01:00:09 miniupnpd[24784]: version 1.9 started
May 13 01:00:09 miniupnpd[24784]: HTTP listening on port 44484
May 13 01:00:09 miniupnpd[24784]: Listening for NAT-PMP/PCP traffic on port 5351

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
 楼主| 发表于 2018-5-13 05:57:18 | 显示全部楼层
May 13 02:51:39 roamast: eth1: add client [90:ad:f7:c3:2e:05] to monitor list
May 13 05:53:56 WAN Connection: Fail to connect with some issues.
May 13 05:53:57 nat: apply redirect rules
May 13 05:54:01 WAN Connection: Ethernet link up.
May 13 05:54:01 rc_service: wanduck 221:notify_rc restart_wan_if 0
May 13 05:54:03 wan: [deconfig] udhcpc done[286]
May 13 05:54:03 kernel: Attempt to kill tasklet from interrupt
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 9 for vlan1 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 2 for vlan1 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 9 for vlan2 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 2 for vlan2 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 13 for vlan1 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 1 for vlan1 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 13 for vlan2 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 1 for vlan2 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 4 for vlan1 mvlan_en 0
May 13 05:54:03 kernel: et0: et_mvlan_netdev_event: event 4 for vlan2 mvlan_en 0
May 13 05:54:06 wan: [deconfig] udhcpc done[286]
May 13 05:54:06 pppd[32136]: pppd 2.4.7 started by Sakura, uid 0
May 13 05:54:11 pppd[32136]: Connected to 08:19:a6:24:0a:58 via interface eth0
May 13 05:54:11 pppd[32136]: Connect: ppp0 <--> eth0
May 13 05:54:14 pppd[32136]: CHAP authentication succeeded
May 13 05:54:14 pppd[32136]: peer from calling number 08:19:A6:24:0A:58 authorized
May 13 05:54:14 pppd[32136]: local  IP address 58.216.98.244
May 13 05:54:14 pppd[32136]: remote IP address 58.216.98.1
May 13 05:54:14 pppd[32136]: primary   DNS address 221.228.255.1
May 13 05:54:14 pppd[32136]: secondary DNS address 218.2.135.1
May 13 05:54:14 rc_service: ip-up 32210:notify_rc start_firewall
May 13 05:54:15 miniupnpd[24784]: shutting down MiniUPnPd
May 13 05:54:15 wan: finish adding multi routes
May 13 05:54:15 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 13 05:54:15 rc_service: ip-up 32210:notify_rc stop_upnp
May 13 05:54:15 rc_service: waitting "start_firewall" via ip-up ...
May 13 05:54:16 miniupnpd[32246]: version 1.9 started
May 13 05:54:16 miniupnpd[32246]: HTTP listening on port 55541
May 13 05:54:16 miniupnpd[32246]: Listening for NAT-PMP/PCP traffic on port 5351
May 13 05:54:16 rc_service: ip-up 32210:notify_rc start_upnp
May 13 05:54:16 rc_service: waitting "stop_upnp" via ip-up ...
May 13 05:54:16 miniupnpd[32246]: shutting down MiniUPnPd
May 13 05:54:16 WAN Connection: WAN was restored.
May 13 05:54:17 miniupnpd[32254]: version 1.9 started
May 13 05:54:18 miniupnpd[32254]: HTTP listening on port 51876
May 13 05:54:18 miniupnpd[32254]: Listening for NAT-PMP/PCP traffic on port 5351
May 13 05:54:18 ntp: start NTP update
May 13 05:54:28 rc_service: zcip 32285:notify_rc start_firewall
May 13 05:54:28 zcip client: configured 169.254.46.1
May 13 05:54:29 miniupnpd[32254]: shutting down MiniUPnPd
May 13 05:54:29 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 13 05:54:29 miniupnpd[32305]: version 1.9 started
May 13 05:54:29 miniupnpd[32305]: HTTP listening on port 39709
May 13 05:54:29 miniupnpd[32305]: Listening for NAT-PMP/PCP traffic on port 5351
May 13 05:54:39 rc_service: udhcpc 32309:notify_rc start_firewall
May 13 05:54:39 dhcp client: bound 192.168.1.111 via 192.168.1.1 during 604800 seconds.
May 13 05:54:40 miniupnpd[32305]: shutting down MiniUPnPd
May 13 05:54:40 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 13 05:54:40 miniupnpd[32330]: version 1.9 started
May 13 05:54:40 miniupnpd[32330]: HTTP listening on port 41153
May 13 05:54:40 miniupnpd[32330]: Listening for NAT-PMP/PCP traffic on port 5351

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
 楼主| 发表于 2018-5-13 06:00:22 | 显示全部楼层
0点左右断了一次自动连接了,早晨5:50左右又断了一次自动连接了......心累啊! 是路由器质量问题吗?还是猫的问题?

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
 楼主| 发表于 2018-5-13 17:45:39 | 显示全部楼层
@Dr.Antenna @zfwaitingforyou @Master 大佬们又是我,问题好像还没有解决!

16

主题

495

回帖

1283

积分

金牌会员

Rank: 6Rank: 6

积分
1283

GT-AC5300

发表于 2018-5-14 09:14:06 | 显示全部楼层
猫亮红灯,是不是猫自己也断网了。
你可以把电脑直接接在猫上看会不会也断网

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
 楼主| 发表于 2018-5-14 09:16:31 | 显示全部楼层
本帖最后由 YULVKK 于 2018-5-14 09:27 编辑
maple_1994 发表于 2018-5-14 09:14
猫亮红灯,是不是猫自己也断网了。
你可以把电脑直接接在猫上看会不会也断网 ...

日志在上面,帮忙看下吧。猫应该断了,亮红灯了。其实2月份我发过一贴,当时的情况是猫和路由器灯都正常亮着,2-3天断一次,但是不会自动重连,必须重启猫或者路由器。 最近是一天断2-3次,猫亮红灯,但是会自动重连,2分多钟重连上。

2

主题

20

回帖

47

积分

新手上路

Rank: 1

积分
47
 楼主| 发表于 2018-5-14 09:18:54 | 显示全部楼层
maple_1994 发表于 2018-5-14 09:14
猫亮红灯,是不是猫自己也断网了。
你可以把电脑直接接在猫上看会不会也断网 ...

我不是很懂,这个日志能说明什么吗? 应该不会泄露什么隐私吧?

16

主题

495

回帖

1283

积分

金牌会员

Rank: 6Rank: 6

积分
1283

GT-AC5300

发表于 2018-5-14 09:29:52 | 显示全部楼层
YULVKK 发表于 2018-5-14 09:18
我不是很懂,这个日志能说明什么吗? 应该不会泄露什么隐私吧?

不会泄露隐私,请放心吧
你的Log和运营商更换自动IP时产生的log很像。
WAN Connection: Ethernet link down.
WAN Connection: Ethernet link up.
说明你路由器的wan 口确实有断线过
感觉是猫或者运营商的问题的可能性更大

261

主题

3832

回帖

9567

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
9567

RT-AX86U

发表于 2018-5-14 10:10:45 | 显示全部楼层
你直接接到你猫上使用能正常吗?
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

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

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

秒后自动关闭

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

GMT+8, 2025-4-23 06:01 , Processed in 3.274677 second(s), 34 queries , Gzip On.

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

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