MT2500偶尔断流
目前是MT2500接光猫,小米AX6000接MT2500开中继模式当wifi。平常用着没问题,就是偶尔会断网,有时候自动就恢复了甚至感觉不到只是在MT2500的管理页面里看到wan口是离线。有时候就不行,要自己去拔插一下网线重启下之类的才会恢复。
换过一根网线,换完之后有半个月没断过,然后又开始偶尔的断网。
这种情况是什么造成的?
附上部分系统日志,太长了我截取部分看起来跟状态改变相关的部分:
Tue Apr4 08:30:11 2023 daemon.notice netifd: Network device 'eth0' link is up
Tue Apr4 08:30:11 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Apr4 08:30:11 2023 daemon.notice netifd: Interface 'wan' is setting up now
Tue Apr4 08:30:11 2023 daemon.notice netifd: wan (16495): udhcpc: started, v1.33.2
Tue Apr4 08:30:11 2023 daemon.notice netifd: wan (16495): udhcpc: sending discover
Tue Apr4 08:30:11 2023 daemon.notice netifd: wan (16495): udhcpc: sending select for 192.168.1.2
Tue Apr4 08:30:11 2023 daemon.notice netifd: wan (16495): udhcpc: lease of 192.168.1.2 obtained, lease time 86400
Tue Apr4 08:30:11 2023 daemon.notice netifd: Interface 'wan' is now up
Tue Apr4 08:30:11 2023 daemon.info dnsmasq: reading /tmp/resolv.conf.d/resolv.conf.auto
Tue Apr4 08:30:11 2023 daemon.info dnsmasq: using only locally-known addresses for domain test
……
Tue Apr4 08:30:11 2023 daemon.info dnsmasq: using nameserver 127.0.0.1#5335 for domain bmw.gp
……
Tue Apr4 08:30:12 2023 daemon.info dnsmasq: using 18461 more nameservers
Tue Apr4 08:30:12 2023 user.notice mwan3: Execute ifup event on interface wan (eth0)
Tue Apr4 08:30:12 2023 user.notice mwan3: Starting tracker on interface wan (eth0)
Tue Apr4 08:30:13 2023 kern.info kernel: [ 3559.903499] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Tue Apr4 08:30:13 2023 daemon.notice netifd: Network device 'eth0' link is down
Tue Apr4 08:30:13 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Apr4 08:30:13 2023 daemon.notice netifd: wan (16495): udhcpc: received SIGTERM
Tue Apr4 08:30:13 2023 daemon.notice netifd: wan (16495): udhcpc: unicasting a release of 192.168.1.2 to 192.168.1.1
Tue Apr4 08:30:13 2023 daemon.notice netifd: wan (16495): udhcpc: sending release
Tue Apr4 08:30:13 2023 daemon.notice netifd: wan (16495): udhcpc: entering released state
Tue Apr4 08:30:13 2023 user.info mwan3rtmon: Detect rtchange event.
Tue Apr4 08:30:13 2023 daemon.notice netifd: wan (16495): Command failed: Permission denied
Tue Apr4 08:30:13 2023 daemon.notice netifd: Interface 'wan' is now down
Tue Apr4 08:30:13 2023 daemon.notice netifd: Interface 'wan' is disabled
Tue Apr4 08:30:13 2023 kern.info kernel: [ 3560.006079] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Apr4 08:30:13 2023 daemon.notice netifd: Interface 'wan' is enabled
Tue Apr4 08:30:13 2023 daemon.warn dnsmasq: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Tue Apr4 08:30:14 2023 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Tue Apr4 08:30:14 2023 user.notice mwan3: Execute ifdown event on interface wan (unknown)
Tue Apr4 08:30:15 2023 user.info mwan3track: Detect ifdown event on interface wan (eth0)
Tue Apr4 08:30:16 2023 kern.info kernel: [ 3563.070950] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Apr4 08:30:16 2023 kern.info kernel: [ 3563.079416] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Apr4 08:30:16 2023 daemon.notice netifd: Network device 'eth0' link is up
Tue Apr4 08:30:16 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Apr4 08:30:16 2023 daemon.notice netifd: Interface 'wan' is setting up now
Tue Apr4 08:30:16 2023 daemon.notice netifd: wan (17797): udhcpc: started, v1.33.2
Tue Apr4 08:30:16 2023 daemon.notice netifd: wan (17797): udhcpc: sending discover
Tue Apr4 08:30:17 2023 daemon.notice netifd: wan (17797): udhcpc: sending select for 192.168.1.2
Tue Apr4 08:30:17 2023 daemon.notice netifd: wan (17797): udhcpc: lease of 192.168.1.2 obtained, lease time 86400
Tue Apr4 08:30:17 2023 daemon.notice netifd: Interface 'wan' is now up
Tue Apr4 08:30:17 2023 daemon.info dnsmasq: reading /tmp/resolv.conf.d/resolv.conf.auto
Tue Apr4 08:30:17 2023 daemon.info dnsmasq: using only locally-known addresses for domain test
……
Tue Apr4 08:30:17 2023 daemon.info dnsmasq: using nameserver 127.0.0.1#5335 for domain hkopentv.com
……
Tue Apr4 08:30:17 2023 daemon.info dnsmasq: using 18461 more nameservers
Tue Apr4 08:30:17 2023 user.notice mwan3: Execute ifup event on interface wan (eth0)
Tue Apr4 08:30:17 2023 user.notice mwan3: Starting tracker on interface wan (eth0)
Tue Apr4 08:30:17 2023 user.notice mwan3track: Stopping mwan3track for interface "wan"
Tue Apr4 08:30:18 2023 user.info mwan3rtmon: Detect rtchange event.
Tue Apr4 08:30:19 2023 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Tue Apr4 08:30:55 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.219 0e:2b:cb:a5:8c:e4
……
Tue Apr4 08:44:02 2023 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.8.215 68:ab:bc:65:4c:1d fawad-airrtc-30015_mibt4C1D
……
Tue Apr4 08:59:09 2023 user.info mwan3track: Lost 4 ping(s) on interface wan (eth0)
Tue Apr4 08:59:37 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
……
Tue Apr4 08:59:57 2023 user.info mwan3track: Lost 5 ping(s) on interface wan (eth0)
Tue Apr4 09:00:40 2023 user.info mwan3track: Lost 10 ping(s) on interface wan (eth0)
Tue Apr4 09:00:40 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
……
Tue Apr4 09:01:06 2023 user.info mwan3track: Lost 4 ping(s) on interface wan (eth0)
Tue Apr4 09:01:08 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.126 a8:51:ab:ce:95:b5
……
Tue Apr4 09:01:34 2023 user.info mwan3track: Lost 4 ping(s) on interface wan (eth0)
Tue Apr4 09:01:53 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.126 a8:51:ab:ce:95:b5
……
Tue Apr4 09:02:37 2023 user.info mwan3track: Lost 7 ping(s) on interface wan (eth0)
Tue Apr4 09:02:49 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
……
Tue Apr4 09:03:05 2023 user.info mwan3track: Lost 4 ping(s) on interface wan (eth0)
Tue Apr4 09:03:39 2023 user.notice mwan3: Execute ifdown event on interface wan (eth0)
Tue Apr4 09:03:39 2023 user.info mwan3track: Detect ifdown event on interface wan (eth0)
Tue Apr4 09:03:44 2023 user.notice mwan3track: Interface wan (eth0) is offline
Tue Apr4 09:03:46 2023 user.info mwan3track: Lost 10 ping(s) on interface wan (eth0)
Tue Apr4 09:03:53 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
……
Tue Apr4 09:03:56 2023 user.info mwan3track: Lost 2 ping(s) on interface wan (eth0)
Tue Apr4 09:03:58 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.126 a8:51:ab:ce:95:b5
……
Tue Apr4 09:04:03 2023 user.info mwan3track: Lost 1 ping(s) on interface wan (eth0)
Tue Apr4 09:04:11 2023 user.info mwan3track: Lost 1 ping(s) on interface wan (eth0)
Tue Apr4 09:04:14 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
……
Tue Apr4 09:04:42 2023 user.info mwan3track: Lost 8 ping(s) on interface wan (eth0)
Tue Apr4 09:04:57 2023 user.info mwan3track: Lost 2 ping(s) on interface wan (eth0)
Tue Apr4 09:05:06 2023 user.info mwan3track: Lost 2 ping(s) on interface wan (eth0)
Tue Apr4 09:05:16 2023 user.info mwan3track: Lost 2 ping(s) on interface wan (eth0)
Tue Apr4 09:05:22 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
……
Tue Apr4 09:05:29 2023 user.info mwan3track: Lost 1 ping(s) on interface wan (eth0)
Tue Apr4 09:05:32 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.216 88:12:ac:55:90:32
Tue Apr4 09:05:32 2023 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.8.216 88:12:ac:55:90:32 NarwalRobotics
Tue Apr4 09:05:34 2023 user.notice mwan3track: Interface wan (eth0) is online
Tue Apr4 09:05:34 2023 user.notice mwan3: Execute ifup event on interface wan (eth0)
Tue Apr4 09:05:34 2023 user.notice mwan3: Starting tracker on interface wan (eth0)
Tue Apr4 09:05:36 2023 user.info mwan3rtmon: Detect rtchange event.
Tue Apr4 09:05:36 2023 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Tue Apr4 09:05:41 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
………
Tue Apr4 09:10:53 2023 user.info mwan3track: Lost 3 ping(s) on interface wan (eth0)
看看光猫的型号呢,重新插拔网线就立即好了吗,还是说必须重启mt2500呢,需要重启光猫吗 hansome 发表于 2023-4-4 19:56
看看光猫的型号呢,重新插拔网线就立即好了吗,还是说必须重启mt2500呢,需要重启光猫吗 ...
光猫的型号。。。就是电信装网的时候配的那种,我APP上看叫天翼5CA2,品牌: SDNSDN,型号: SDN20XX。能恢复的情况是一般我拔插一下网线就好了;不过我有时候也会干脆都重启一下。 jkle 发表于 2023-4-5 17:52
能提供更多的信息嗎?
比如说啥,我把光猫的型号啥的回复给楼上了 看log像是mwan3引起的,看下你多WAN那边的配置呢 毫无疑问就是Mwan3引起的,直接修改mwan3的配置就可以了 我也突然会断网,只不过是我在打游戏的情况下,不清楚什么情况。 看上去是多WAN检测的问题,可以在这里将多WAN配置关闭试试
萝卜大侠 发表于 2023-5-18 09:41
看上去是多WAN检测的问题,可以在这里将多WAN配置关闭试试
好像没解决,很奇怪。而且关掉之后就看不到这个wan口的联网状态了,现在断网都看不出了= = xyc9121993 发表于 2023-7-1 14:15
好像没解决,很奇怪。而且关掉之后就看不到这个wan口的联网状态了,现在断网都看不出了= = ...
有没有尝试过更换网线呢? 萝卜大侠 发表于 2023-7-1 16:34
有没有尝试过更换网线呢?
尝试过好几根网线了我一开始也以为是网线没插紧的问题,因为有时候重新拔插一下网线可能也好了。最近看日志有时候是某个设备一直在请求dhcp的样子
Thu Aug 10 04:18:09 2023 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca keting
Thu Aug 10 04:18:10 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
Thu Aug 10 04:18:10 2023 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca keting
Thu Aug 10 04:18:29 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
Thu Aug 10 04:18:29 2023 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca keting
Thu Aug 10 04:20:02 2023 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca
Thu Aug 10 04:20:02 2023 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.8.123 a8:51:ab:d5:9e:ca keting 萝卜大侠 发表于 2023-7-1 16:34
有没有尝试过更换网线呢?
内核日志么看不懂了
[ 11.594858] mediatek_soc_hnat 15100000.hnat: wan = eth0
[ 11.600144] mediatek_soc_hnat 15100000.hnat: lan = eth1
[ 11.605419] mediatek_soc_hnat 15100000.hnat: ppd = eth1
[ 11.610654] mediatek_soc_hnat 15100000.hnat: gmac num = 2
[ 11.616057] mediatek_soc_hnat 15100000.hnat: ppe num = 1
[ 11.621861] mediatek_soc_hnat 15100000.hnat: PPE0 entry number = 8192
[ 11.638728] mediatek_soc_hnat 15100000.hnat: PPE0 hwnat start
[ 11.644544] hnat roaming work enable
[ 12.824026] mtk_soc_eth 15100000.ethernet eth0: Link is Down
[ 12.862354] MediaTek MT7981 PHY mdio-bus:00: TX-VCM SW cal result: 0x1
[ 12.873704] mtk_soc_eth 15100000.ethernet eth1: PHY driver
[ 12.886120] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/gmii link mode
[ 12.894182] br-lan: port 1(eth1) entered blocking state
[ 12.899477] br-lan: port 1(eth1) entered disabled state
[ 12.904928] device eth1 entered promiscuous mode
[ 12.912680] br-lan: port 1(eth1) entered blocking state
[ 12.917941] br-lan: port 1(eth1) entered forwarding state
[ 12.930688] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
[ 12.939133] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.947720] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 13.526296] tertf: br-lan registered, add it
[ 13.863010] br-lan: port 1(eth1) entered disabled state
[ 23.110804] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 23.119285] br-lan: port 1(eth1) entered blocking state
[ 23.124546] br-lan: port 1(eth1) entered forwarding state
[ 36.422707] mtk_soc_eth 15100000.ethernet eth1: Link is Down
[ 36.428477] br-lan: port 1(eth1) entered disabled state
[ 38.470817] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 38.479349] br-lan: port 1(eth1) entered blocking state
[ 38.484610] br-lan: port 1(eth1) entered forwarding state 顶一顶。我现在设置小米路由器每周重启一次好像断流情况变少了;不过偶尔时有出现;有没有大佬看一看上面的日志,能不能看出是啥问题?
页:
[1]