Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
  1. #1
    New ROGer Array
    Join Date
    Jan 2022
    Reputation
    10
    Posts
    4

    GT-AX11000 disconnecting devices from the internet daily

    I am having an issue with my router where it appears to be deauthorizing all the devices on my network at least once per day, and thus causing a loss of connection for a few minutes.

    I have updated the routers firmware, replaced my cable modem to rule it out, replaced my network cable between the cable modem and the router, and so far am still suffering this seemingly random disconnect issue.

    My system log is as follows for today:


    Feb 2 03:37:39 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-75
    Feb 2 03:37:40 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 0C:AE:7D:C8:66:02, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 04:02:40 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 04:02:40 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-74
    Feb 2 04:02:44 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 04:25:21 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-53
    Feb 2 04:25:21 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-53
    Feb 2 04:25:22 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 04:4E:AF:8B:E9:66, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 04:25:25 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:0
    Feb 2 04:25:25 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-53
    Feb 2 04:44:23 vpnserver1[25038]: 162.142.125.136:47835 TLS: Initial packet from [AF_INET]162.142.125.136:47835 (via [AF_INET]72.200.70.37%eth0), sid=4d658221 07fcfd52
    Feb 2 04:44:39 vpnserver1[25038]: 162.142.125.8:42238 TLS: Initial packet from [AF_INET]162.142.125.8:42238 (via [AF_INET]72.200.70.37%eth0), sid=3dab9c40 8f525e64
    Feb 2 04:45:23 vpnserver1[25038]: 162.142.125.136:47835 [UNDEF] Inactivity timeout (--ping-restart), restarting
    Feb 2 04:45:23 vpnserver1[25038]: 162.142.125.136:47835 SIGUSR1[soft,ping-restart] received, client-instance restarting
    Feb 2 04:45:39 vpnserver1[25038]: 162.142.125.8:42238 [UNDEF] Inactivity timeout (--ping-restart), restarting
    Feb 2 04:45:39 vpnserver1[25038]: 162.142.125.8:42238 SIGUSR1[soft,ping-restart] received, client-instance restarting
    Feb 2 05:03:13 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 05:03:13 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-74
    Feb 2 05:03:18 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 05:48:13 WATCHDOG: [FAUPGRADE][auto_firmware_check7458)]do webs_update
    Feb 2 05:48:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7476)]retrieve firmware information
    Feb 2 05:48:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7491)]fimrware update check first time
    Feb 2 05:48:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7524)]no need to upgrade firmware
    Feb 2 05:48:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7458)]do webs_update
    Feb 2 05:48:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7476)]retrieve firmware information
    Feb 2 05:48:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7496)]fimrware update check once
    Feb 2 05:49:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7458)]do webs_update
    Feb 2 05:49:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7476)]retrieve firmware information
    Feb 2 05:49:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7496)]fimrware update check once
    Feb 2 05:49:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7458)]do webs_update
    Feb 2 05:49:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7476)]retrieve firmware information
    Feb 2 05:49:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7491)]fimrware update check first time
    Feb 2 05:49:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7524)]no need to upgrade firmware
    Feb 2 05:59:09 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 05:59:09 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-75
    Feb 2 05:59:14 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 06:58:18 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 06:58:18 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-76
    Feb 2 06:58:32 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 07:26:28 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:26:28 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:26:28 miniupnpd[25014]: upnpevents_processfds: 0x126ad0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd073f1 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/wqhpgipvsb
    Feb 2 07:26:28 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:26:28 miniupnpd[25014]: upnpevents_processfds: 0x123378, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0cead after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/chspkilclw
    Feb 2 07:40:18 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:40:18 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:40:18 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0c675 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/prrzzjbacf
    Feb 2 07:40:18 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:40:18 miniupnpd[25014]: upnpevents_processfds: 0x122fd0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd03004 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/lmeiltaaak
    Feb 2 07:49:24 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 07:49:24 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-52
    Feb 2 07:49:24 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-52
    Feb 2 07:54:23 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind C2:56:4E:51:F6:25, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-61
    Feb 2 07:54:23 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind C2:56:4E:51:F6:25, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-61
    Feb 2 07:54:24 wlceventd: wlceventd_proc_event(508): eth6: Disassoc C2:56:4E:51:F6:25, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 07:56:26 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:56:26 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:56:26 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd03f32 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/gfainqcnno
    Feb 2 07:56:26 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 07:56:26 miniupnpd[25014]: upnpevents_processfds: 0x122fd0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd06e1d after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/wyvubqmqzn
    Feb 2 08:09:36 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 08:09:36 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-77
    Feb 2 08:10:10 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-76
    Feb 2 08:10:10 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-76
    Feb 2 08:10:11 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 0C:AE:7D:C8:66:02, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 08:11:01 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 10 mbps full duplex
    Feb 2 08:11:02 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
    Feb 2 08:11:04 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
    Feb 2 08:12:32 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:12:32 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:12:32 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd036d0 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/eazeeboahh
    Feb 2 08:12:32 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:12:32 miniupnpd[25014]: upnpevents_processfds: 0x122fd0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd07945 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/zhqzbnmehp
    Feb 2 08:12:34 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
    Feb 2 08:12:36 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
    Feb 2 08:13:47 wlceventd: wlceventd_proc_event(527): eth7: Auth 38E:AD:21:1D:58, status: Successful (0), rssi:0
    Feb 2 08:13:47 wlceventd: wlceventd_proc_event(556): eth7: Assoc 38E:AD:21:1D:58, status: Successful (0), rssi:-41
    Feb 2 08:24:31 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-52
    Feb 2 08:24:31 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-52
    Feb 2 08:24:32 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 04:4E:AF:8B:E9:66, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 08:24:34 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:0
    Feb 2 08:24:34 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-51
    Feb 2 08:28:41 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:28:42 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:28:42 miniupnpd[25014]: upnpevents_processfds: 0x121ff0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0506a after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/atfuyouttv
    Feb 2 08:28:42 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:28:42 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0628f after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/oopfqjmddg
    Feb 2 08:44:47 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:44:47 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:44:47 miniupnpd[25014]: upnpevents_processfds: 0x121ff0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0b1f4 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/bohkwgijla
    Feb 2 08:44:47 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 08:44:47 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd00f69 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/wuqzfwwyvr
    Feb 2 09:00:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 09:00:56 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-76
    Feb 2 09:00:56 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:00:56 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:00:56 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0d730 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/jdtvulebua
    Feb 2 09:00:56 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:00:56 miniupnpd[25014]: upnpevents_processfds: 0x126ad0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd07839 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/ztghgxnieh
    Feb 2 09:01:00 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 09:17:06 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:17:06 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:17:06 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0e8b5 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/vbyendrghr
    Feb 2 09:17:06 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:17:06 miniupnpd[25014]: upnpevents_processfds: 0x126ad0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0d205 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/ubmcojsahi
    Feb 2 09:33:11 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:33:11 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:33:11 miniupnpd[25014]: upnpevents_processfds: 0x126698, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd06fff after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/sgdpebivqf
    Feb 2 09:33:11 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:33:11 miniupnpd[25014]: upnpevents_processfds: 0x126ad0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd058d0 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/ozeujuflbu
    Feb 2 09:41:22 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 09:41:22 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-51
    Feb 2 09:41:22 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-51
    Feb 2 09:41:36 wlceventd: wlceventd_proc_event(508): eth6: Disassoc D8:C0:A6:58:91:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 09:41:36 wlceventd: wlceventd_proc_event(508): eth6: Disassoc D8:C0:A6:58:91:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 09:41:36 wlceventd: wlceventd_proc_event(527): eth6: Auth D8:C0:A6:58:91:E9, status: Successful (0), rssi:0
    Feb 2 09:41:36 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc D8:C0:A6:58:91:E9, status: Successful (0), rssi:-44
    Feb 2 09:41:59 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind D8:C0:A6:58:91:E9, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
    Feb 2 09:41:59 wlceventd: wlceventd_proc_event(508): eth6: Disassoc D8:C0:A6:58:91:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 09:42:00 wlceventd: wlceventd_proc_event(556): eth6: Assoc D8:C0:A6:58:91:E9, status: Successful (0), rssi:-44
    Feb 2 09:42:57 wlceventd: wlceventd_proc_event(508): eth6: Disassoc D8:C0:A6:58:91:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Feb 2 09:42:57 wlceventd: wlceventd_proc_event(508): eth6: Disassoc D8:C0:A6:58:91:E9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

    Feb 2 09:49:21 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:49:21 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:49:21 miniupnpd[25014]: upnpevents_processfds: 0x11a5d0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd05eb1 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/prhxmuulsx
    Feb 2 09:49:21 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 09:49:21 miniupnpd[25014]: upnpevents_processfds: 0x124f80, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd09337 after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/tixfzqriyp
    Feb 2 09:57:22 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 09:57:22 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-76
    Feb 2 09:57:27 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 10:05:24 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 10:05:24 miniupnpd[25014]: upnp_event_process_notify: connect(192.168.50.106:2869): Connection timed out
    Feb 2 10:05:24 miniupnpd[25014]: upnpevents_processfds: 0x11e7e0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3fd0b88b after an ERROR cb: http://192.168.50.106:2869/upnp/eventing/sqiezlczhn



    I was disconnected this morning at 09:41-09:42 All of my network devices were disconnected from the internet while this was happening and my internet light on the router was red for the duration of it.



    Does anyone have any idea what is going on here, and how to fix this? My wife and I both work from home, so this is extremely important.

  2. #2
    New ROGer Array
    Join Date
    Jan 2022
    Reputation
    10
    Posts
    4

    On the 1/31 I also caught this event (same result, total disconnect)

    Jan 31 16:05:59 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Unspecified reason (1), rssi:-48
    Jan 31 16:05:59 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-48
    Jan 31 16:05:59 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-48
    Jan 31 16:12:24 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-50
    Jan 31 16:12:24 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-50
    Jan 31 16:12:32 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 04:4E:AF:8B:E9:66, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

  3. #3
    New ROGer Array
    Join Date
    Jan 2022
    Reputation
    10
    Posts
    4

    Happened again at 12:11 today

    Feb 2 12:11:26 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Unspecified reason (1), rssi:-52
    Feb 2 12:11:26 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-52
    Feb 2 12:11:26 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-52
    Feb 2 12:11:39 wlceventd: wlceventd_proc_event(527): eth6: Auth 0C:AE:7D:C8:66:02, status: Successful (0), rssi:0
    Feb 2 12:11:39 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0C:AE:7D:C8:66:02, status: Successful (0), rssi:-74
    Feb 2 12:12:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-74
    Feb 2 12:12:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:AE:7D:C8:66:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-74
    Feb 2 12:12:41 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 0C:AE:7D:C8:66:02, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0




    ----------------------------------------------------------------
    Update:

    Asus tech support had me turn on Jumbo Packets and disable beam forming, which totally cut the router off from the internet.

    I have since done a hard factory reset. Will update if problems ensue.

    Update 2: resetup my DDNS and almost as soon as I did it this happened:

    Feb 2 23:00:38 disk_monitor: Got SIGALRM...
    Feb 2 16:03:48 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 04:4E:AF:8B:E9:66, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 2 16:03:48 wlceventd: wlceventd_proc_event(527): eth6: Auth 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-53
    Feb 2 16:03:48 wlceventd: wlceventd_proc_event(556): eth6: Assoc 04:4E:AF:8B:E9:66, status: Successful (0), rssi:-53
    Feb 2 16:05:13 wlceventd: wlceventd_proc_event(527): eth6: Auth B2:F2:99:75:33:46, status: Successful (0), rssi:0
    Feb 2 16:05:13 wlceventd: wlceventd_proc_event(556): eth6: Assoc B2:F2:99:75:33:46, status: Successful (0), rssi:-82

    I then lost my internet connection across all devices... again.
    Last edited by ROGBEAR; 02-02-2022 at 11:07 PM.

  4. #4
    TeamROG Moderator Array xeromist PC Specs
    xeromist PC Specs
    Laptop (Model)Intel NUC laptop LAPQC71D
    MotherboardROG Crosshair VIII Dark Hero
    ProcessorAMD 5800X
    Memory (part number)32GB G.Skill Ripjaws V 3600
    Graphics Card #1ROG Strix RTX3090Ti
    Sound CardSound Blaster Z
    MonitorAORUS FV43U
    Storage #1Samsung 970 Pro 512GB
    CPU CoolerCustom loop
    CaseBeQuiet Dark Base Pro 900 V2
    Power SupplyCorsair HX1000
    Keyboard ROG Strix Flare II Animate
    Mouse ROG Chakram X
    Headset Steelseries Arctis Pro Wireless
    Mouse Pad ROG Scabbard
    Headset/Speakers Logitech z906 5.1
    Network RouterpfSense/OPNsense
    xeromist's Avatar
    Join Date
    Jul 2010
    Reputation
    436
    Posts
    8,625

    Do you have any devices hard wired and do they have issues?
    * Support disease research with Folding@Home *

    < < < Click the drop-down above my avatar for my PC specs!

  5. #5
    New ROGer Array
    Join Date
    Jan 2022
    Reputation
    10
    Posts
    4

    Quote Originally Posted by xeromist View Post
    Do you have any devices hard wired and do they have issues?
    Yes, this affects both wired and wireless devices, at the same time.

    Update:

    post factory reset the problem seems to have accelerated. It lost internet three times over the evening (same error messages in log)
    Last edited by ROGBEAR; 02-03-2022 at 03:46 PM.

  6. #6
    ROG Enthusiast Array
    Join Date
    Aug 2021
    Reputation
    10
    Posts
    73

    Quote Originally Posted by ROGBEAR View Post
    Yes, this affects both wired and wireless devices, at the same time.

    Update:

    post factory reset the problem seems to have accelerated. It lost internet three times over the evening (same error messages in log)
    try this..............but there may also be a newer beta coming soon?
    https://rog.asus.com/forum/showthrea...a-3004-386-rc3

  7. #7
    ROG Guru: Orange Belt Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    324

    AXE11000 here that I just received last Thursday. Updated with latest firmware and (Automatic updates set for 3 am). Service speed upgraded to 1Gbps hence purchase of upgraded router. RT-AC68U moved to 2nd floor for AiMesh. First tried the blue WAN (only) port 2.5 G port connected to in wall wire to 16 port central switch. Maximum speed at 4 am was 940 Mbps downstream. My son complained of instability. I found two RJ-45 connected from router to the same 5 port switch!

    Moved modem wire to 2.5 G WAN/LAN and activated, disconnected the mistaken extra wire to the switch. (Technically I just removed it and filled the 4 router ports, don't really need the TV connected I left it disconnected). I switched Wi-Fi security setting to WPA-2/WPA-3 on both 2.4 and 5 GHz. (Downstream improved to 1083 Mbps maximum @ 6am if that matters).

    No more disconnecting from modem daily as I know....
    Last edited by jzchen; 02-07-2022 at 06:16 PM.

  8. #8
    ROG Guru: Orange Belt Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    324

    Sadly I spoke too soon. As I type on my phone's cellular connection the little WAN light on the router is red but the modem lights look normal. It appears to have shifted dropping the WAN connection to every morning! Sigh...

  9. #9
    ROG Guru: Orange Belt Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    324

    ISP acknowledged a wiring issue and ran new cable from pole to home. Said next step to find someone to run cable from service entry directly to modem. Have to find someone to do that for me, may be a problem from modem outwards....

  10. #10
    ROG Guru: Orange Belt Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    324

    I feel like I can pretty much confirm a signal issue on the service side as of yesterday. With my son and wife out of the house and one iPhone streaming the Olympics on Peacock to the TV, we had zero drops yesterday. There are two splitters to get the coax to a central location in the house. I can save one split if I connect the modem at the side of the house instead, but then router would literally be on the side wall of the house. Another possibility is run a new low loss cable as noted. Anyone know a good coax runner in the Los Angeles area? Also there are so many different types of coax, RG-6, RG-7, RG-11? Would one of those expensive sweep tested Belden cables help? Then I wouldn't even know if they are able connect properly. (Thank you in advance for any leads and/or advice)!

Page 1 of 2 1 2 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •