RT-AC86U经常断流，求大神帮忙
请问和开启UPnP有关系吗？==================================================Jan 22 05:11:19 pppd:Connection terminated.Jan 22 05:11:19 pppd: ModemhangupJan 22 05:11:19 WAN Connection:Fail to connect with some issues.Jan 22 05:11:19 DualWAN: skipsingle wan wan_led_control - WANRED offJan 22 05:11:19 nat: apply redirectrulesJan 22 05:11:29 pppd:Connected to 10:51:72:4b:40:25 via interface eth0Jan 22 05:11:29 pppd: Connect:ppp0 <--> eth0Jan 22 05:11:32 pppd: PAPauthentication succeededJan 22 05:11:32 pppd: peerfrom calling number 10:51:72:4B:40:25 authorizedJan 22 05:11:32 pppd:localIP address 100.64.27.122Jan 22 05:11:32 pppd: remoteIP address 100.64.0.1Jan 22 05:11:32 pppd:primary DNS address 218.30.19.40Jan 22 05:11:32 pppd:secondary DNS address 61.134.1.4Jan 22 05:11:32 rc_service: ip-up29198:notify_rc start_firewallJan 22 05:11:32 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 22 05:11:32 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol TCPJan 22 05:11:32 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 22 05:11:32 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 22 05:11:32 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 22 05:11:32 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol TCPJan 22 05:11:32 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 22 05:11:32 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 22 05:11:32 miniupnpd:shutting down MiniUPnPdJan 22 05:11:32 nat: apply natrules (/tmp/nat_rules_ppp0_eth0)Jan 22 05:11:32 wan: finish addingmulti routesJan 22 05:11:32 rc_service: ip-up29198:notify_rc stop_upnpJan 22 05:11:32 rc_service:waitting "start_firewall" via ip-up ...Jan 22 05:11:32 ntp: start NTPupdateJan 22 05:11:32 miniupnpd:version 1.9 startedJan 22 05:11:32 miniupnpd:HTTP listening on port 55059Jan 22 05:11:32 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 22 05:11:33 rc_service: ip-up29198:notify_rc start_upnpJan 22 05:11:33 rc_service:waitting "stop_upnp" via ip-up ...Jan 22 05:11:33 miniupnpd:shutting down MiniUPnPdJan 22 05:11:34 miniupnpd:version 1.9 startedJan 22 05:11:34 miniupnpd:HTTP listening on port 51480Jan 22 05:11:34 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 22 05:11:36 WAN Connection: WAN was restored.===============================================Jan 23 16:53:18 WAN Connection:Fail to connect with some issues.Jan 23 16:53:18 DualWAN: skipsingle wan wan_led_control - WANRED offJan 23 16:53:18 nat: apply redirectrulesJan 23 16:53:20 pppd:Connection terminated.Jan 23 16:53:20 pppd: ModemhangupJan 23 16:53:30 pppd:Connected to 10:51:72:4b:40:25 via interface eth0Jan 23 16:53:30 pppd: Connect:ppp0 <--> eth0Jan 23 16:53:33 pppd: PAPauthentication succeededJan 23 16:53:33 pppd: peerfrom calling number 10:51:72:4B:40:25 authorizedJan 23 16:53:33 pppd:localIP address 100.64.7.102Jan 23 16:53:33 pppd: remoteIP address 100.64.0.1Jan 23 16:53:33 pppd:primary DNS address 218.30.19.40Jan 23 16:53:33 pppd:secondary DNS address 61.134.1.4Jan 23 16:53:33 rc_service: ip-up24454:notify_rc start_firewallJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 8888 -> 192.168.50.226:8888 protocol UDPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:1080 protocol TCPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:3027 protocol UDPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 27870 -> 192.168.50.136:27870 protocol UDPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 1443 -> 192.168.50.129:1443 protocol TCPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 54321 -> 192.168.50.17:54321 protocol TCPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 54321 -> 192.168.50.17:12345 protocol UDPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 53302 -> 192.168.50.17:56698 protocol TCPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 53302 -> 192.168.50.17:53302 protocol UDPJan 23 16:53:33 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 23 16:53:33 miniupnpd:Failed to redirect 56697 -> 192.168.50.17:56697 protocol TCPJan 23 16:53:33 miniupnpd:shutting down MiniUPnPdJan 23 16:53:33 wan: finish addingmulti routesJan 23 16:53:33 nat: apply natrules (/tmp/nat_rules_ppp0_eth0)Jan 23 16:53:33 rc_service: ip-up24454:notify_rc stop_upnpJan 23 16:53:33 rc_service:waitting "start_firewall" via ip-up ...Jan 23 16:53:33 ntp: start NTPupdateJan 23 16:53:33 miniupnpd:version 1.9 startedJan 23 16:53:33 miniupnpd:HTTP listening on port 43643Jan 23 16:53:33 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 23 16:53:34 rc_service: ip-up24454:notify_rc start_upnpJan 23 16:53:34 rc_service:waitting "stop_upnp" via ip-up ...Jan 23 16:53:34 miniupnpd:shutting down MiniUPnPdJan 23 16:53:35 miniupnpd:version 1.9 startedJan 23 16:53:35 miniupnpd:HTTP listening on port 55914Jan 23 16:53:35 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 23 16:53:38 WAN Connection: WANwas restored.===================================================Jan 25 04:26:12 WAN Connection:Fail to connect with some issues.Jan 25 04:26:12 DualWAN: skipsingle wan wan_led_control - WANRED offJan 25 04:26:12 nat: apply redirectrulesJan 25 04:26:15 pppd:Connection terminated.Jan 25 04:26:15 pppd: ModemhangupJan 25 04:26:26 pppd:Connected to 10:51:72:4b:40:25 via interface eth0Jan 25 04:26:26 pppd: Connect:ppp0 <--> eth0Jan 25 04:26:29 pppd: PAPauthentication succeededJan 25 04:26:29 pppd: peerfrom calling number 10:51:72:4B:40:25 authorizedJan 25 04:26:29 pppd:localIP address 100.64.7.162Jan 25 04:26:29 pppd: remoteIP address 100.64.0.1Jan 25 04:26:29 pppd:primary DNS address 218.30.19.40Jan 25 04:26:29 pppd:secondary DNS address 61.134.1.4Jan 25 04:26:29 rc_service: ip-up19574:notify_rc start_firewallJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol TCPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 8888 -> 192.168.50.226:8888 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:1080 protocol TCPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:3027 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 27870 -> 192.168.50.136:27870 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 37792 -> 192.168.50.97:37792 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol TCPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 8888 -> 192.168.50.226:8888 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:1080 protocol TCPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:3027 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 27870 -> 192.168.50.136:27870 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 37792 -> 192.168.50.97:37792 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol TCPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 8888 -> 192.168.50.226:8888 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:1080 protocol TCPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:3027 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 27870 -> 192.168.50.136:27870 protocol UDPJan 25 04:26:29 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 25 04:26:29 miniupnpd:Failed to redirect 37792 -> 192.168.50.97:37792 protocol UDPJan 25 04:26:29 miniupnpd:shutting down MiniUPnPdJan 25 04:26:29 wan: finish addingmulti routesJan 25 04:26:29 rc_service: ip-up19574:notify_rc stop_upnpJan 25 04:26:29 ntp: start NTPupdateJan 25 04:26:29 rc_service:waitting "start_firewall" via ip-up ...Jan 25 04:26:29 nat: apply natrules (/tmp/nat_rules_ppp0_eth0)Jan 25 04:26:29 miniupnpd:version 1.9 startedJan 25 04:26:29 miniupnpd:HTTP listening on port 52760Jan 25 04:26:29 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 25 04:26:30 rc_service: ip-up19574:notify_rc start_upnpJan 25 04:26:30 rc_service:waitting "stop_upnp" via ip-up ...Jan 25 04:26:30 miniupnpd:shutting down MiniUPnPdJan 25 04:26:31 miniupnpd:version 1.9 startedJan 25 04:26:31 miniupnpd:HTTP listening on port 44942Jan 25 04:26:31 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 25 04:26:32 WAN Connection: WANwas restored.==========================================================Jan 26 15:14:31 WAN Connection:Fail to connect with some issues.Jan 26 15:14:31 DualWAN: skipsingle wan wan_led_control - WANRED offJan 26 15:14:31 nat: apply redirectrulesJan 26 15:14:32 pppd:Connection terminated.Jan 26 15:14:32 pppd: ModemhangupJan 26 15:14:42 pppd:Connected to 10:51:72:4b:40:25 via interface eth0Jan 26 15:14:42 pppd: Connect:ppp0 <--> eth0Jan 26 15:14:45 pppd: PAPauthentication succeededJan 26 15:14:45 pppd: peerfrom calling number 10:51:72:4B:40:25 authorizedJan 26 15:14:45 pppd:localIP address 100.64.48.192Jan 26 15:14:45 pppd: remoteIP address 100.64.0.1Jan 26 15:14:45 pppd:primary DNS address 218.30.19.40Jan 26 15:14:45 pppd:secondary DNS address 61.134.1.4Jan 26 15:14:45 rc_service: ip-up13902:notify_rc start_firewallJan 26 15:14:45 miniupnpd:add_filter_rule() : iptc_commit() error : Resource temporarily unavailableJan 26 15:14:45 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:1080 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:3027 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 27870 -> 192.168.50.136:27870 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 36045 -> 192.168.50.97:36045 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 1443 -> 192.168.50.129:1443 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 54321 -> 192.168.50.17:54321 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 54321 -> 192.168.50.17:12345 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 61130 -> 192.168.50.17:61929 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 61130 -> 192.168.50.17:61130 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 61928 -> 192.168.50.17:61928 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 22750 -> 192.168.50.17:22750 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 8888 -> 192.168.50.226:8888 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:1080 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 13841 -> 192.168.50.129:3027 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 27870 -> 192.168.50.136:27870 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 36045 -> 192.168.50.97:36045 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 1443 -> 192.168.50.129:1443 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 54321 -> 192.168.50.17:54321 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 54321 -> 192.168.50.17:12345 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 61130 -> 192.168.50.17:61929 protocol TCPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 61130 -> 192.168.50.17:61130 protocol UDPJan 26 15:14:45 miniupnpd:add_filter_rule() : chain FUPNP not foundJan 26 15:14:45 miniupnpd:Failed to redirect 61928 -> 192.168.50.17:61928 protocol TCPJan 26 15:14:45 miniupnpd:shutting down MiniUPnPdJan 26 15:14:45 wan: finish addingmulti routesJan 26 15:14:45 nat: apply natrules (/tmp/nat_rules_ppp0_eth0)Jan 26 15:14:45 ntp: start NTPupdateJan 26 15:14:45 rc_service: ip-up13902:notify_rc stop_upnpJan 26 15:14:45 rc_service:waitting "start_firewall" via ip-up ...Jan 26 15:14:45 miniupnpd:version 1.9 startedJan 26 15:14:45 miniupnpd:HTTP listening on port 42055Jan 26 15:14:45 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 26 15:14:46 WAN Connection: WANwas restored.==================================================Jan 28 02:43:35 WAN Connection:Fail to connect with some issues.Jan 28 02:43:35 DualWAN: skipsingle wan wan_led_control - WANRED offJan 28 02:43:35 nat: apply redirectrulesJan 28 02:43:36 pppd:Connection terminated.Jan 28 02:43:36 pppd: ModemhangupJan 28 02:43:46 pppd:Connected to 10:51:72:4b:40:25 via interface eth0Jan 28 02:43:46 pppd: Connect:ppp0 <--> eth0Jan 28 02:43:49 pppd: PAPauthentication succeededJan 28 02:43:49 pppd: peerfrom calling number 10:51:72:4B:40:25 authorizedJan 28 02:43:49 pppd:localIP address 100.64.125.143Jan 28 02:43:49 pppd: remoteIP address 100.64.0.1Jan 28 02:43:49 pppd:primary DNS address 218.30.19.40Jan 28 02:43:49 pppd:secondary DNS address 61.134.1.4Jan 28 02:43:49 rc_service: ip-up8845:notify_rc start_firewallJan 28 02:43:49 miniupnpd:shutting down MiniUPnPdJan 28 02:43:50 wan: finish addingmulti routesJan 28 02:43:50 nat: apply natrules (/tmp/nat_rules_ppp0_eth0)Jan 28 02:43:50 rc_service: ip-up8845:notify_rc stop_upnpJan 28 02:43:50 rc_service:waitting "start_firewall" via ip-up ...Jan 28 02:43:50 ntp: start NTPupdateJan 28 02:43:50 miniupnpd:version 1.9 startedJan 28 02:43:50 miniupnpd:HTTP listening on port 52749Jan 28 02:43:50 miniupnpd:Listening for NAT-PMP/PCP traffic on port 5351Jan 28 02:43:50 WAN Connection: WANwas restored. 1-22 05.11
同样的问题。一个多小时一断。。。。。 换别的路由器就没问题 应该和开UPnP无关，具体什么原因导致，从上面的系统日志还看不出来。 Master 发表于 2020-2-10 19:46
应该和开UPnP无关，具体什么原因导致，从上面的系统日志还看不出来。
昨天已经刷了官改，求大神帮忙看看这些日志都是啥意思，我之前从见过
Feb 12 19:00:08 disk_monitor: Got SIGALRM...
Feb 12 19:32:17 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:6D:50:FC:1F:6D, status: 0, reason: d11 RC reserved (0)
Feb 12 19:32:17 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 8C:6D:50:FC:1F:6D, status: 0, reason: d11 RC reserved (0)
Feb 12 22:22:42 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:6D:50:FC:1F:6D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 12 22:22:42 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:6D:50:FC:1F:6D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Feb 12 23:00:08 disk_monitor: Got SIGALRM...
Feb 12 23:36:57 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E0:33:8E:17:BF9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 12 23:36:59 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E0:33:8E:17:BF9, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Feb 12 23:37:00 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth E0:33:8E:17:BF9, status: 0, reason: d11 RC reserved (0)
Feb 12 23:37:00 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc E0:33:8E:17:BF9, status: 0, reason: d11 RC reserved (0)
Feb 13 00:36:56 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E0:33:8E:17:BF9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 13 00:36:56 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth E0:33:8E:17:BF9, status: 0, reason: d11 RC reserved (0)
Feb 13 00:36:56 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc E0:33:8E:17:BF9, status: 0, reason: d11 RC reserved (0)
Feb 13 01:36:55 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E0:33:8E:17:BF9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 13 01:36:55 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth E0:33:8E:17:BF9, status: 0, reason: d11 RC reserved (0)
Feb 13 01:36:55 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc E0:33:8E:17:BF9, status: 0, reason: d11 RC reserved (0)
Feb 13 02:57:25 WATCHDOG: period_retry = 1
Feb 13 02:57:26 WATCHDOG: retrieve firmware information
Feb 13 02:57:26 WATCHDOG: no need to upgrade firmware
Feb 13 02:57:55 WATCHDOG: period_retry = 2
Feb 13 02:57:56 WATCHDOG: retrieve firmware information
Feb 13 02:57:56 WATCHDOG: no need to upgrade firmware
Feb 13 05:36:50 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E0:33:8E:17:BF:D9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 13 05:36:51 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth E0:33:8E:17:BF:D9, status: 0, reason: d11 RC reserved (0)
Feb 13 05:36:51 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc E0:33:8E:17:BF:D9, status: 0, reason: d11 RC reserved (0)
Feb 13 06:36:49 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E0:33:8E:17:BF:D9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 13 06:36:50 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth E0:33:8E:17:BF:D9, status: 0, reason: d11 RC reserved (0)
Feb 13 06:36:50 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc E0:33:8E:17:BF:D9, status: 0, reason: d11 RC reserved (0)
Feb 13 06:37:07 ntp: start NTP update
Feb 13 08:38:23 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind E4:46:DA:FF:B1:A7, status: 0, reason: Disassociated due to inactivity (4)
Feb 13 08:38:23 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc E4:46:DA:FF:B1:A7, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Feb 13 10:03:37 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 18:4F:32:F7:D0:97, status: 0, reason: d11 RC reserved (0)
Feb 13 10:03:37 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 18:4F:32:F7:D0:97, status: 0, reason: d11 RC reserved (0)
Feb 13 11:45:09 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 18:4F:32:F7:D0:97, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Feb 13 11:45:09 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 18:4F:32:F7:D0:97, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Feb 13 11:58:27 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Feb 13 11:58:39 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Feb 13 11:58:42 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Feb 13 11:59:44 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc013770de8 next ffffffc01371f660 prev ffffffc01371f660 rep_entry->list ffffffc01371f660 next ffffffc013770de8 prev ffffffc013770de8
Feb 13 11:59:44 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc013770de8 next ffffffc0137ad6a0 prev ffffffc0137ad6a0 rep_entry->list ffffffc0137ad6a0 next ffffffc013770de8 prev ffffffc013770de8 wangstar560 发表于 2020-2-13 18:54
昨天已经刷了官改，求大神帮忙看看这些日志都是啥意思，我之前从见过
Feb 12 19:00:08 disk_monitor: Got ...
主要就是判断2.4G无线客户端连线是否正常的log + 确认过一次固件是否要更新 + LAN口状态 + 最后两行好像是关于处理多播的相关信息
页:
[1]