Menu
What's new
By:
Filters Better Search

My system log 9-12-2020

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Lee MacMillan

Lee MacMillan

Senior Member
This is typical of a daily system log from my AC66U-B1 running the latest Asus firmware. Just wondering if this is typical. It looks like most of the items are wireless devices connecting and disconnecting. My main computer (Windows 10) is attached via ethernet cable and it is put in sleep mode when not in use. It is usually turned on between 8 and 9 a.m. and shut down between 10 and 10:30 p.m. I have 12-15 wireless devices attached but rarely are more than 2 or 3 active at once. I have a list of the MAC addresses of all my devices (or so I thought) but there are a couple addresses I can't identify. I guess I have more work to do on that list! I find it a little odd that a couple devices that get used every day (a Roku and another Samsung TV) don't appear in the log. I had to delete quite a few (redundant) lines to get under the 10000 character message limit.

Sep 12 00:02:04 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 34:6F:92:0D:B4:68, status: Successful (0) (Sensi wireless thermostat)
Sep 12 00:02:04 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 34:6F:92:0D:B4:68, status: Successful (0)
Sep 12 03:17:32 ahs: [read_json]Update ahs JSON file.
Sep 12 03:17:49 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 54:60:09:E0:E5:B8, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 03:18:02 ahs: [read_json]Update ahs JSON file.
Sep 12 03:18:09 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 54:60:09:E0:E5:B8, status: Successful (0) (Chromecast audio)
Sep 12 03:18:09 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 54:60:09:E0:E5:B8, status: Successful (0)
Sep 12 03:18:33 ahs: [read_json]Update ahs JSON file.
Sep 12 03:54:35 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0) (Kindle)
Sep 12 03:54:35 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 03:55:35 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 03:55:35 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 04:05:47 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 10:62:E5:95:5E:7A, status: 0, reason: Disassociated due to inactivity (4) (HP printer)
Sep 12 08:53:46 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth F8:0F:F9:F4:EA:9E, status: Successful (0) (my Google Pixel 3a)
Sep 12 08:53:46 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc F8:0F:F9:F4:EA:9E, status: Successful (0)
Sep 12 09:28:14 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth 58:CB:52:96:9D:50, status: Successful (0) (my wife's Google Pixel 3a)
Sep 12 09:28:14 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc 58:CB:52:96:9D:50, status: Successful (0)
Sep 12 09:47:04 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind F8:0F:F9:F4:EA:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 09:49:19 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth F8:0F:F9:F4:EA:9E, status: Successful (0)
Sep 12 09:49:19 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc F8:0F:F9:F4:EA:9E, status: Successful (0)
Sep 12 09:52:58 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 14:BB:6E:05:A6:27, status: Successful (0) (Samsung TV)
Sep 12 09:52:58 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 14:BB:6E:05:A6:27, status: Successful (0)
Sep 12 13:29:37 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 8A:13:98:38:6A:41, status: Successful (0) ???
Sep 12 13:29:37 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 8A:13:98:38:6A:41, status: Successful (0)
Sep 12 13:31:08 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8A:13:98:38:6A:41, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 15:39:39 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth E0:9D:31:17:10:54, status: Successful (0) ???
Sep 12 15:39:39 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc E0:9D:31:17:10:54, status: Successful (0)
Sep 12 15:49:43 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 15:49:43 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 15:56:02 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind E0:9D:31:17:10:54, status: 0, reason: Unspecified reason (1)
Sep 12 16:04:15 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 14:BB:6E:05:A6:27, status: Successful (0)
Sep 12 16:04:15 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 14:BB:6E:05:A6:27, status: Successful (0)
Sep 12 16:13:13 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth BC:76:5E:2F:84:47, status: Successful (0) (Samsung tablet)
Sep 12 16:13:13 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 16:13:13 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 16:56:09 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind E0:9D:31:17:10:54, status: 0, reason: Unspecified reason (1)
Sep 12 16:57:05 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 16:57:05 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 16:58:55 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 16:58:55 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 17:26:38 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 17:26:38 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 17:35:00 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind BC:76:5E:2F:84:47, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 17:36:40 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 17:36:40 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 18:42:01 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind BC:76:5E:2F:84:47, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 18:42:08 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 18:42:08 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 18:54:51 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 18:54:51 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 19:31:35 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 19:31:35 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 19:47:06 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 19:47:06 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 20:01:27 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 20:01:27 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 22:11:33 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind 58:CB:52:96:9D:50, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 22:12:58 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind F8:0F:F9:F4:EA:9E, status: 0, reason: Disassociated due to inactivity (4)
 
Post log output inside of a CODE block to make it more readable. Otherwise, that all looks normal.
 
Lee MacMillan said:
This is typical of a daily system log from my AC66U-B1 running the latest Asus firmware. Just wondering if this is typical. It looks like most of the items are wireless devices connecting and disconnecting. My main computer (Windows 10) is attached via ethernet cable and it is put in sleep mode when not in use. It is usually turned on between 8 and 9 a.m. and shut down between 10 and 10:30 p.m. I have 12-15 wireless devices attached but rarely are more than 2 or 3 active at once. I have a list of the MAC addresses of all my devices (or so I thought) but there are a couple addresses I can't identify. I guess I have more work to do on that list! I find it a little odd that a couple devices that get used every day (a Roku and another Samsung TV) don't appear in the log. I had to delete quite a few (redundant) lines to get under the 10000 character message limit.

Sep 12 00:02:04 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 34:6F:92:0D:B4:68, status: Successful (0) (Sensi wireless thermostat)
Sep 12 00:02:04 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 34:6F:92:0D:B4:68, status: Successful (0)
Sep 12 03:17:32 ahs: [read_json]Update ahs JSON file.
Sep 12 03:17:49 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 54:60:09:E0:E5:B8, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 03:18:02 ahs: [read_json]Update ahs JSON file.
Sep 12 03:18:09 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 54:60:09:E0:E5:B8, status: Successful (0) (Chromecast audio)
Sep 12 03:18:09 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 54:60:09:E0:E5:B8, status: Successful (0)
Sep 12 03:18:33 ahs: [read_json]Update ahs JSON file.
Sep 12 03:54:35 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0) (Kindle)
Sep 12 03:54:35 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 03:55:35 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 03:55:35 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 04:05:47 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 10:62:E5:95:5E:7A, status: 0, reason: Disassociated due to inactivity (4) (HP printer)
Sep 12 08:53:46 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth F8:0F:F9:F4:EA:9E, status: Successful (0) (my Google Pixel 3a)
Sep 12 08:53:46 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc F8:0F:F9:F4:EA:9E, status: Successful (0)
Sep 12 09:28:14 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth 58:CB:52:96:9D:50, status: Successful (0) (my wife's Google Pixel 3a)
Sep 12 09:28:14 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc 58:CB:52:96:9D:50, status: Successful (0)
Sep 12 09:47:04 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind F8:0F:F9:F4:EA:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 09:49:19 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth F8:0F:F9:F4:EA:9E, status: Successful (0)
Sep 12 09:49:19 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc F8:0F:F9:F4:EA:9E, status: Successful (0)
Sep 12 09:52:58 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 14:BB:6E:05:A6:27, status: Successful (0) (Samsung TV)
Sep 12 09:52:58 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 14:BB:6E:05:A6:27, status: Successful (0)
Sep 12 13:29:37 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 8A:13:98:38:6A:41, status: Successful (0) ???
Sep 12 13:29:37 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 8A:13:98:38:6A:41, status: Successful (0)
Sep 12 13:31:08 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8A:13:98:38:6A:41, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 15:39:39 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth E0:9D:31:17:10:54, status: Successful (0) ???
Sep 12 15:39:39 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc E0:9D:31:17:10:54, status: Successful (0)
Sep 12 15:49:43 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 15:49:43 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 15:56:02 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind E0:9D:31:17:10:54, status: 0, reason: Unspecified reason (1)
Sep 12 16:04:15 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 14:BB:6E:05:A6:27, status: Successful (0)
Sep 12 16:04:15 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 14:BB:6E:05:A6:27, status: Successful (0)
Sep 12 16:13:13 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth BC:76:5E:2F:84:47, status: Successful (0) (Samsung tablet)
Sep 12 16:13:13 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 16:13:13 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 16:56:09 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind E0:9D:31:17:10:54, status: 0, reason: Unspecified reason (1)
Sep 12 16:57:05 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 16:57:05 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 16:58:55 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 16:58:55 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 17:26:38 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 17:26:38 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc BC:76:5E:2F:84:47, status: Successful (0)
Sep 12 17:35:00 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind BC:76:5E:2F:84:47, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 17:36:40 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 17:36:40 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 18:42:01 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind BC:76:5E:2F:84:47, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 18:42:08 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 18:42:08 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 18:54:51 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 18:54:51 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 19:31:35 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 19:31:35 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 19:47:06 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth F0:81:73:B7:66:24, status: Successful (0)
Sep 12 19:47:06 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc F0:81:73:B7:66:24, status: Successful (0)
Sep 12 20:01:27 syslog: WLCEVENTD wlceventd_proc_event(481): eth1: Disassoc F0:81:73:B7:66:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep 12 20:01:27 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind F0:81:73:B7:66:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 22:11:33 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind 58:CB:52:96:9D:50, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Sep 12 22:12:58 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind F8:0F:F9:F4:EA:9E, status: 0, reason: Disassociated due to inactivity (4)
Click to expand...
As said by Colin, looks like typical Asus factory firmware log
 
Thanks for the replies. I did figure out that one of the MAC addresses I couldn't identify is my Lenovo laptop (I had it written down incorrectly in my list). The other one is identified as "others" in my Asus router Android app. Still trying to figure that one out.
 
Lee MacMillan said:
Thanks for the replies. I did figure out that one of the MAC addresses I couldn't identify is my Lenovo laptop (I had it written down incorrectly in my list). The other one is identified as "others" in my Asus router Android app. Still trying to figure that one out.
Click to expand...
It may help to search for the vendor of the network interface by MAC address:
uic.win

MAC Address Lookup

Vendor information can be displayed from the MAC address. Vendor information is updated daily.
uic.win uic.win
Or login to the router GUI, the router does the search for you :)
 
