Flint 4 4.11 beta 3 mesh issues

nemetharon · October 2, 2026, 4:24pm

Hi!

I have a setup where a flint 4 is a main router and a flint 3 is a mesh node. I updated the flint 4 from beta 1 to beta 3 and noticed that under mesh the flint 3 was disappeared and I only say the onboarding screen. So I tried to reset the flint 3 and add it again but wifi scan would not find it. I even tried ethernet backhaul but no luck. I have also noticed that under clients the “Connect to” column was empty everywhere (on beta1 it said Main router). So I downgraded back to beta 1 and the setup worked first time.

Can somebody please look into this? Did anyone experience something like this?

AI_bot · October 2, 2026, 4:26pm

Because the same Flint 4/Flint 3 topology works again after reverting only the Flint 4 to beta1, this is consistent with a possible beta3 regression or configuration-migration issue rather than a pairing-range problem.

Please provide the complete beta1 and beta3 build identifiers for the Flint 4, plus the Flint 3 firmware version. If you can reproduce the failure once more, export the Flint 4 log from System → Log immediately after the failed Wi-Fi scan or Ethernet onboarding attempt. Send the complete log privately to a GL.iNet support member rather than posting it publicly; the build details can be posted here. For now, remaining on the working beta1 build is the practical workaround.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

charles2 · October 13, 2026, 3:11am

Hi,

Thank you for sharing your findings.

We tested Flint 4 with firmware v4.11.0 Beta 3 locally and were able to discover a Flint 3 Mesh node through Wi-Fi scanning. So far, we haven't reproduced the node discovery issue you described.

To help us investigate further, could you please confirm a few details?

When upgrading from Beta 1 to Beta 3, did you choose to keep the existing configuration? Have you also tried resetting the Mesh configuration on Flint 4?
Is this issue consistently reproducible after upgrading from Beta 1 to Beta 3?

nemetharon · October 13, 2026, 6:49am

Thank you for your response!

Yes, I chose the keep the existing configuration option when upgrading from beta 1 to 3.

I will test whether doing the upgrade again will solve the issue, however I can only do that in the weekend, I will get back to you then.

I also have a memory leak issue that I have reported in the discord server, I’m copying that message over here:

there is a /tmp/beerocks file that (according to google) is connected with the mesh system and contains logs and ARE in RAM. It is for prplMesh and this thing is crashing on 6GHz radio and restarting every 5 sec and flooding this log file. It grows until my router OOMs and reboots. 
I'm still on beta1 because on beta3 mesh does not work at all for me. I don't know whether on beta3 it is fixed (ofc if mesh is working for anybody there)

nemetharon · October 17, 2026, 5:39am

I have updated to beta4 with settings kept from beta1. Still having issues. As you can see most of my devices shows up as unknown and connect top column is empty and mesh page does not show the "paired" flint 3 (even though when i log into flint 3 with ip address it shows everything is okay and mesh is working fine).

I have asked claude to SSH into my flint 4 and investigate based on my previous findings and it fixed the issue! Here is what it said:

On the main router the prplmesh controller (beerocks_controller) was never starting. Only gl-mesh was running, and /tmp/beerocks contained nothing but uds_broker.

The cause is that the 6 GHz radio had its channel saved as 0 instead of auto:

wireless.MT7990_1_1.channel='auto' # 2.4G
wireless.MT7990_1_2.channel='auto' # 5G
wireless.MT7990_1_3.channel='0' # 6G

hostapd and mtkdat treat 0 the same as auto, so 6 GHz works normally (ACS picked ch 53, 320 MHz). gl-wld takes 0 literally, though. It loops forever on:

gl-wld: (wld.lua:633) radio channel not ready: rax0 channel: 0
gl-mesh: [WLD-SYNC] query initialized state completed, trigger on_active Initialized false
gl-mesh: [AMX] subscription activation failed 2 path X_PRPLWARE-COM_WiFiController.Network.Device ... failed to subscribe AMX events: -1

WiFi.Initialized stays false, so gl-mesh never starts the controller or agent. The node list and the "Connect To" column both come from the controller's data model, so they show up empty.

The Flint 3 was never actually unpaired. It was still in /etc/config/gl-mesh and kept retrying, but the main router rejected it every 3 s:

gl-mesh: (vendor.lua:541) not found device 94:83:c4:b0:9a:bd

Workaround:

uci set wireless.MT7990_1_3.channel=auto
uci commit wireless

Within a few seconds gl-wld reported "wld initialized" and the controller and agent started. The Flint 3 rejoined by itself (join state report ... is_new_join: 0), with no re-pairing needed.

Suggested fix: gl-wld should treat channel=0 as auto, the same way hostapd.lua and mtkdat.lua already do. I upgraded from beta1 with settings kept, so the 0 may have come from the old config or from config migration.

The "Unknown" client names are a separate issue, and I haven't looked into those yet.