Firmware v4.9 Preview: What to Expect

[will.qiu]

@knee_mountain523

Apple generally prevent users from downgrading to older OS updates. Will GL.iNet do that or all firmware versions will be available for download and allow the downgrade and upgrade as needed? Given the current situation with the no-VPN option, I hope that v4.8 will continue to be made available for download for the foreseeable future even when v4.9 and v4.10 becomes final.

No, we do not prevent users from downgrading unless there is a specific known issue that would prevent the device from functioning properly.

You can always find previously released firmware versions in our Download Center and download/install them as needed.

However, please note that we cannot guarantee that keeping the existing configuration during a firmware downgrade will work properly.

[will.qiu]

@knee_mountain523

With regards to DPI, I know @will.qiu said there are some issues with extending the retention period beyond a week. I would really like to see a monthly and annual retention period. Even two years would be awesome. Why not permit the storage of the logs on a USB stick to mitigate internal storage capacity concerns and its lifespan? Can this issue be brought up with the GL.iNet team?

Thank you for the suggestion. We’ll discuss it with our product team.

Regarding the differences between DNS-level and DPI-level blocking, please refer to our previous discussion:

Adguard Home Vs DPI Content Filtering

Hi AdGuard Home filters at the DNS level, while DPI operates at the IP packet level. They work independently. However, since DNS queries occur before accessing a domain, AdGuard Home filtering typically takes effect first. All data is processed locally and is not uploaded to Netify or GL.iNet. [image] This feature is already in the roadmap and will be supported in a future firmware update.

[knee_mountain523]

You're misunderstanding me about what I'm trying to do by downgrading. While I wait for your team to sort out the viability of implementing a no-VPN option, if I ever need to do a factory reset of my router, I will downgrade to the latest v4.8 firmware, factory reset it, add a non-VPN tunnel, then upgrade and retain my settings, and finally finetune my router. Then it'll be safe to upgrade from that point forward while retaining my no-VPN tunnel?

I was asking if there were any bugs or security concerns associated with configuring the necessary settings on v4.8, and then upgrading to v4.9 or later while maintaining the configuration. Are you aware of any?

[knee_mountain523]

I really love seeing the data from the DPI log. It reminds me of the statistics from Control D. In a lot of ways, it does seem like DPI is sort of like it.

I personally think the length of the retention period should really be decided by the storage capacity of the external storage. Then, when space is running out, it will make DPI infinitely more useful. GL.iNet has lots of good ideas, but sometimes, you guys don't really expand on it and make it more useful.

[will.qiu]

Upgrading from v4.8 to v4.9 should generally be fine, except for the items already noted in the Release Notes that require attention.

For upgrades to later versions, we generally recommend not keeping the existing configuration, especially when upgrading to a new major version.

[will.qiu]

Hi,

@caicy @subid @denial @Costas

BE6500 v4.9.0 was released yesterday:

GL.iNet download center

[Subi18]

thx, Thanks, I’ve been testing the update and everything is running smoothly so far. The new DPI engine is really good; thanks to it, I can see the traffic and requests the network is making. The wait was worth it—SQM works well for gaming, as my network suffers from significant bufferbloat without it.

[denial]

thanks, i have also my flint3e updated

[knee_mountain523]

How should I configure SQM? Should I enter the advertised rates that my ISP provides? My gigabit plan is actually 940/940.

[Aramil]

Somewhere between 85% to 95% of total, very dependent on the line/ISP, start at 95% and move down and test against buffer bloat site, only really helps on busy networks.

[Costas]

You don't generaly need SQM with these speeds. SQM is mostly usefull for low speed lines.

[knee_mountain523]

What about configuring it on my travel routers at the hotel? I don't know who their ISP is and what kind of connection it's on. How should SQM be configured?

[will.qiu]

You can refer to the following steps:

Difficulties with bufferbloat

Hi, Thank you for sharing your current SQM configuration. To find a suitable SQM setting for your connection, could you please try the following test? Disable SQM first and run a speed test to determine your baseline download and upload speeds. Enable SQM again and set both Download and Upload speeds to around 95% of the baseline values. Run the Bufferbloat test again. If the result is good, you can gradually increase the limits. If the Bufferbloat result is still not satisfactory, reduce th…

However, we do not recommend using SQM in this scenario. SQM is designed to work when the network bandwidth is relatively stable. If the available bandwidth fluctuates significantly, SQM may not be able to function effectively.

[fonsanan]

Still no Update for the Slate 7 Pro in sight?

[knee_mountain523]

They're skipping v4.9 and will release v4.10 in Q1 2027.

[emsofo]

Why does the Slate 7 BE3600 get a 4.10 Beta but not the Slate 7 Pro ?!? No Beta for the flagship?

[will.qiu]

The v4.10 beta currently available for the Slate 7 is an early, model-specific AstroMesh test build. The Slate 7 (GL-BE3600) and Slate 7 Pro (GL-BE10000) use different hardware platforms, so their firmware must be developed and validated separately. The product tier therefore does not determine which beta becomes available first.

The Slate 7 Pro is planned to skip v4.9 and move to v4.10, but no public v4.10 beta or confirmed release date is available for it yet. We will share an update through the official channels once a test build is ready.

[knee_mountain523]

Even a relatively stable beta v4.10 for the Slate 7 Pro will be a nice Christmas present.

[will.qiu]

We’ll do our best—hopefully, we can make it a Christmas present for you!

[Peter_Pan]

Hello,

I use Flint2 with v4.8.4 and was waiting for some relatively calm period to upgrade to v4.9.0.

This week would be the right time for me but the GUI admin panel now suggests direct upgrade to v4.9.1

So my (rather naive) question is:

Should I follow the GUI admin panel and allow a direct upgrade to 4.9.1 or should I first upgrade to 4.9.0. via the GL.iNet download center? (bearing in mind that I definitely want to keep the existing configuration )

Thank you in advance