Flint 3 / GL-BE9300: IoT Wi-Fi Instability, VAP Create Error, and Camera Disconnections After Wi-Fi Changes

Hello,

I would like to report and ask for help regarding a Wi-Fi issue on my GL.iNet Flint 3 / GL-BE9300.

After changing Wi-Fi settings from the web interface, including regular Wi-Fi configuration and MLO settings, I started seeing instability on my IoT Wi-Fi network. The IoT SSID is bridged to br-iot, and the logs show that the IoT VAP/interface is being stopped and started again.

Relevant log points:

wifi.set_config
wifi.set_mlo_config

Later, the kernel log shows the IoT SSID being created on 5 GHz:

DES SSID SET=IoT
channel_cfreq: 5220

The IoT VAP/interface also appears to restart:

br-iot: port 3(wlan16) entered forwarding state
wlan_cfg80211_start_ap: Start wlan16
...
wlan_cfg80211_stop_ap: Stop wlan16
...
wlan_cfg80211_start_ap: Start wlan16

The main error I would like to ask about is this one:

VAP Create Error. Vap macaddr 94:83:c4:b4:78:b4 matches with already existing vap wlan1 with ID 1
WARNING: CPU: 0 PID: 5157 at ... osifp_create_wlan_vap
wlan vap failed

There are also repeated messages such as:

assoc req from dms not-supported sta
wlan_cfg80211_change_station: Ignore set station for ap vlan wlan06
Max BSS Idle enabled client

The affected devices are mainly IoT devices / Wi-Fi cameras. They associate, complete the WPA handshake, and receive DHCP leases, but then they disconnect and reconnect repeatedly. For example, one camera receives an IP address on br-iot, but then keeps disconnecting and sending DHCPDISCOVER requests again.

Example:

DHCPACK(br-iot) 192.168.10.122 f8:16:0c:0b:7f:90 Camera

I also noticed that one physical LAN port assigned to br-iot is flapping:

lan1 link down
br-iot: port 1(eth1.2) entered disabled state
lan1 link up, speed 100
br-iot: port 1(eth1.2) entered forwarding state

My questions are:

Is the VAP Create Error related to a known Qualcomm/QCA Wi-Fi driver issue on the Flint 3?
Can this be caused by MLO, MBSSID, multiple SSIDs, or virtual AP creation?
Is it recommended to disable 5 HHz IoT networks and keep IoT only on 2.4 GHz with WPA2?
Could the assoc req from dms not-supported sta messages explain why cameras are disconnecting?
Is the LAN1 link flapping related, or is it likely a separate physical cable/port issue?
What Wi-Fi settings are recommended for maximum compatibility with IoT cameras on the Flint 3?

My current suspicion is that the IoT network is unstable because of a combination of MLO/MBSSID/virtual AP handling and IoT clients that do not work well with MLO in Lan.

Thank you.

Hi

Sorry for the delayed reply.

Regarding the IoT Wi-Fi issue:
We have already added the IoT Wi-Fi in the v4.9.0 beta firmware. Could you please upgrade to this version and check whether the issue still persists?

Download link:

Upgrade guide:


Regarding the dms not-supported sta issue:
This is usually caused by limited compatibility on the IoT/Wi-Fi client device side. Please try the following suggestion and see whether it helps:


Regarding the LAN 1 disconnection issue:
At the moment, it is unclear whether this is related to the physical cable/port or something else.

Please try the following:

  1. Replace it with some different Ethernet cables that are known to work properly
  2. Connect the device to a different LAN port
  3. Insert an unmanaged switch between the device and the BE9300 to see whether it improves the situation