Just an update on my issue with Terminal - I uninstalled the package and reinstalled, this time with it accessible over http only. It now works as expected.
As someone who’s been battling RAM usage for the last year on a Flint 2, with the assumed culprit being AGH, I love this suggestion. Thanks for taking the time to think about it and add it here.
Now have this set up on my new Flint 4. ZRAM swap and GUI Terminal also installed and running without issue.
Glad to hear the community script, ZRAM swap, and GUI Terminal installed successfully on your Flint 4. Thank you for sharing the compatibility result with other users.
This utility is not officially supported by GL.iNet. Any guidance is provided on a best-effort basis, and GL.iNet Technical Support may not be able to troubleshoot or maintain this configuration.
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.
It is possible in your preferences to hide any user, including this new bot. I understand why they want to throw up this caution, but most folks here will understand that and don’t need what may be constant reminders.
Yes, forum users can use their Discourse preferences to ignore or mute accounts whose posts they do not wish to see. The notice is included to distinguish AI-generated replies from staff-verified support responses.
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.
Thanks for pointing this out and for sharing the preference option with other forum members. We understand the concern about repetitive notices; the disclosure is currently required on every AI-generated reply so readers can clearly distinguish it from a staff response.
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.
As nice as this forum was, the damned AI bot will make me switch to another brand.
PLEASE REMOVE THE BOTS. PLEASE!
It's already off 
New version is out which is a rewrite of the AGH management based on the feedback above.
- Supports many more curated blocklists and a couple additions to the default “recommended” list
- Memory impact meter for list count selected/enabled. Red doesn’t mean it won’t work but doesn’t mean it will work either
- UI rewrite to be more consistent with other UIs (like package manager). Split action for separating install vs enable
- Better support for Beryl 7 with inline support to disable storage limitations
- Added a zram swap shortcut into the renamed “advanced options” menu - Storage, Zram, Access, and UI Updates seemed like too long of a menu option
There are some limitations that will be addressed in a future release:
- Don’t disable storage list limitations on Beryl 7 then add a bunch of high rule count lists exceeding 8.5M in size, then change back to having the storage list limitation enabled. AGH will end up with one or more orphaned non-functioning list(s) until there is more storage available. Two options being considered is to just remove all the lists during this action or provide a stern warning to not do this unless you are willing to do your own cleanup
- The memory impact meter isn’t real-time so there are some situations where there is a discrepancy between lists selected and the noted impact. Exiting the list selection menu and re-entering will refresh the meter. Considering adding either a manual refresh or moving to a forced refresh (similar to fan and HW info page 1 screens)
- HaGeZi’s threat intelligence has been purposely left off since it has 1.1M entries and has a high chance of crashing most routers except the Flint 4. Consider URLHaus + PhishTank that’s already included in the recommended list as an alternative approach
For those not aware of the advanced features menu:
- Remove storage limits for Beryl 7 routers (due to the 512M RAM)
- Enable Zram Swap - in memory compression to effectively increase RAM by 50%. Highly recommended for 512M routers or less running AGH. Generally < 1% CPU hit on higher end routers like Beryl 7, Brume 3, Slate 7 Pro, Flint 2 & 4, etc
- AGH Direct Web UI access (with or without credentials - recommend with) bypassing the GL WebUI
- Enable updating AGH directly through the AGH WebUI. This is the preferred mechanism to update your AGH to the latest version. If there is a desire to toggle between beta and stable release trains, please provide feedback
Thanks to all that have been providing feedback and bug reports. It’s appreciated.
One thing I didn’t realize, and I’m not sure exactly how this came about, but I did play with optimizing the MTU on the wireguard client on my Mango. Then I took the Mango offline and put it in my travel bag. What I didn’t realize is that it adjusted the MTU on other devices as well, so that my nightly replication between two servers was broken. As soon as I adjusted the MTU back to 1420 from 1440 those other connections started working again.
This looks to be a fantastic project.
All new version is out that I’m really excited to share:
-
All new toggle switch identifier in GL web-UI. This allows you to visually see the current toggle button position in the web-ui and in the app. Also reduced the overlay time in web-ui so it looks more fluid
-
All new persistence enablement support for web-UI tweaks (ttyd, toggle button, and fan settings)
-
More uniformity fixes across the app focusing on prompt/language consistency
-
Other minor tweaks and fixes
For complete details, please refer to the changelog
Hi, I updated my Flint 4 to v4.1.1 Beta 3 this evening and now I can’t seem enable the zram swap feature. I get this when attempting to enable it:
I’ve tried to uninstall the feature, using the various methods and reinstall it, as well as uninstall the entire utils package and reinstall it but, I just get the same result.
Known issue with the beta build. I’ve been working with GL to get the issue resolved.
New version is now out which has an integrated CLI firmware updater in it. In addition to having many built in safety checks, it leverages an updated package and persistence manager to ensure all additional supported packages and features survive a firmware update. Note that you will have a final chance to back out of the process before it starts the upgrade.
Complete change log here: GL-iNet_utils/CHANGELOG.md at main · GLiNet-Community-Scripts/GL-iNet_utils · GitHub
Awesome, thanks for this.
In case I missed something in the release notes, is the Zram swap issue in v4.11 Beta 3 still outstanding?