ispy build Gargoyle 1.15.x OpenWrt 25.12 (BETA) - 2026-07-19

[ispyisail]

ispy build

Gargoyle 1.15.x OpenWrt 25.12 (BETA) - 2026-07-19

Gargoyle 1.15.x "based on OpenWrt 25.12" is a community test build from the ispyisail fork, switching to the new OpenWrt 25.12 base (kernel 6.12). This is not Michael's (lantis) official release and is not a preview of it — it's a separate, unofficial testing track meant to shake out bugs early on the new base and exercise a new automated build/signing/hosting pipeline. If you want the official release, wait for that one.

VERY BETA. These builds have had automated testing but only limited real-hardware time. Flashing beta firmware can brick your router. Do not flash a device you cannot recover (TFTP / serial / vendor recovery), and do not use these on a router you depend on.

Do not keep settings when moving onto this base from any earlier Gargoyle version — config formats changed between bases and stale settings cause weird breakage. Back up your settings first, flash clean, and reconfigure. Proceed with caution.

Changes since BETA4/BETA5 (2026-07-18):

• OTA firmware-update client is now live (System → Update → Check for Updates) — signed manifest verification, board/hardware-floor checks, checksum-verified download, fail-closed apply. Nothing published to update to yet (manifest publishing side is still empty), but the client itself is real and tested.
• apk-tools now ships on every build profile, not just the internal test profile — a real gap found via the first hardware test of the apk-backed package manager on a GL-MT6000.
• Fixed: OTA's anti-replay check could get permanently stuck if a manifest ever legitimately regressed to an older timestamp (a publisher revert, not an attack) — every future check failed forever, even against genuinely newer manifests. Now flags it and keeps working; the real rollback protection is enforced at download/apply instead.
• Fixed: removing a plugin that was baked into the image at build time could silently report success while leaving its files untouched on disk. Confirmed live on real hardware. A failed removal now correctly stays reported as installed.
• New automated test coverage added for both bugs above, confirmed failing before the fix and passing after.

Also included, since the OpenWrt 25.12 base bump:

• New OpenWrt 25.12 base, kernel 6.12
• Plugins install from a signed online feed, verified against a key baked into the firmware
• VLAN Manager — define VLANs and assign switch ports from the GUI, with subnet auto-suggest and live validation
• Port forwarding: source-zone selector, so forwards can target extra WAN VLANs
• Captive portal, bundled on x86 and installable as a signed plugin elsewhere
• Multi-tab GUI save-corruption fixes across quotas, restrictions, routing, port forwarding, VLANs and more
• WireGuard: saving no longer wipes manually-added peers
• First-boot timezone/country list fixes
• Basic page: Router IP field now accepts CIDR-form addresses (OpenWrt 24.10+), so changing the router IP works again
• DHCP: reworked "alternative gateway" option, with clear notices where it bypasses Bandwidth/Quotas
• QoS init-script fix that could misapply port ranges
• DDNS/identification pages: proper hostname/domain validation
• Security hardening in the weburl module and several config parsers, found by fuzzing

Known Issues

• Plugin installation needs the router to reach GitHub (the feed is hosted on GitHub Releases) — no upstream internet means it can't fetch the package list
• 4 out of 32 previously-supported devices (e.g. TL-WR841) don't fit this base and are not included
• OTA Check for Updates works but currently has nothing to offer (see above) — expected, not a bug

Downloads
Please find the downloads at the Firmware Finder — search by model name, or drag an existing Gargoyle backup file onto the page to identify your board automatically: https://ispyisail.github.io/gargoyle-firmware/

Direct release page (all files, with checksums and signatures): https://github.com/ispyisail/gargoyle-f ... 7.19-beta6

Discussion
Community test builds — full announcement and change history

[hr]
https://ispyisail.github.io/gargoyle-firmware/ for the latest test builds
This is unofficial, experimental, community-tested software — not the official Gargoyle release. Please report back what you find, good or bad; "works fine on <model>" is just as useful as a bug report.
https://github.com/ispyisail/gargoyle

[Lantis]

