ET8 Disconnecting Devices

agentred

New Around Here
Hi all,

Apologies if this isn't the right section but I'm having trouble with my wifi dropping/ignoring devices. I have an ethernet backhaul mesh with two ET8's and (until recently) an RT-AX55 all running stock firmware. I've had some trouble with devices not connecting properly (Nest Protect, Nest Audio) and I thought it was just the devices being weird. But now I'm thinking it's the Asus setup that's creating a problem.

To start at the beginning, my ET8's and AX55 were working fine for about a month. At some point (I don't know when) the AX55 node started showing as 'offline' in the Asus app. I tried resetting it a few times, but it still showed as 'offline'. Devices near the Node would connect to the wifi, but not have any internet access, give a weird ip address (169.254.185.xx while my regular network is 192.168.50.X).

The only solution I found was to unplug the AX55, then devices would reconnect to the ET8's. I did a factory reset of the AX55 and added it as a node again in the app. It took a very long time to connect, and then instantly switched to offline. Same thing - devices connect to it but don't get internet. Repeated the reset, same thing.

The reason I mentioned the google devices earlier was that the same thing happens with them. I can add them to the wifi, but then they instantly appear as offline in the Nest app.

So I'm not sure what's going on. Is this a known issue? Is there a setting that can make this smoother? Nothing should've changed in the network. Is there any solution short of factory resetting the main ET8? I have a lot of devices and don't want to manually add them all again...

Sorry for the long ramble and thanks for any input!

Also wanted to add the system log. I basically did a factory reset and collected the logs from the point the device (24:4B:FE:1D:44:D0) was detected. Within about a minute it seems to get kicked out. WHy is it giving high RSSI's when the backhaul is supposed to be ethernet? Please let me know if this is helpful or if I should collect other logs or contact Asus etc., thank you!


Code:
Jun 24 21:42:43 wlceventd: wlceventd_proc_event(527): eth4: Auth 24:4B:FE:1D:44:D0, status: Successful (0), rssi:0
Jun 24 21:42:43 wlceventd: wlceventd_proc_event(556): eth4: Assoc 24:4B:FE:1D:44:D0, status: Successful (0), rssi:-73
Jun 24 21:42:47 wlceventd: wlceventd_proc_event(491): eth4: Deauth_ind 24:4B:FE:1D:44:D0, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-73
Jun 24 21:42:48 wlceventd: wlceventd_proc_event(491): eth4: Deauth_ind 24:4B:FE:1D:44:D0, status: 0, reason: Previous authentication no longer valid (2), rssi:-73
Jun 24 21:42:48 wlceventd: wlceventd_proc_event(527): eth5: Auth 24:4B:FE:1D:44:D4, status: Successful (0), rssi:-89
Jun 24 21:42:48 wlceventd: wlceventd_proc_event(556): eth5: Assoc 24:4B:FE:1D:44:D4, status: Successful (0), rssi:-89
Jun 24 21:42:49 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 24:4B:FE:1D:44:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:42:52 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 24:4B:FE:1D:44:D4, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-89
Jun 24 21:42:53 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 24:4B:FE:1D:44:D4, status: 0, reason: Previous authentication no longer valid (2), rssi:-89
Jun 24 21:42:54 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 24:4B:FE:1D:44:D4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:42:54 wlceventd: wlceventd_proc_event(527): eth4: Auth 24:4B:FE:1D:44:D0, status: Successful (0), rssi:0
Jun 24 21:42:54 wlceventd: wlceventd_proc_event(556): eth4: Assoc 24:4B:FE:1D:44:D0, status: Successful (0), rssi:-73
Jun 24 21:43:18 rc_service: cfg_server 2052:notify_rc start_bsd
Jun 24 21:43:18 cfg_server:  event: wl_chanspec_changed_action
Jun 24 21:43:18 cfg_server: skip event due no chanlist update
Jun 24 21:43:20 wlceventd: wlceventd_proc_event(508): wds0.0.1: Disassoc 24:4B:FE:1D:44:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:20 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 24:4B:FE:1D:44:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:20 kernel: wl0: set timeout 5 secs to wait dev reg finish
Jun 24 21:43:20 kernel: Flushing net_device wds0.0.1.
Jun 24 21:43:22 wlceventd: wlceventd_proc_event(527): eth4: Auth 24:4B:FE:1D:44:D0, status: Successful (0), rssi:0
Jun 24 21:43:22 wlceventd: wlceventd_proc_event(556): eth4: Assoc 24:4B:FE:1D:44:D0, status: Successful (0), rssi:-73
Jun 24 21:43:24 wlceventd: wlceventd_proc_event(527): eth5: Auth 24:4B:FE:1D:44:D4, status: Successful (0), rssi:0
Jun 24 21:43:24 wlceventd: wlceventd_proc_event(556): eth5: Assoc 24:4B:FE:1D:44:D4, status: Successful (0), rssi:-89
Jun 24 21:43:26 wlceventd: wlceventd_proc_event(491): eth4: Deauth_ind 24:4B:FE:1D:44:D0, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-72
Jun 24 21:43:27 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 24:4B:FE:1D:44:D4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:27 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 24:4B:FE:1D:44:D4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:27 wlceventd: wlceventd_proc_event(491): eth4: Deauth_ind 24:4B:FE:1D:44:D0, status: 0, reason: Previous authentication no longer valid (2), rssi:-72
Jun 24 21:43:28 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 24:4B:FE:1D:44:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:29 roamast: [EXAP]ignore static clients 24:4B:FE:1D:44:D4
Jun 24 21:43:31 wlceventd: wlceventd_proc_event(527): eth4: Auth 24:4B:FE:1D:44:D0, status: Successful (0), rssi:0
Jun 24 21:43:31 wlceventd: wlceventd_proc_event(556): eth4: Assoc 24:4B:FE:1D:44:D0, status: Successful (0), rssi:-70
Jun 24 21:43:38 wlceventd: wlceventd_proc_event(508): wds0.0.1: Disassoc 24:4B:FE:1D:44:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:38 kernel: wl0: set timeout 5 secs to wait dev reg finish
Jun 24 21:43:38 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 24:4B:FE:1D:44:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 21:43:38 kernel: Flushing net_device wds0.0.1.
 
