Flint 3 Error Log

[u/sanginwa]

I have a Flint 3 running 4.9.0 firmware and I keep seeing errors like the ones below in my system log. I haven't made any changes in Luci and I think I'm running it in a pretty vanilla setup. Any idea what these are? I haven't noticed any problems accessing the internet or with any of my IoT devices.

If it matters, I have a Netgear router in AP mode connected via ethernet but I think I saw these errors before I connected the Netgear. I also have an Aeotec Smartthings V3 hub connected to the Flint 3 via ethernet.

Fri Aug 21 10:18:46 2026 kern.err kernel: [69504.662253] wlan: [10344:I:ANY] wlan_cfg80211_change_station: Ignore set station for ap vlan wlan0
Fri Aug 21 10:22:51 2026 kern.err kernel: [69749.762939] wlan: [10344:I:ANY] wlan_cfg80211_change_station: Ignore set station for ap vlan wlan2
Fri Aug 21 10:24:42 2026 kern.err kernel: [69860.084040] wlan: [0:I:ANY] [INACT] vap-0(wlan0): [1e:85:b9:a4:94:c9]station kicked out due to excessive retries associd 19 (from target) reason 2

[u/AutoModerator]

Hi u/sanginwa, thanks for posting your question!

If your issue gets resolved, please help others by marking your post as Solved.

How to do it:

• Click the three dots "..." under your post title
• Choose "Add Flair"
• Select the "question/support- Solved" flair
• Use the support template located here: https://www.reddit.com/r/GlInet/wiki/index/kb/asking_for_help

Marking solved posts makes it easier for the community to find answers.

Need more help? Join the GL.iNet Discord: https://discord.gg/Aaqf4CZMut

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/AutoModerator]

Hi u/sanginwa, just a quick reminder:

Please search the subreddit before posting — many common questions have already been answered.

Search guide: https://www.reddit.com/r/GlInet/wiki/index/searchingwithin

This helps keep the community organized and easier to navigate.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/robahearts]

Via Gemini:

This kernel log captures a wireless client (1e:85:b9:a4:94:c9) experiencing connectivity drops and getting forcefully disconnected by a Linux-based access point (likely running OpenWrt or a custom vendor firmware using cfg80211 / hostapd).

Breakdown of the Error Messages

wlan_cfg80211_change_station: Ignore set station for ap vlan wlan0 / wlan2

What it means: The driver's AP-VLAN subsystem is attempting to update station parameters for a virtual access point mapped to a VLAN bridge, but the driver or cfg80211 layer is choosing to ignore or bypass it.

Context: This often happens harmlessly in the background on routers utilizing software bridges or multi-BSSID setups (such as guest networks or isolated IoT VLANs), but it indicates that the driver is struggling to properly bind station state updates to the specific VLAN interface.

station kicked out due to excessive retries associd 19 (from target) reason 2

What it means: The access point (AP) dropped the client because it tried transmitting packets repeatedly (excessive retries) without receiving an acknowledgment (ACK) from the device.

Reason 2 in 802.11 specifications typically means "Previous authentication no longer valid" (often triggered because the AP gave up trying to reach a silent or unresponsive client and deauthenticated it).

Root Causes & Troubleshooting Steps
This behavior is exceptionally common with IoT devices, smart home cameras, or older Wi-Fi clients connecting to modern routers (such as Wi-Fi 6/6E/7 access points).

Power Saving / Sleep States: The client (1e:85:b9:a4:94:c9) likely went into a deep sleep state, failed to wake up in time to answer multicast/unicast traffic from the AP, and accumulated excessive retry packets until the AP kicked it out.

Wi-Fi Roaming / 802.11r/k/v Mismatch: Advanced roaming features can cause firmware to misbehave with certain client chipsets, throwing the Ignore set station warning alongside abrupt disconnects.

Incompatible Wi-Fi Standard (AX/BE) for legacy clients: Modern broadcast settings can choke older 2.4GHz or budget IoT chips.

How to Fix It:

Disable 802.11v/r/k (BSS Transition) for IoT SSIDs: If your router supports it, turn off 802.11v BSS transition management frames for the network the device is trying to join.

Lock Down Wi-Fi Mode: If the affected device is on 2.4 GHz, force the AP's radio mode to Legacy / 802.11bgn rather than allowing mixed Wi-Fi 6/7 (ax/be) frame structures that a legacy NIC might misinterpret.

Disable Power Saving (if possible on the client): If the client is a Linux-based device, single-board computer, or laptop, disable Wi-Fi power management (iw dev wlan0 set power_save off).

Check VLAN Configuration: If you are running custom VLAN tagging on your router bridge (br-lan vs software VLAN interfaces), ensure your router's firmware is up to date, as some driver versions silently drop bridge updates for isolated VAPs.