# Differences between firmware, GUI & OpenWrt (?)

**URL:** <https://forum.gl-inet.com/t/differences-between-firmware-gui-openwrt/43531>\
**Category:** Router\
**Created:** [June 13, 2024, 5:18pm UTC](https://forum.gl-inet.com/t/differences-between-firmware-gui-openwrt/43531 "2024-06-13T17:18:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\
**Post date:** [June 13, 2024, 5:21pm UTC](https://forum.gl-inet.com/t/differences-between-firmware-gui-openwrt/43531/2 "2024-06-13T17:21:27Z")

</div>

> [@ivanSB](#):
>
> Is your UI just a layer on top of uci configuration file? So that if I make a change in your UI it will be reflected in uci and if I make a change in uci it will be reflected in your UI?

Yes and no. The GL GUI uses wrappers to modify the config files - so it's not like `luci` itself, which highly utilize the config files; it's more like a mixture. Not all settings (and changes) will be shown in the GL GUI.

> [@ivanSB](#):
>
> And the disclaimer "It is provided as is. GL.iNet is not responsible for LuCI maintenance." just mean you won't feel bound to offer support?

`luci` is a 3rd party tool - so that's why no support can be offered.

> [@ivanSB](#):
>
> can we get some more info on the difference in "performance and compatibility issues" and possibly hardware feature support between open-source drivers and MTK, to make a more informed choice between the two firmware?

Feel free to scroll through 2200 posts: [Flint 2 (GL-MT6000 ) - bug reports - collective thread](https://forum.gl-inet.com/t/flint-2-gl-mt6000-bug-reports-collective-thread/35608/)

From my feeling: Doesn't matter if you are a normal user with not pretty old devices.

---

_[View the full topic](https://forum.gl-inet.com/t/differences-between-firmware-gui-openwrt/43531)._
