I followed the advice to enable the 2.4 GHz network from the unit, which does broadcast after deleting the upstream WLAN network and rebooting the unit :tada:. Workaround achieved, thank you!!

Something is a little weird with the 5 GHz network though, I’m hoping the root issue can be resolved. Thinking it’s related to DFS, I started playing around with the DFS settings in the web UI. The upstream WLAN is on 5 GHz channel 100, which is a DFS channel.

I disabled Allow Repeat DFS Channels on Repeater Options

The router says it’s not connected to the upstream WLAN, but my phone connected to the upstream WLAN sees the router on the LAN, and can ping it. My laptop is connected to the 2.4 GHz network from the unit, and I have internet access. So the unit is able to join the upstream WLAN on a DFS channel, and route traffic from the downstream 2.4 GHz WLAN to the upstream 5 GHz DFS WLAN, but shows a connection failed error in the UI.

The unit is still not broadcasting its own 5 GHz network, regardless of the Allow DFS Channel setting enabled or disabled on the 5 GHz network settings on the Wireless page.

I logged into LuCI just to get the logs, which show a lot of these events repeated:

Tue Nov 1 12:51:16 2022 daemon.warn hostapd: Failed to check if DFS is required; ret=-1
Tue Nov 1 12:51:16 2022 daemon.warn hostapd: Failed to check if DFS is required; ret=-1
Tue Nov 1 12:51:16 2022 daemon.info repeater: (/usr/sbin/repeater:1095) Scan starting…
Tue Nov 1 12:51:16 2022 daemon.info repeater: (/usr/sbin/repeater:1179) wlan-sta0: scan…SFR_35E0_5GHZ
Tue Nov 1 12:51:21 2022 daemon.info repeater: (/usr/sbin/repeater:1220) wlan-sta0: found 4 networks
Tue Nov 1 12:51:21 2022 daemon.info repeater: (/usr/sbin/repeater:1111) scan finished
Tue Nov 1 12:51:22 2022 daemon.warn hostapd: Failed to check if DFS is required; ret=-1
Tue Nov 1 12:51:22 2022 daemon.warn hostapd: Failed to check if DFS is required; ret=-1
Tue Nov 1 12:51:24 2022 daemon.info repeater: (/usr/sbin/repeater:608) Switching…
Tue Nov 1 12:51:24 2022 daemon.err repeater: (/usr/sbin/repeater:481) skip bss with dfs channel: SFR_35E0_5GHZ 6C:61:F4:41:35:E5 100
Tue Nov 1 12:51:24 2022 daemon.err repeater: (/usr/sbin/repeater:617) not found matched BSS for ‘SFR_35E0_5GHZ’
Tue Nov 1 12:51:24 2022 daemon.err repeater: (/usr/sbin/repeater:564) not found available network, re-scan in 57 seconds…
Tue Nov 1 12:51:28 2022 daemon.warn hostapd: Failed to check if DFS is required; ret=-1
Tue Nov 1 12:51:28 2022 daemon.warn hostapd: Failed to check if DFS is required; ret=-1

I tried to edit my original post to add this, but it seems that editing is locked?

  • Device Model
    ** GL-AXT1800 / Slate AX
  • Firmware version
    ** v4.0.3
  • Screenshots
    ** Above
  • Network topology diagram
    ** AirBnB host Wi-Fi router > Slate > Laptop
    ** AirBnB host Wi-Fi router > Phone
  • Problem description
    ** Slate router doesn’t broadcast its 5 GHz Wi-Fi network when not connected to an upstream network, likely due to DFS logic implementation
    ** Slate router UI doesn’t accurately reflect upstream WLAN connectivity status, in either error messages or not
    ** Deleting a wireless network from the Internet > Repeater > Join WLAN menu does not prevent the unit from connecting to the wireless network after a reboot