Last edited:

OzarkEdge

Part of the Furniture
Hi all,

Apologies if this isn't the right section but I'm having trouble with my wifi dropping/ignoring devices. I have an ethernet backhaul mesh with two ET8's and (until recently) an RT-AX55 all running stock firmware. I've had some trouble with devices not connecting properly (Nest Protect, Nest Audio) and I thought it was just the devices being weird. But now I'm thinking it's the Asus setup that's creating a problem.

To start at the beginning, my ET8's and AX55 were working fine for about a month. At some point (I don't know when) the AX55 node started showing as 'offline' in the Asus app. I tried resetting it a few times, but it still showed as 'offline'. Devices near the Node would connect to the wifi, but not have any internet access, give a weird ip address (169.254.185.xx while my regular network is 192.168.50.X).

The only solution I found was to unplug the AX55, then devices would reconnect to the ET8's. I did a factory reset of the AX55 and added it as a node again in the app. It took a very long time to connect, and then instantly switched to offline. Same thing - devices connect to it but don't get internet. Repeated the reset, same thing.

The reason I mentioned the google devices earlier was that the same thing happens with them. I can add them to the wifi, but then they instantly appear as offline in the Nest app.

So I'm not sure what's going on. Is this a known issue? Is there a setting that can make this smoother? Nothing should've changed in the network. Is there any solution short of factory resetting the main ET8? I have a lot of devices and don't want to manually add them all again...

Sorry for the long ramble and thanks for any input!

Google suggests 169.254.185.xx means 'the client has an Ethernet link but cannot reach the DHCP server'. If so, then I would start with cabling... try a known good cable... and perhaps progress to recommissioning your network... you may not get past a hardware fault... worked... then stopped working.

OE
 

agentred

New Around Here
Google suggests 169.254.185.xx means 'the client has an Ethernet link but cannot reach the DHCP server'. If so, then I would start with cabling... try a known good cable... and perhaps progress to recommissioning your network... you may not get past a hardware fault... worked... then stopped working.

OE

Thanks for the idea!! Unfortunately... no luck. Tried a different cable and a different socket, same issue, same error in the log file.
 

L&LD

Part of the Furniture
Have you tried simply powering all network equipment down (fully) and then restarting them in order?

 

Latest threads

Sign Up For SNBForums Daily Digest

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