Just as a disclaimer, a lot of these features do not reflect what is (currently) going to be available from a 25.12 based release, and may not make it ever. This is purely a fork (as it says in the opener).
ispyisail has worked hard to make this available which is very appreciated.
I just don't want people setting their expectations of the development direction based on this one and being confused or disappointed.

However if people use this and like it then they should continue to do so! Users should make note of the features that are important to them that may become focus for bringing into the mainline.

Reality is, an "official" OpenWrt 25.12 based firmware is probably going to be available near Christmas, not likely before. So this gets you on the latest and greatest early, if that's important to you.

My Feedback:
The "firstboot timezone/country freeze" bug I was not able to replicate in the base firmware, I advise that you need to double check your build environment is in one piece and your build config has not replaced any utilities (e.g. awk).
Further feedback and real world experiences were needed on the driving force behind the WireGuard change (as that is an anti-pattern that I won't implement). The whole point of the plugin is for Gargoyle to manage the configs for you. If you are manually adding peers it is supposed to delete them, they are unmanaged.
Is Gargoyle not able to import/read/work with some configurations you are trying to do? That should be looked at and expanded on rather than this (in my opinion).

(I covered both of these points in my email if you hadn't read it yet)

[Lantis]

Also I was surprised to see patch 022 still in the tree? APK hates non standard package naming. Was something done to fix this?

[ispyisail]

Fix 1
https://github.com/ispyisail/gargoyle/discussions/121

Fix 2
https://github.com/ispyisail/gargoyle/discussions/122

Discussion
https://github.com/ispyisail/gargoyle/discussions/123

[ispyisail]

Up to beta9 now

Synced back with Lantis build, has everything Lantis build has plus extra stuff

Latest OpenWRT
Latest OpenVPN
Latest Wireguard
Latest TOR

All the lastest secuity patches that i could find

[oliver44]

Hi,
I am experiencing the same issue with my GL.iNet GL-MT6000 (Flint 2). The 5GHz Wi-Fi band is completely inactive and does not broadcast at all.Could you please assist or let me know if there is a specific fix, driver update, or a test firmware build that resolves this issue for this router model?Thank you!

[ispyisail]

Hi oliver44, thanks for reporting this — and sorry it's still biting you.

I dug into this today on my own GL-MT6000 running the current beta, and I think I've found at least part of the problem. It's likely not specific to this build: I found your post from October 2024 describing the same symptom on the official 23.05 release, so this looks like a long-standing MT6000 issue rather than something new in the 25.12 base.

What I found

On my MT6000, the wireless country code is unset by default, which leaves the router in the "world" regulatory domain. In that domain, only four 5GHz channels can actually host an access point:

- 36, 40, 44, 48 — usable
- 52 through 144 — blocked (no-IR + radar detection)
- 149 through 165 — blocked (no-IR)

That's 21 of 25 channels that a router physically cannot transmit an AP on until a country is set.

The bug on our side: Gargoyle's 5GHz channel dropdown lists all of those channels anyway, including the 21 unusable ones. So it's very easy to pick one, hit save, and have the radio simply never come up — with no error message explaining why. That matches your "sees just channel 36 and 100, plus the wifi does not activate" description from 2024 quite closely.

Could you try this?

1. Go to Advanced -> Wireless Country and set your country, then save.
2. Go to Basic -> Wireless and set the 5GHz channel to 36, then save.

If 5GHz comes back, that confirms it and I'll get the channel list fixed properly so it only offers channels that can actually work.

If that doesn't fix it, could you post the following? It'd help a lot:

Code: Select all

uci show wireless
iw reg get
logread | grep -i hostapd | tail -30

And also:
- Which beta are you on (beta6, beta9, etc.)?
- Does 2.4GHz work normally?
- Did you keep your settings when you flashed, or start clean? (The release notes recommend not keeping settings across the base change — stale wireless config is another possible cause here.)

Thanks again for the report — this one's been hiding for a while and your post is what surfaced it.

[ispyisail]

have a possiable fix

https://github.com/ispyisail/gargoyle/pull/136

[ispyisail]

beta11 is up with the fix hopefully

[cpucpu]

Finally I'll be able to setup a sing-box server. Just finished setting up openwrt on a wr3000p.