try sqm on help me with speed drop
Is the x2000 planned to eventually support mesh as well?
The GL-X2000 (Spitz Plus) is currently listed as unsupported for GL.iNet EasyMesh, and no specific plan or release date for adding support has been announced. GL.iNet intends to extend Mesh to more compatible models based on hardware capabilities and development progress, but this does not confirm future X2000 support.
Please monitor the official Mesh supported-model list for changes.
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.
Yes, Flint 3e will also support Mesh. Firmware is expected to be released at the end of the month.
Are you using the v4.11 beta3 firmware updated on September 30th? It fixes related issues.
Any info on when the Slate 7 Pro will get the beta?
I was just going to ask this lol
Already have my Flint 3 and Slate 7 running in mesh mode, would love to add the Slate 7 pro to it.
Also waiting for the Slate 7 Pro… it was supposed to be in September, no update ? 
It seems that the mesh mode 4.11.0 beta release 3 on the Flint 4 doesn't sync radio settings which I think is ok but then in the UI you can't change the settings as they are locked. This doesn't make sense and limits me to 80mhz for example.
My Flint 4 main router meshed to Flint 3 and Slate 7 have issue with IoT network and Guest Network, connection keeps dropping and shows up as no internet conenction on the said network, It works fine when i switched it to router only mode and no mesh connected. There seems to be an issue with the VLAN of the network ok easymesh? Currently i disabled the mesh now and using the Slate 7 and Flint 3 as AP over LAN.
Another problem I encounter right now is that the 5GHZ network on my Flint 4 seems to have issues with my Samsung devices, specifically with my S26 Ultra and Tab S9, it will connect and then randomly drop within a few mins of using it.
The v4.11 beta version of Slate 7 Pro has been released.
In Mesh networking, the 5G band needs to handle the wireless backhaul, providing a stable, low-interference link for communication between child nodes and the master node. Allowing users to arbitrarily modify channels or bandwidths could lead to the following problems:
Interference between the backhaul channel and the terminal access channel, resulting in an unstable Mesh topology.
Instability of the 160MHz equal-width band on some channels (DFS), easily triggering radar avoidance and causing disconnections.
Complex multi-node synchronization and coordination.
Therefore, the current firmware locks the 5G backhaul band to 80MHz to ensure stable coverage.
I notice that the Flint 4 on this Beta firmware will randomly lose the 2.4GHz WiFi network or will not have any internet access there.
I thought it was an Internet or a Smart Home Device issue.
Until I saw for myself, my PC is connected to the internet without any issues.
But… I saw ALL my Smart Home Devices have their ‘trying to connect to WiFi’ lights blinking.
In other words, those days when Alexa had a slow or outright jammed up moment ignoring my commands was all because of the Flint 4.
And it caused annoying devices like the Govee COB Lights to completely lose WiFi connection entirely until I re-register the WiFi with it. Which is absolutely annoying.
Can I ask, why does the 2.4GHz Network randomly stop working or I would say, have random intermittent disconnects that cause ALL devices waiting to reconnect to the Network from time to time?
Any way to resolve this issue?
Please provide the complete topology and Mesh backhaul method.
Regarding the IoT disconnection issue, please export the complete logs for all three routers in System < Log < Export Log.
Regarding the Flint 4 connection dropout issue on the 5G Wi-Fi band, please allow the following commands to output wireless-related log information.
mwctl rai0 show MibBucket &&dmesg -c
mwctl rai0 show stainfo &&dmesg -c
while true;do mwctl rai0 show stacountinfo=1&&dmesg -c;sleep 2;done
You can send the logs to me via PM.
Could you please run the following command to collect wireless information related to the 2.4GHz band?
mwctl ra0 show MibBucket &&dmesg -c
mwctl ra0 show stainfo &&dmesg -c
while true;do mwctl ra0 show stacountinfo=1&&dmesg -c;sleep 2;done
And please export the complete log content.
Please PM me and send me the relevant log information.
Currently, I recommend that you revert to the stable version v4.9.2. Then connect your IoT devices to the IoT network for use.
Here is the download link: GL.iNet download center
Some of us aren't using a wireless backhaul so it's only disruptive to lock 160mhz from us. Also if you set the channel to the start of the non DFS range and then use 160mhz you can use it on clients which support DFS and which don't support DFS.
i have the same issue but only occurs to me when using the mesh system
I was using Mesh before too. I thought it was a Mesh issue. I got so annoyed, I just went back to just using the Flint 4 alone.
But then, the problem still occurred and I finally saw for myself how ALL my IoT devices were affected.
And since I still got Internet, so I know it must be the WiFi itself at this point.
Hope you don’t mind. But I cannot revert back to the old firmware. I’m using a Fibre Optic cable direct to the Router. And the older firmware doesn’t recognize my SFP+ Module.
Mind if I ask, why I should be using the IoT Network that subnets the IoT devices?
I’d prefer them to be on the same subnet. Thus, I find the IoT Wireless option not to my preference.
Any benefits to it that I can’t do on the 2.4GHz Wireless network?