RT-AC1750_B1用386版本固件，PPPoE拨号会频繁断网

タツ · 发表于 2022-1-21 19:18:50

现象：北京联通，光猫桥接，使用路由器拨号，每隔十几分钟左右，便会断网，且不会自动恢复，需要手动去webui重新拨号；然后过十几分钟又会断网，循环往复。非偶发，必然出现。

为了排查问题，也看了论坛里许多帖子，做了如下尝试：
尝试1：使用光猫拨号，可数天不断网（之前一直用的状态）。光猫桥接、路由器设置AP模式，使用PC拨号，也可以很长时间不断网。基本判断是路由器的问题。

尝试2：刷固件，换改版梅林、官方固件，并且双清，重新拨号，该现象仍然会发生。

尝试3：关闭路由器的IPV6，无效果。

尝试4：将WAN连接中的“网络监测”设置为关闭、PPP Echo、DNS Probe，都无效果。

尝试5：将系统设置里的“网络监控”的DNS查询、Ping全勾上或取消，都无效果。

尝试6：将系统设置里的“自动注销”设置成0或30，都无效果。
尝试7：从386最新版本的固件刷回384、385版本，都可以很长时间不掉线。现在感觉基本可以认为386固件有BUG。但是很奇怪如果是这么严重的BUG为什么没看到太多人有跟我一样的问题。

想请问下坛里的大佬们是否遇到过类似的问题，有什么解决方案，或者排查思路。感激不尽！
另外如果真的是386固件bug，找官方反馈是否能够得到修复呢

附件是比较干净一个复现log，我在清除历史log后进行操作，从联网到断网的过程（前面日期跳到5月5号也很迷惑，其实这段都是同一个时间段的记录）

更新：
换到386.1的梅林后，捕获到了之前没看到过的log：

Jan 22 22:34:23 pppd[563]: LCP terminated by peer
Jan 22 22:34:23 pppd[563]: Connect time 24.2 minutes.
Jan 22 22:34:23 pppd[563]: Sent 9494761 bytes, received 33103428 bytes.
Jan 22 22:34:23 lldpd[352]: removal request for address of 123.116.112.1%11, but no knowledge of it
Jan 22 22:34:23 dnsmasq[830]: read /etc/hosts - 6 addresses
Jan 22 22:34:23 dnsmasq[830]: using nameserver 192.168.1.1#53
Jan 22 22:34:26 pppd[563]: Connection terminated.
Jan 22 22:34:26 pppd[563]: Sent PADT
Jan 22 22:34:26 pppd[563]: Modem hangup

看起来是被ISP踢下线了？386.1被踢下线后看起来自动重拨能重新连上，但是更新的固件重播以后还是中断，目前看来是这个原因。
至于被踢下线这件事情，不知道大家有没有解决方法。

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

タツ · 发表于 2022-1-21 19:20:31

附上一个比较干净的复现log（另外对于Log里的时间会偶尔跳到5月5号，也很没有头绪，这些log都是在我清除历史log后进行操作留下的，都是17:29左右打的log）：

