justo 发表于 2022-6-24 16:00:12

yanke1124 发表于 2022-6-24 15:42
那照这样看我可能解决死机问题了,以前是无法自动重启,是死机,每隔几天一次,现在是死机变为重启了,所 ...
如果没有IPv6资源的话那就先不要开功能了。虽然这个和重启没有关系。
升级完固件之后,最好重置一下。

死机的问题我遇到过两三次。也不知道原因

yanke1124 发表于 2022-6-24 16:03:38

justo 发表于 2022-6-24 15:59
说不清楚,我官方正式版最新的那个如果不管ax,那基本上一天重启一次
关了后坚持七天了
但是,如果把设备 ...

我组的MESH,加上节点,长期设备(包含两个节点路由)不到20个,多数重启都发生在晚上睡觉过程中,早上起来发现死机的

yanke1124 发表于 2022-6-24 16:07:34

justo 发表于 2022-6-24 16:00
如果没有IPv6资源的话那就先不要开功能了。虽然这个和重启没有关系。
升级完固件之后,最好重置一下。


IPv6对我来说主要是内网穿透比较好用,当然NAS也可以直接用厂家的内网穿透,其实速度也还好,毕竟重庆电信千兆宽带给的上行也就35M,哎,还是年龄大了也不忘小折腾

yanke1124 发表于 2022-6-24 16:09:38

justo 发表于 2022-6-24 16:00
如果没有IPv6资源的话那就先不要开功能了。虽然这个和重启没有关系。
升级完固件之后,最好重置一下。


重置太麻烦,节点也要重置,重新配对,配烦了,手动重启一下可以吗;P

justo 发表于 2022-6-24 16:36:00

yanke1124 发表于 2022-6-24 16:09
重置太麻烦,节点也要重置,重新配对,配烦了,手动重启一下可以吗

你这种如果是固定时间死机,那要查一下别的原因,可能是外因引起的。
按理说二十来个设备,不会有我这种自动重启现象。
最好是重置一下吧,有些奇奇怪怪的问题,是升级引起的。找个休息时间搞一下。

justo 发表于 2022-6-24 16:36:51

yanke1124 发表于 2022-6-24 16:07
IPv6对我来说主要是内网穿透比较好用,当然NAS也可以直接用厂家的内网穿透,其实速度也还好,毕竟重庆电 ...
你们电信限流量吗?上海电信,达到1T就限制速度到300M,太绝了

yanke1124 发表于 2022-6-24 16:37:28

本帖最后由 yanke1124 于 2022-6-25 14:48 编辑

justo 发表于 2022-6-24 16:36
你这种如果是固定时间死机,那要查一下别的原因,可能是外因引起的。
按理说二十来个设备,不会有我这种 ...

并不固定,可能是明晚,也可能是后晚,有一次是在下午,其他均在不定期的晚上。

yanke1124 发表于 2022-6-24 20:07:36

本帖最后由 yanke1124 于 2022-6-25 14:48 编辑

