Fair enough, Will.
Is the Flint 2 Snapshot still based on Openwrt 21.02/kernel 5.4?
Yes, only the OP24/OP25 images are separate Native OpenWrt branches using the open-source drivers and newer kernels.
Hi
Is it normal that the fan on the MT3000 would spin at maximum speed (~6000 RPM) during each boot, even though the CPU temperature is very low (39-50°C)?
Hi,
Could you please confirm the complete firmware version currently installed? You can find it under System → Upgrade .
An earlier OP25 build had a fan-control issue, but it should have been fixed in v4.9.1-op25 beta2 and later versions . If you are already using beta2 or a later build, please also let us know how long the fan remains at approximately 6000 RPM after startup.
It is currently on v4.9.1-op25 beta3, but I’ve seen this on beta2 and 1. However, this only lasts for about 50-80 seconds after boot. After this, it stops and returns to normal.
When can we expect a new build? The beta3 version came out 2 months ago…
Really? 
What about it? I was wondering because each boot increases the power load by quite a lot and it’s loud. I have not seen this happen in older versions, quite sounds like I’m running a gaming computer for a router
I don’t know if this has been answered already, but in your testing, which drivers perform better on the Beryl AX in terms of speed throughput and stability, the opensource driver or the closed source MTK driver?
Thanks for the report. We have reproduced this behavior on a local Beryl AX running 4.9.1-op25 beta 3 .
During startup, the kernel PWM fan driver initially runs the fan at full speed as a fail-safe. The GL.iNet fan-control service starts later and then adjusts or stops the fan according to the CPU temperature.
We will check with the R&D team to see if this can be improved in future firmware updates.
1 Like
Based on the community feedback we have received, neither driver is consistently better in every scenario. Their throughput, stability, and device compatibility can vary depending on the wireless environment, connected clients, and configuration.
We recommend trying the OP25 firmware in your own environment and comparing it with the MTK driver firmware to see which one works better for your use case. Just note to back up your configuration before switching firmware.
Now my Flint2 with OP25 firmware is running since 47 days without problem.
1 Like
Great, I hope to have linux kernel 6.12.x in the stable version soon.
When can we expect a new build? Beta 3 was released more than two months ago…
1 Like
Hi,
Thank you for your interest.
We only recently completed development of v4.11 for Flint 2 and Beryl AX. Work on v4.11.x-op25 will begin once the R&D team has the capacity to take it on.
3 Likes
Please get them to fix issues with Bark and router based parental controls (randomised Mac clients and time based) not working with current 4.9.1 op25 firmware
This is the correct behaviour. Don’t change anything.
2 Likes
Hi,
The purpose of an OP25 release is to integrate the GL.iNet SDK with the vanilla OpenWrt 25 codebase. It does not add new features or change the existing feature set by itself.
For Bark, we are still waiting for the upstream provider to supply OP25-compatible code and APK files. Improvements to the built-in parental controls, including the randomized-MAC and time-based control scenarios you mentioned, will require further planning by our product team. We cannot confirm a release schedule for either item at this time.