May 5 13:06:10 rc_service: httpd 731:notify_rc restart_wan_if 0;restart_stubby
May 5 13:06:13 pppd[1129]: pppd 2.4.7 started by archer, uid 0
May 5 13:06:13 pppd[1129]: Connected to d8:49:0b:b6:8c:b9 via interface eth0
May 5 13:06:13 pppd[1129]: Connect: ppp0 <--> eth0
May 5 13:06:23 pppd[1129]: PAP authentication succeeded
May 5 13:06:23 pppd[1129]: peer from calling number D8:49:0B:B6:8C:B9 authorized
May 5 13:06:23 pppd[1129]: local IP address 123.116.126.122
May 5 13:06:23 pppd[1129]: remote IP address 123.116.112.1
May 5 13:06:23 pppd[1129]: primary DNS address 202.106.46.151
May 5 13:06:23 pppd[1129]: secondary DNS address 202.106.195.68
May 5 13:06:24 kernel: nf_conntrack_rtsp v0.6.21 loading
May 5 13:06:25 kernel: nf_nat_rtsp v0.6.21 loading
May 5 13:06:25 wan: finish adding multi routes
May 5 13:06:25 miniupnpd[793]: shutting down MiniUPnPd
May 5 13:06:25 zcip client: configured 169.254.201.100
May 5 13:06:25 syslog: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
May 5 13:06:25 miniupnpd[1231]: HTTP listening on port 41575
May 5 13:06:26 miniupnpd[1231]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 13:06:28 WAN Connection: WAN was restored.
May 5 13:06:28 ntp: start NTP update
Jan 21 17:29:52 rc_service: ntp 1222:notify_rc restart_diskmon
Jan 21 17:29:52 disk_monitor: Finish
Jan 21 17:29:58 disk monitor: be idle
Jan 21 17:30:23 crond[730]: time disparity of 1954344 minutes detected
Jan 21 17:31:34 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7396)]periodic_check AM 4:43
Jan 21 17:31:34 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7435)]do webs_update
Jan 21 17:31:36 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7453)]retrieve firmware information
Jan 21 17:31:36 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7456)]user in use
Jan 21 17:31:52 ahs: [read_json]Update ahs JSON file.
Jan 21 17:32:05 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7435)]do webs_update
Jan 21 17:32:05 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7453)]retrieve firmware information
Jan 21 17:32:05 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7456)]user in use
Jan 21 17:32:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7435)]do webs_update
Jan 21 17:32:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7453)]retrieve firmware information
Jan 21 17:32:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7456)]user in use
Jan 21 17:43:35 acsd: selected channel spec: 0x1004 (4)
Jan 21 17:43:35 acsd: Adjusted channel spec: 0x1004 (4)
Jan 21 17:43:35 acsd: selected channel spec: 0x1004 (4)
Jan 21 17:43:35 acsd: acs_set_chspec: 0x1004 (4) for reason APCS_CSTIMER
Jan 21 17:43:36 acsd: selected channel spec: 0xe19b (153/80)
Jan 21 17:43:36 acsd: Adjusted channel spec: 0xe19b (153/80)
Jan 21 17:43:36 acsd: selected channel spec: 0xe19b (153/80)
Jan 21 17:43:36 acsd: acs_set_chspec: 0xe19b (153/80) for reason APCS_CSTIMER
Jan 21 17:55:37 DualWAN: skip single wan wan_led_control - WANRED off
Jan 21 17:55:40 pppd[1129]: Connection terminated.
Jan 21 17:55:40 pppd[1129]: Modem hangup
Jan 21 17:55:42 WAN Connection: Fail to connect with some issues.
Jan 21 17:55:50 pppd[1129]: Connected to d8:49:0b:b6:8c:b9 via interface eth0
Jan 21 17:55:50 pppd[1129]: Connect: ppp0 <--> eth0
Jan 21 17:56:01 pppd[1129]: PAP authentication succeeded
Jan 21 17:56:01 pppd[1129]: peer from calling number D8:49:0B:B6:8C:B9 authorized
Jan 21 17:56:01 pppd[1129]: local IP address 123.116.126.126
Jan 21 17:56:01 pppd[1129]: remote IP address 123.116.112.1
Jan 21 17:56:01 pppd[1129]: primary DNS address 202.106.46.151
Jan 21 17:56:01 pppd[1129]: secondary DNS address 202.106.195.68
Jan 21 17:56:01 wan: finish adding multi routes
Jan 21 17:56:01 miniupnpd[1231]: shutting down MiniUPnPd
Jan 21 17:56:02 syslog: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Jan 21 17:56:02 miniupnpd[4674]: HTTP listening on port 49300
Jan 21 17:56:02 WAN Connection: WAN was restored.
Jan 21 17:56:02 miniupnpd[4674]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 21 17:58:39 acsd: selected channel spec: 0x100b (11)
Jan 21 17:58:39 acsd: Adjusted channel spec: 0x100b (11)
Jan 21 17:58:39 acsd: selected channel spec: 0x100b (11)
Jan 21 17:58:39 acsd: acs_set_chspec: 0x100b (11) for reason APCS_CSTIMER
Jan 21 17:58:41 acsd: selected channel spec: 0xe29b (157/80)
Jan 21 17:58:41 acsd: Adjusted channel spec: 0xe29b (157/80)
Jan 21 17:58:41 acsd: selected channel spec: 0xe29b (157/80)
Jan 21 17:58:41 acsd: acs_set_chspec: 0xe29b (157/80) for reason APCS_CSTIMER