Manual Supported Devices

Supported Devices

There is no stable, official release yet. Everything available right now — including everything linked from this page — is a beta/pre-release community test build. Flashing beta firmware can brick your router. Don't flash a device you can't recover (TFTP / serial / vendor recovery), and don't use these builds on a router you actually depend on. A proper official release is being worked on separately; when it exists, use that instead.

Find your device: Firmware Finder

The fastest, most accurate way to check whether your specific router is supported and get the right image is the Firmware Finder — search by model name or alias. If you already have a Gargoyle backup file from an existing install (System → Backup → backup.tar.gz), you can drag it onto the Finder page and it will identify candidate boards directly from the backup, entirely in your browser — nothing is uploaded anywhere.

Everything below is background on how device support is organized, for when you want more context than the Finder gives you.

How device support works

Gargoyle builds on top of OpenWrt's own target/subtarget system — a target is a chip family (e.g. mediatek), and most targets have one or more subtargets covering specific board generations within that family (e.g. mediatek/filogic). Device support is inherited from whatever OpenWrt itself supports for a given target, plus whatever Gargoyle's own build profiles enable for it.

That means there are two different tiers of "supported" worth keeping straight:

1. Actively published, with a pre-built image — you can just download and flash it via Firmware Finder.
2. Exists in the source tree, buildable, but not part of the current published test builds — you'd need to build it yourself (see Building and Flashing), and it may need real work to get running on the current OpenWrt base.

Tier 1: actively published targets

The current community test builds cover four targets, all on OpenWrt 25.12 (kernel 6.12):

Target	Covers
ath79	Most older Atheros-based routers — e.g. Archer C7, WNDR3800, and similar.
mediatek (filogic subtarget)	Modern MediaTek-based routers, including the GL.iNet GL-MT6000 / Flint 2.
ipq40xx	Qualcomm IPQ40xx-based boards.
x86	PC and VM images — including a ready-made vnet-wifi profile used for the project's own test simulator.

GL.iNet GL-MT6000 (mediatek/filogic) is the one device that's been through a full build → flash → real-hardware provisioning → automated test suite cycle as part of this project's own development process — if you're choosing hardware specifically to run Gargoyle on, it's the most proven option today. Everything else in these four targets should work to the extent OpenWrt itself supports that specific board, but hasn't necessarily been individually verified against Gargoyle's own web UI and features the way the MT6000 has.

Hardware floor

Very small-flash/RAM devices are explicitly not supported on the current OpenWrt 25.12 base — for example, 4MB flash / 32MB RAM devices like the TL-WR841 can't fit a modern build. If you have older, more constrained hardware, check the Firmware Finder for your exact model rather than assuming it's covered.

Tier 2: other targets (build from source)

These targets exist in the Gargoyle source tree, with real (in some cases years-long) commit history, but aren't part of the current published beta test builds — no ready-made image, and unverified against the current OpenWrt base:

Target	Covers
ramips	A large family of MediaTek/Ralink-based routers (many TP-Link, Xiaomi, and similar consumer models).
bcm47xx	Older Broadcom-based routers.
bcm27xx	Raspberry Pi (0, B, 2, 3, 4, and newer per its subtarget list).
ipq806x	Qualcomm IPQ806x-based boards.
mvebu	Marvell-based hardware, including the Linksys WRT1900AC/1200AC family.
rockchip	Rockchip-based single-board computers.
custom	A generic/legacy profile predating the project's current per-target structure.

If your device falls in one of these targets, expect to build it yourself (see Building and Flashing) and to do some of your own troubleshooting — these targets aren't necessarily broken, they're just outside what's currently being actively built, published, and tested.

Flashing

• Coming from stock vendor firmware: use a -factory image for your exact model, via your vendor's firmware-upgrade page or recovery method — this varies by device, so check the OpenWrt wiki page for your specific model if you're unsure.
• Already running Gargoyle or OpenWrt: use the -sysupgrade image via Backup, Restore & Firmware Update → System → Update.
• Jumping to a newer OpenWrt base (e.g. from an older Gargoyle release onto one of these 25.12 test builds): don't use "Attempt to Preserve Settings." Config formats changed between base versions, and carrying old settings across a big base jump causes hard-to-diagnose breakage. Back up your configuration, flash clean, and reconfigure from scratch. (Automatic settings migration across a base jump is being worked on, but isn't available yet.)

Every published image has a .sha256 checksum file next to it on the releases page — verify your download against it before flashing.

Something not working on your device?

See Troubleshooting / FAQ, or check/report against the specific test-build discussion on GitHub Discussions — "works fine on this model" reports are genuinely useful too, not just bug reports, since hardware coverage for these builds is still being actively mapped out.

See also

• Building and Flashing — building from source for Tier 2 targets or any customization
• Troubleshooting / FAQ