Jun 24 03:04:07 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:04:49 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:07:36 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:08:18 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:09:07 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:09:39 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:12:27 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:13:03 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:14:07 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:14:49 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:17:17 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:17:50 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:19:08 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:19:49 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:21:59 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.
Jun 24 03:21:59 kernel: ^[ xport_reset: rc = 0; intf = 1 port = 0 spd = 1G dup = 1
Jun 24 03:21:59 kernel: ^[[0m
Jun 24 03:22:00 kernel: MACSEC: macsec is not enabled
Jun 24 03:22:01 kernel: ^[ xport_init: rc = 0; intf = 1 port = 0 spd = 1G dup = 1
Jun 24 03:22:01 kernel: ^[[0m
Jun 24 03:22:01 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 1000 mbps full duplex
Jun 24 03:22:04 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.
Jun 24 03:22:04 kernel: ^[ xport_reset: rc = 0; intf = 1 port = 0 spd = 1G dup = 1
Jun 24 03:22:04 kernel: ^[[0m
Jun 24 03:22:08 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 100 mbps full duplex
Jun 24 03:22:08 WAN Connection: Fail to connect with some issues.
Jun 24 03:22:13 WAN Connection: WAN(0) link down.
Jun 24 03:22:25 kernel: MACSEC: macsec is not enabled
Jun 24 03:22:26 kernel: ^[ xport_init: rc = 0; intf = 1 port = 0 spd = 1G dup = 1
Jun 24 03:22:26 kernel: ^[[0m
Jun 24 03:22:26 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 1000 mbps full duplex
Jun 24 03:22:28 WAN Connection: WAN(0) link up.
Jun 24 03:22:28 rc_service: wanduck 24819:notify_rc restart_wan_if 0
Jun 24 03:22:30 odhcp6c: Failed to send DHCPV6 message to ff02::1:2 (Network is unreachable)
Jun 24 03:22:33 kernel: netlink: 12 bytes leftover after parsing attributes in process `ip'.
Jun 24 03:22:33 kernel: netlink: 12 bytes leftover after parsing attributes in process `ip'.
Jun 24 03:22:33 dnsmasq: failed to create listening socket for ::1: Address already in use
Jun 24 03:22:33 dnsmasq: interface br0 failed to join DHCPv6 multicast group: Address already in use
Jun 24 03:22:34 dnsmasq: failed to create listening socket for fe80::642:1aff:fe5f:5348%br0: Address already in use
Jun 24 03:22:35 pppd: pppd 2.4.7 started by ROG-GT-AX6000, uid 0
Jun 24 03:22:35 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.
Jun 24 03:22:35 kernel: ^[ xport_reset: rc = 0; intf = 1 port = 0 spd = 1G dup = 1
Jun 24 03:22:35 kernel: ^[[0m
Jun 24 03:22:38 kernel: MACSEC: macsec is not enabled
Jun 24 03:22:39 kernel: ^[ xport_init: rc = 0; intf = 1 port = 0 spd = 1G dup = 1
Jun 24 03:22:39 kernel: ^[[0m
Jun 24 03:22:39 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 1000 mbps full duplex
Jun 24 03:22:40 WAN Connection: Fail to connect with some issues.
Jun 24 03:22:46 modprobe: module ip6t_REJECT not found in modules.dep
Jun 24 03:22:46 modprobe: module ip6t_ROUTE not found in modules.dep
Jun 24 03:22:46 modprobe: module ip6t_LOG not found in modules.dep
Jun 24 03:22:46 dhcp client: bound 192.168.1.2/255.255.255.0 via 192.168.1.1 for 86400 seconds.
Jun 24 03:22:50 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Jun 24 03:23:10 pppd: Timeout waiting for PADO packets
Jun 24 03:23:25 pppd: Connected to 00:00:5e:00:01:0b via interface eth0
Jun 24 03:23:25 pppd: Connect: ppp0 <--> eth0
Jun 24 03:23:25 pppd: PAP authentication succeeded
Jun 24 03:23:25 pppd: peer from calling number 00:00:5E:00:01:0B authorized
Jun 24 03:23:25 pppd: localLL address fe80::64db:490e:c599:1e60
Jun 24 03:23:25 pppd: remote LL address fe80::0200:5eff:fe00:010b
Jun 24 03:23:25 rc_service: ipv6-up 25996:notify_rc start_rdisc6
Jun 24 03:23:25 rc_service: ipv6-up 25996:notify_rc start_dhcp6c
Jun 24 03:23:25 rc_service: waitting "start_rdisc6" via ipv6-up ...
Jun 24 03:23:25 pppd: localIP address 10.1.108.216
Jun 24 03:23:25 pppd: remote IP address 10.1.108.1
Jun 24 03:23:25 pppd: primary   DNS address 61.128.128.68
Jun 24 03:23:25 pppd: secondary DNS address 61.128.192.68
Jun 24 03:23:25 modprobe: module ip6t_REJECT not found in modules.dep
Jun 24 03:23:25 modprobe: module ip6t_ROUTE not found in modules.dep
Jun 24 03:23:25 modprobe: module ip6t_LOG not found in modules.dep
Jun 24 03:23:25 wan: finish adding multi routes
Jun 24 03:23:25 miniupnpd: shutting down MiniUPnPd
Jun 24 03:23:25 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Jun 24 03:23:25 miniupnpd: HTTP listening on port 34491
Jun 24 03:23:25 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Jun 24 03:23:29 dhcp6 client: bound prefix 240e:332:d01:d000::/56
Jun 24 03:23:31 WAN Connection: WAN was restored.

哥们看看,是不是运营商的问题。
昨晚又问了电信维修师傅,说设置了两天光猫自动重启的,真的是服了,还不给改!

justo 发表于 2022-6-25 10:18:00

yanke1124 发表于 2022-6-24 16:37
并不固定,可能是明晚,也可能是后晚,有一次是在下午,其他均在不定期的晚上 ...

或者,你把日志发论坛来,,版主管理员他们都能帮忙分析的。

normon 发表于 2022-6-25 16:24:18

justo 发表于 2022-6-24 16:36
你们电信限流量吗?上海电信,达到1T就限制速度到300M,太绝了
不限速,1T我肯定不够,我现在是电信联通双千兆,都不限速的。
页: 30 31 32 33 34 35 36 37 38 39 [40] 41 42 43 44 45 46 47 48 49
查看完整版本: GT-AX6000奇奇怪怪的自动重启姿势之一【不重启了,完结】