Feature Request: Performance vs On-Demand Mode + Advanced Network Controls in GL.iNet UI

Routers
1

Hi GL.iNet team,

I’d like to suggest a few enhancements to the GL.iNet UI that would greatly improve performance tuning and advanced use cases, especially for users running WireGuard, SQM, or high-throughput setups.

1. Performance vs On-Demand Mode (System / Network)

It would be extremely helpful to have a UI toggle similar to mobile OS behavior:

  • Performance mode

    • CPU governor locked to performance

    • Optimized defaults for high throughput and low latency

    • Intended for VPN routers, servers, or heavy traffic use

  • On-Demand / Balanced mode

    • CPU governor set to ondemand

    • Power/thermal optimized for light or intermittent usage

Currently this can be done via SSH, but exposing it in the UI would:

  • Prevent accidental performance regressions

  • Avoid breaking the UI when users manually change governors

  • Make advanced tuning safer and more accessible

2. Congestion Control & Queue Discipline (UI-Visible)

Please consider adding UI options for:

  • TCP congestion control selection (e.g. cubic, bbr)

  • Queue discipline selection (e.g. fq, cake)

At the moment:

  • These changes require SSH

  • In some firmware versions, switching to BBR/FQ via CLI can cause the GL.iNet UI to stop responding

  • Reverting to defaults restores the UI, which suggests tight coupling between UI services and kernel/network defaults

Even a read-only status view (showing active CC/qdisc) would help significantly.

3. WireGuard-Aware Performance Presets

For WireGuard users specifically:

  • Optional preset for VPN throughput (buffers, governor, offloading hints)

  • Clear indication of what is “supported by UI” vs “advanced/CLI only”

This would reduce trial-and-error and support tickets.

4. Advanced Settings Section (Optional / Expert Mode)

A hidden or opt-in “Advanced / Expert” section could safely expose:

  • CPU governor selection

  • Congestion control

  • Queue discipline

  • Offloading toggles (with warnings)

This keeps the default UI simple while empowering power users.

Overall, GL.iNet hardware is very capable, but today some performance-critical tuning lives only in SSH and can unintentionally disrupt the UI. Bringing these controls (or at least visibility) into the UI would be a big win for reliability, transparency, and advanced users.

Thanks for considering happy to test or provide feedback if needed.

—

(Flint 3 user, firmware 4.8.4)

2

Hi

Thank you for your suggestion.
We’ll make a note of it and pass it along to the product team for consideration in future firmware updates.

At the moment, these features seem to be primarily relevant to advanced users, so the priority may not be very high and they may not be implemented in the near term.

4

Thank you for taking the time to review!