# Source code for GL firmware and packages

**URL:** <https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632>\
**Category:** Cellular, USB modems\
**Created:** [December 29, 2023, 10:59pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632 "2023-12-29T22:59:29Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![SpitzAX3000](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/spitzax3000/32/11018_2.png) [@SpitzAX3000](https://forum.gl-inet.com/u/SpitzAX3000)\
**Post date:** [December 29, 2023, 10:59pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/1 "2023-12-29T22:59:29Z")

</div>

I remember back in September 2023, there was a discussion online about GL’s firmware source code and the possibility of it to becoming a closed source.

If it is still an open source, can anyone points me to the source code of GL packages, and openwrt firmware ?

---

<div class="post-metadata">

**Author:** ![xize11](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/xize11/32/5340_2.png) [@xize11](https://forum.gl-inet.com/u/xize11)\
**Post date:** [December 29, 2023, 11:22pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/2 "2023-12-29T23:22:21Z")

</div>

Everything can be found [here](https://github.com/orgs/gl-inet/repositories)

However for the more bigger source/firmware “the infra builder” its set to private from what i understand its due the difference with global firmware and chinese firmware which is locked, as avoidance people using this builder to jail break their router its being privated.

Though drivers and some other things like a direct fork of OpenWrt are still visible, also a older image builder for normal openwrt i believe 😉

As far as i know packages were not intended to be open source if they belonged to GL sdk they often are pre compiled in these repos.

Also for the flint 1, there should also be a fork of openwifi, openwifi itself is also a fork of OpenWrt but with working drivers for flint 1 🙂 so if it was related to your questions, you could check the commit history there aswell for interest 👍

---

<div class="post-metadata">

**Author:** ![SpitzAX3000](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/spitzax3000/32/11018_2.png) [@SpitzAX3000](https://forum.gl-inet.com/u/SpitzAX3000)\
**Post date:** [December 30, 2023, 12:22am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/3 "2023-12-30T00:22:28Z")

</div>

Thanks for the replay! I was looking however for the source code of few GL packages , which I had not found on the GL’s GitHub repositories.

---

<div class="post-metadata">

**Author:** ![blackbox](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/c2a13f/32.png) [@blackbox](https://forum.gl-inet.com/u/blackbox)\
**Post date:** [December 30, 2023, 1:47am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/4 "2023-12-30T01:47:39Z")

</div>

Most of the packages that they modify can be found in [this repo](https://github.com/gl-inet/gl-feeds/tree/common). But not all of their packages are open source, even though [some of them should be](https://forum.gl-inet.com/t/flint-2-gl-mt6000-bug-reports-collective-thread/35608/231), since they contain modified files from packages that use the GPL v2 license.

---

<div class="post-metadata">

**Author:** ![SpitzAX3000](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/spitzax3000/32/11018_2.png) [@SpitzAX3000](https://forum.gl-inet.com/u/SpitzAX3000)\
**Post date:** [December 30, 2023, 3:43am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/5 "2023-12-30T03:43:53Z")

</div>

@blackbox thanks, that’s really helped !

---

<div class="post-metadata">

**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\
**Post date:** [December 30, 2023, 2:35pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/6 "2023-12-30T14:35:33Z")

</div>

FYI:

> [@Looking for the perfect device/system for TOR inside VPN and VPN inside TOR](https://forum.gl-inet.com/t/looking-for-the-perfect-device-system-for-tor-inside-vpn-and-vpn-inside-tor/36434/6):
>
> I see this as a hardware question rather than software. Regardless of the device, OP, you’re going to want vanilla OpenWrt to have full access to the OWRT ecosystem rather than waiting on GL to update GL repos for the ‘latest & greatest’. I say this because you’re going to be getting into far more advanced configuration than the GL GUI/repos allow & some of the GL functions conflict w/ more advanced OWRT packages. A quick overview: The Flint v2 (GL-MT6000) is slowly getting mainline OWRT 23.0…

> [@MT3000 Beryl AX Open Source WiFi driver firmware](https://forum.gl-inet.com/t/mt3000-beryl-ax-open-source-firmware/36607):
>
> System upgrade: From SDK-based OpenWrt-21.02 to fully open source OpenWrt-23.05.

---

<div class="post-metadata">

**Author:** ![SpitzAX3000](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/spitzax3000/32/11018_2.png) [@SpitzAX3000](https://forum.gl-inet.com/u/SpitzAX3000)\
**Post date:** [December 30, 2023, 3:08pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/7 "2023-12-30T15:08:49Z")

</div>

I don’t understand your replay?! I was looking for the source code for gl packages for editing and recompiling.

Thanks anyway!

---

<div class="post-metadata">

**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\
**Post date:** [December 30, 2023, 3:10pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/8 "2023-12-30T15:10:20Z")

</div>

Soon you should _officially_ be able to pull directly fr OWRT. I figured you’d want to know.

---

<div class="post-metadata">

**Author:** ![SpitzAX3000](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/spitzax3000/32/11018_2.png) [@SpitzAX3000](https://forum.gl-inet.com/u/SpitzAX3000)\
**Post date:** [December 30, 2023, 4:40pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/9 "2023-12-30T16:40:43Z")

</div>

Clarify please ? Pull what ? GL packages source code ? From which repository?

---

<div class="post-metadata">

**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\
**Post date:** [December 31, 2023, 6:59am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/10 "2023-12-31T06:59:58Z")

</div>

We’ll have to wait & see… when it happens, it happens.

---

<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:** [December 31, 2023, 8:38am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/11 "2023-12-31T08:38:16Z")

</div>

Since the CN authorities are very harsh I would not think that there will be any source codes of GL stuff soon.

---

<div class="post-metadata">

**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\
**Post date:** [December 31, 2023, 10:49am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/12 "2023-12-31T10:49:26Z")

</div>

Now that’s an interesting question. I’ve seen lots of GitHub repos fr individual CN devs but don’t recall one fr a CN company. I wonder what would happen if GL when full on F/LOSS & dropped the closed sourced, third party SDKs? Beyond that it strikes me the GUI & various control/setup scripts aren’t necessarily applicable to CPC regulation.

A question for another day perhaps.

---

<div class="post-metadata">

**Author:** ![Renboom](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/r/a698b9/32.png) [@Renboom](https://forum.gl-inet.com/u/Renboom)\
**Post date:** [January 5, 2024, 7:48am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/13 "2024-01-05T07:48:19Z")

</div>

Hi, currently the source code of our GL package used for editing and recompiling is closed source.

---

<div class="post-metadata">

**Author:** ![james801](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/3e96dc/32.png) [@james801](https://forum.gl-inet.com/u/james801)\
**Post date:** [December 10, 2024, 5:17pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/14 "2024-12-10T17:17:03Z")

</div>

Hi,

old thread but is it possible to clone their repo to make our own build from GL fork?

---

<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:** [December 10, 2024, 5:17pm UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/15 "2024-12-10T17:17:15Z")

</div>

No, not possible. The GL firmware is partly closed source.

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [October 29, 2025, 11:42am UTC](https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-packages/36632/16 "2025-10-29T11:42:15Z")

</div>


