Firmware v4.9 Preview: What to Expect

Hello,

I see! Parental controls may only include some filters related to children.
Do you want all the options? Which filters would you mainly enable?
Is your use case aimed at children, or something else?

@bruce

A suggestion... I tried enabling QoS via ‘Customise’, but I noticed that the settings don’t include a specific option for P2P protocols (such as BitTorrent, but also others) so that, in my case, I could assign them a low priority. Is it possible to add this option to the preset list? :slightly_smiling_face:

Received, I'll make a note of that.

2 Likes

a better work around would be allowing users to set the -c and -w flags for the adguard process

the problem is not rule size the problem is the query.db is very large and rapidly depletes system ram in as little as 24h

Hi, when can we expect the 4.9 firmware based on OP?

Same question, for Flint2 when can we expect 4.9.0-op25 ? A rough ETA would be great. One week/month etc. Thanks :blush:

2 Likes

Sorry for the late reply.

I took a preliminary look through the content in the referenced post.

It seems that the ADG configuration files / working directory were moved from the router’s internal flash storage to a USB drive or similar external storage device.

However, this does not appear to affect memory usage itself.

The /etc/AdGuardHome/ directory is mounted on the router’s internal flash storage and is unrelated to RAM usage:

root@GL-BE9300:~# df /etc/AdGuardHome/
Filesystem           1K-blocks      Used Available Use% Mounted on
overlayfs:/overlay     7260736    206616   7054120   3% /

In addition, the default AdGuard Home configuration already limits the number of stored records and retention time:

querylog:
  dir_path: ""
  ignored: []
  interval: 2160h
  size_memory: 1000
  enabled: true
  file_enabled: false

statistics:
  dir_path: ""
  ignored: []
  interval: 24h
  enabled: true

Could you please further clarify how the measures mentioned in the referenced post helped with the ADG Home OOM issue, so we can better discuss it with the development team?

All seems to work in

SYSTEM → TIME ZONES

…and still no DPI progress

what else should i do?

Hi

Could you please export the logs so we can take a look? PM me or Bruce, thanks.

done :slight_smile:

4.9 Beta 3 now appears out (13/5/26)

No obvious change log. Just the generic 4.9 Whats New.

I’ve installed today’s 4.9.0 release and can confirm that, with AdGuard Home enabled, the 2.4GHz IoT Wi-Fi network now has internet access :+1:

1 Like

odd perhaps the gli build in version behaves differently but it should not be ignoring the -c -w flags regardless

I honestly never used it beyond day one because it keept ooming the system so I switched to the upstream releases

but the config change SHOULD work on any implementation of ADH if its not then something is wrong

perhaps take this discussion back to the agh oom thread I linked

and btw take my account out of approval mode please

We have upgraded your user level, so you should no longer be in approval mode.

@xackep @Void

Regarding v4.9.x-op25, we have finished the preliminary work and are currently in internal testing.

However, we still need time to test and fix any issues discovered during testing—we cannot specify exactly how long this will take, so no timeline is available at this time.

7 Likes

will packages such as adguardhome be upgraded to the current release after testing

one of the problems with glinet is your packages are substation behind mainline in terms of package updates

Openwrt has shifted to using apk for its packages as well making staying up to date harder

as well

There is a new Beta from 2026-05-13 for Flint 2, what are the changes? Changelog is still from 1st Beta…

Thank @True0Man for sharing the logs and remote access.

After remote checking, we found that the current DPI time synchronization completion flag depends on the Multi-WAN functionality.

When Multi-WAN is disabled, the related flag may fail to be created correctly.

We have already asked the development team to further fix this issue.

For other users who encounter this issue, please update to the latest v4.9.0 beta firmware, and then switch the time zone once in “Admin Panel → System → Time Zone” (you can switch it back to the correct one afterward) as a temporary workaround.

After waiting a moment for the NTP/NTS time synchronization to complete, you should be able to enable DPI normally.

Nice to hear, thank you.

And at least approximate dates?)

On this version, by setting the USA in wifi in lights, do you always have performance like 4.8.3?