大神帮我看下这个日志内容什么意思
今天发现两次异常了，源自丫头说链接不上WIFI，昨天刚用N1刷了玩心云，路由器里面打开了:启动UPnP，启动DMZ。日志内容，最近一次：
May5 13:05:34 A.QoS: qos_count=0, qos_check=1
May5 13:05:35 ntp: start NTP update
Jul 16 18:35:07 rc_service: ntp 1941:notify_rc restart_diskmon
Jul 16 18:35:07 disk_monitor: Finish
Jul 16 18:35:07 disk monitor: be idle
Jul 16 18:35:08 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:08 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:08 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:09 kernel: Archer TCP Pure ACK Enabled
Jul 16 18:35:09 rc_service: ip-up 1906:notify_rc stop_samba
Jul 16 18:35:09 rc_service: ip-up 1906:notify_rc start_samba
Jul 16 18:35:09 rc_service: waitting "stop_samba" via ip-up ...
Jul 16 18:35:09 Samba Server: smb daemon is stopped
Jul 16 18:35:09 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:09 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:09 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:10 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:10 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:10 watchdog: start ddns.
Jul 16 18:35:10 rc_service: watchdog 1591:notify_rc restart_ddns watchdog
Jul 16 18:35:10 rc_service: waitting "start_samba" via...
Jul 16 18:35:10 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:11 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:11 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:11 kernel:*** ERROR: # redir_url=http://192.168.20.1:80/blocking.asp?cat_id=75&mac=327669DF1189&domain=metrics1-drcn.dt.dbankcloud.cn
Jul 16 18:35:12 ddns: update WWW.ASUS.COM update@asus.com, wan_unit 0
Jul 16 18:35:12 ddns: Clear ddns cache.
Jul 16 18:35:12 ddns: Start Inadyn(9).
Jul 16 18:35:12 inadyn: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Jul 16 18:35:12 inadyn: Update forced for alias A7B2C36D0F8B7FA4EC49E34684FF22389.asuscomm.com, new IP# 180.139.133.63
Jul 16 18:35:15 inadyn: alias address=<180.139.133.63>
Jul 16 18:35:15 inadyn: request<GET /ddns/update.jsp?hostname=A7B2C36D0F8B7FA4EC49E34684FF22389.asuscomm.com&myip=180.139.133.63&model=RT-AX82U&fw_ver=3.0.0.4.388_22158-gba695f1 HTTP/1.0^M Authorization: Basic MjQ0QkZFQzM1RTI4OjBGODJEOTE0NTJCNEU1RDFDODRBMTI1RDg3MDFGOEU2^M Host: ns1.asuscomm.com^M User-Agent: inadyn/2.8.1 https://github.com/troglobit/inadyn/issues^M ^M >
Jul 16 18:35:15 inadyn: HTTP/1.1 200 OK^M Date: Sun, 16 Jul 2023 10:35:15 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Jul 16 18:35:15 inadyn: Updating cache for A7B2C36D0F8B7FA4EC49E34684FF22389.asuscomm.com
Jul 16 18:35:15 wlceventd: wlceventd_proc_event(530): eth5: Auth 5C:E5:0C:42:E4:8C, status: Successful (0), rssi:0
Jul 16 18:35:15 wlceventd: wlceventd_proc_event(559): eth5: Assoc 5C:E5:0C:42:E4:8C, status: Successful (0), rssi:-46
Jul 16 18:35:15 ddns: ddns update ok
Jul 16 18:35:32 crond: time disparity of 2733450 minutes detected
Jul 16 18:35:35 kernel: TCP: mptcp_fallback_infinite 0xf5d5abb3 will fallback - pi 1, src 180.139.133.63 dst 99.83.159.30 from tcp_rcv_established+0x13c/0x75c
Jul 16 18:35:39 wlceventd: wlceventd_proc_event(530): eth5: Auth 5C:E5:0C:10:16:59, status: Successful (0), rssi:0
Jul 16 18:35:39 wlceventd: wlceventd_proc_event(559): eth5: Assoc 5C:E5:0C:10:16:59, status: Successful (0), rssi:-60
Jul 16 18:36:02 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind E2:C2:AC:D1:57:37, status: 0, reason: Disassociated due to inactivity (4), rssi:-55
Jul 16 18:36:02 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind E2:C2:AC:D1:57:37, status: 0, reason: Previous authentication no longer valid (2), rssi:-55
Jul 16 18:36:03 wlceventd: wlceventd_proc_event(511): eth6: Disassoc E2:C2:AC:D1:57:37, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jul 16 18:36:10 wlceventd: wlceventd_proc_event(530): eth6: Auth 5E:F7:65:4A:D3:DE, status: Successful (0), rssi:0
Jul 16 18:36:10 wlceventd: wlceventd_proc_event(559): eth6: Assoc 5E:F7:65:4A:D3:DE, status: Successful (0), rssi:-50
Jul 16 18:36:16 wlceventd: wlceventd_proc_event(530): eth5: Auth 50:EC:50:FF:10:17, status: Successful (0), rssi:0
Jul 16 18:36:16 wlceventd: wlceventd_proc_event(559): eth5: Assoc 50:EC:50:FF:10:17, status: Successful (0), rssi:-62
Jul 16 18:36:33 wlceventd: wlceventd_proc_event(530): eth6: Auth 38:E6:0A:8A:DF:45, status: Successful (0), rssi:0
Jul 16 18:36:33 wlceventd: wlceventd_proc_event(559): eth6: Assoc 38:E6:0A:8A:DF:45, status: Successful (0), rssi:-73
Jul 16 18:36:41 hour monitor: ntp sync fail, will retry after 120 sec
Jul 16 18:36:42 WATCHDOG: periodic_check AM 2:15
Jul 16 18:36:42 WATCHDOG: do webs_update
Jul 16 18:36:51 WATCHDOG: retrieve firmware information
Jul 16 18:36:51 WATCHDOG: user in use
Jul 16 18:36:55 ahs: Update ahs JSON file.
Jul 16 18:37:21 WATCHDOG: do webs_update
Jul 16 18:37:21 WATCHDOG: retrieve firmware information
Jul 16 18:37:21 WATCHDOG: user in use
Jul 16 18:37:51 WATCHDOG: do webs_update
Jul 16 18:37:51 WATCHDOG: retrieve firmware information
Jul 16 18:37:51 WATCHDOG: user in use
启动 UPnP启动
這段log主要是
1.阻止了一個網頁，可能是那種搶紅包的，被判斷為危險網頁
2.E2:C2:AC1:57:37這個MAC連接狀態，由於inactivity和驗證不正確連線異常，還有一個就是信號不好，也連接異常了一次
所以，推測你說的連接異常，就是第二點的狀況，可以再檢查一下
页:
[1]