You must log in or register to reply here.

Similar threads

R
Failed wifi connections still logged as successful?
Replies
2
Views
242
SeriousFamily
SeriousFamily
TheLyppardMan
Lots of recurring entries in the system log
Replies
11
Views
628
TheLyppardMan
TheLyppardMan
T
ASUS RT-AX55U\56v2 Firmware version 9.0.0.4.386_52297-g05e2188
Replies
3
Views
327
Tech9
Tech9
J
Help with system logs - Constant wifi drops
Replies
4
Views
1K
bloomwow
B
slurmsmckenzie
RT-AX86U - system log spam from Tuya Smart device
2 3
Replies
55
Views
4K
slurmsmckenzie
slurmsmckenzie
Similar threads
Thread starter Title Forum Replies Date
TheLyppardMan Lots of recurring entries in the system log ASUSWRT - Official 11
slurmsmckenzie RT-AX86U - system log spam from Tuya Smart device ASUSWRT - Official 55
TheLyppardMan System Log - what do these recurring entries mean? ASUSWRT - Official 3
TheLyppardMan What are these system log entries? ASUSWRT - Official 12
F Ping target - from Administration/System ASUSWRT - Official 2
J Help with system logs - Constant wifi drops ASUSWRT - Official 4
P AiMesh creates Open System connection on 6GHz range ASUSWRT - Official 7
R ASUS RT-AX88U Router Is showing Ethernet Ports Notice under Network Map -> System Status -> Status ASUSWRT - Official 20
L Where can I find a comprehensive guide for the Asus WRT operating system, it has so many options, many I don't understand their purpose ASUSWRT - Official 8
P Asus Router tuf ax4200 log enquiry ASUSWRT - Official 0

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 767 (members: 15, guests: 752)
Top