Firmware v4.9 Preview: What to Expect

I’m having an issue with smarthome devices disconnecting frequently. I have a lot of presence sensors/bluetooth proxies around my house. Generally the connection is rock-solid to the router and to my Home Assistant server, but they do ping often and are quick to show ‘dead’ in Home Assistant. It had never been an issue before, but on 4.9 beta2 on my Flint 3 I see them constantly disconnecting and reconnecting (according to home assistant advertisements). Here are a few screenshots I took over the course of ~ a minute:

these were not cherry-picked or anything, I simply opened the proxy dashboard and took a screenshot, waited a few seconds and refreshed then took another screenshot, then again. Basically every time I look at this I see 3-5 ‘dead’ at any moment in time and which are ‘dead’ changes each time as they do still periodically get to check in, just not as often as before. Not sure if the router is limiting them, AGH, etc, but I was not having this issue before and previously had a warning display if <10 were active at a given time since it isn’t uncommon to lose connection for a short while but was super uncommon for multiple to lose connection at the same time long enough to trigger the warning. Since updating to 4.9 the warning is displayed almost all the time.

I haven’t noticed it on PC, laptop, Apple TVs etc but I’m not sure if caches are just keeping me from noticing. I did notice yesterday on my ratgdo smart device for my garage door; when I came home the garage door did not open when trying to control via ratgdo because apparently it was disconnected. A few seconds later it worked, so I suspect the ratgdo is behaving similar to these bluetooth proxies and I just don’t have as much visibility to it on my home assistant dashboard.

This is Not on IoT network, I have not set that feature up in 4.9 yet; right now everything is being used the same as I was on 4.8.4 (AdGuard Home running, no client VPNs set up, Wireguard server enabled)

Way too many active. Why are you using the normal, pro, and pro++ of HaGeZi for example? Pick one

so tonight I flashed the beta 4.9.0 onto my Flint 3 and my Slate 7, whilst I can see where I can easily create an IoT network on my Flint 3, I cant see this option on the Slate 7 ?

SLATE 7

FLINT 3

As you’re using a Beta, they may not have hard-coded it into the GL GUI yet on this router, in this version.

It looks like your Slate 7 is in WDS/Extender/AP mode?
Please note that in these modes, the Guest and IoT networks are not available.

Ahh thats a shame, yes its in AP mode, hardwired to my Flint 3, because unfortunately the Flint doesnt cover the whole house.

It looks like 4.8.4 fixed everything, usually less than 24 hours of uptime video thumbnails on Facebook wont load and TikTok videos do not load properly only sounds. Works perfectly on this version im at 28 hours uptime and no issues. I did experience a tiny bit of packet loss on Fortnite but ill report back any issues

@EBE,

I agree with you that in 4.9.0 Beta for Flint 3, setting up an VPN exception becoming a convoluted task involving one part in GLiNet GUI, and the other in LuCI. It defeats the purposes of user-friendly feature of GL.iNet router, which I think is GL.iNet strong selling point.

Furthermore, by using MAC address of an individual device for VPN exception, it makes it awkward for quick & easy setting-up exception for multiple devices if needed.

My suggestion: Make exception by IP address available. Multiple exceptions can be made with ease. With net mask, for example.

Cheers,

Netcruizer.

1 Like

As many users said it before, i really hope you guys concentrate on op25 or at least op24. Op21 is crazy old and i think many users are not willing to use such an old fw. Cant wait for op25 fw.

5 Likes

yes please GL Inet, Flint 2 is your top tier router, Flint 3 and 3e is a downgrade. They are slower then the Flint 2.

We users are waiting for op24-op25 for a few years already, for your flagship router this is not acceptable.

5 Likes

When will 4.9 beta be available for the Flint 2? This device is way more capable than the Flint 3 and only surpassed by the Flint 4 which is not yet released.

5 Likes

Same sentiments. It feels like they forgot about Flint 2 at all.

1 Like

Testing a new firmware with such new features on an inferior hardware makes me further doubt some of the decisions made by the developers here!. Surely testing on devices that have proven to be a total flop will produce an inadequate software.

I configured the DNS using DNS over QUIC and a private AdGuard DNS server, but I don’t think any requests were sent to the server.

I reactivated AdGuard Home using the same private AdGuard DNS server, and requests started going through to the private server.

Could there be an issue with how the DNS works in firmware version 4.9.0 beta 3?

It worked correctly with beta 2.

It seems like another update my Brume 2 and Beryl AX probably won't receive. The Brume 2, advertised as a 'Security Gateway', hasn't had an official update in a year, and the beta version that started in September remains unfinished.

Is GL.iNet actually achieving absolute security in their routers? It feels like the company is prioritizing releasing an absurd number of new devices, effectively abandoning support for relatively recent models.

That is why I'm planning to switch to MikroTik. They keep models launched nearly 10 years ago running the latest RouterOS versions.

6 Likes

Pro++ includes Normal and Pro. And most of the others probably contain duplicate lists of lists.

Will the GL-MT2500A model not receive updates? It's not that weak, after all.

1 Like

In beta 3 the guest and IoT networks are activly brodcasted from both my GL-BE9300 thats running as AP’s, but the guest networks are not visible in the web gui and can’t be shut down from there. The same was true on the GL-BE9300 I’m using as firewall but I culd ofcourse shut down the guest networks from the web gui.

Hi,

@mefaloc312 @victorbayas @misuzu

We are currently preparing to release v4.9.0 beta for the Flint 2, which may be available sometime this week (possibly even today, unless we encounter any blocking issues).
As for the OP24/25-4.9.x version, it will be released after v4.9.0 beta. The timeline is not fixed yet, as there is still a fair amount of work required to migrate v4.9 to OP24/25.

@DouglasFerreira @CrashXRU
Brume 2 and Beryl AX will receive the v4.9.x update as well, but it may come a bit later.

You can check the first batch of devices receiving v4.9.0 in the Release Roadmap on the download center.
Other devices will be updated in subsequent batches.

4 Likes