Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Want to share your OpenWrt / Gargoyle knowledge? Implemented a new feature? Let us know here.

Moderator: Moderators

ispyisail
Moderator
Posts: 5270
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by ispyisail »

I'm not sure of Lantis plans

Lantis
Moderator
Posts: 7359
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia
Contact:

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by Lantis »

I will find time to merge them upstream and compile, but I now have a backlog of changes to review first.
I had a large influx of changes to review in a single 48 hour window and more have followed.
It takes time.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
https://lantisproject.com/blog

ispyisail
Moderator
Posts: 5270
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by ispyisail »

I had a large influx of changes to review in a single 48 hour window and more have followed.
It was a mistake :)

I blame AI, its the devil i say

fiye68
Posts: 8
Joined: Wed Feb 02, 2022 12:13 pm

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by fiye68 »

ispyisail wrote: ↑
Thu Jun 25, 2026 3:02 am
@fiye68

Thanks for the detailed log — it made the bugs straightforward to track down.

There are two separate problems here:

1. nftables script bugs (now fixed)

Found five issues across three files in the gargoyle-tor package, all nftables migration problems:

Also fixed the CPU spike: update_tor_nftset was calling nft add element once per relay IP (~10,000 times per minute). Replaced with a single batched nft -f - call.

PR submitted: https://github.com/lantis1008/gargoyle/pull/59

2. RAM (hardware limit — not fixable)

The OOM kill at 50% bootstrap is a separate problem:

Code: Select all

tor pid 6631 — 60484kB virtual, 51380kB RSS → killed by OOM
Tor needs ~50 MB just to load relay descriptors. With Gargoyle's full stack running on 128 MB that leaves no headroom. OpenSSL 3 has increased Tor's memory footprint and this appears to be the new floor. The WRT3200ACM won't be able to
run Tor reliably regardless of the script fixes — 256 MB is the practical minimum now.

If anyone has confirmed working hardware on current Gargoyle + Tor I'd be interested to know the model.
Thanks a lot for taking the time to fix these ispyisail and for generally helping Lantis, I wish I had you skills so that I could be of further assistance besides testing and logging!

If the fixes were in part aided by automation tools, I am sure that they were thoroughly checked before merging them to ensure the continuous quality of gargoyle's code.

When there is time and suitable hardware, I will try to test Tor on routers with faster CPU and larger RAM and report back.

karenmcd
Posts: 28
Joined: Tue Jan 26, 2016 8:41 pm

Re: Gargoyle 1.15.x OpenWrt 24.10 beta - 2026-01-06

Post by karenmcd »

hello,

to start off as a disclaimer, the forums and website were not working properly for me for a few days, and i consulted duck.ai. it helped me get updated and fix some things, but it also got me thinking to ask some questions about some package updates. specifically dnsmasq 2.90-r5, dropbear 2024.86-r2 and libopenssl3 3.0.20-r1

current versions seem to be
(from opkg info)
Package: dnsmasq
Version: 2.93-r1

Package: libopenssl3
Version: 3.0.22-r1

(from github)
dropbear 2026.94

im still using this on my openwrt1900acs and not using the E8450-CA yet. Would it be better to unbox the e8450-ca and test updating those packages on it, or is it safe to upgrade dnsmasq and libopenssl3 with opkg -force upgrade?

on my laptop, do i just

Code: Select all

make PROGRAMS="dropbear dbclient dropbearkey dropbearconvert scp" MULTI=1
? and then move them over to the router? (build instructions from dropbear git) or do i need to have some fun learning to build gargoyle?

Thanks!

Code: Select all

# ubus call system board
{
        "kernel": "6.6.141",
        "hostname": "Gargoyle",
        "system": "ARMv7 Processor rev 1 (v7l)",
        "model": "Linksys WRT1900ACS",
        "board_name": "linksys,wrt1900acs",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.7",
                "revision": "r29197-ab4c7d6af7",
                "target": "mvebu/cortexa9",
                "description": "OpenWrt 24.10.7 r29197-ab4c7d6af7",
                "builddate": "1779897308"
        },
        "gargoyle": {
                "distribution": "Gargoyle",
                "version": "1.15.X",
                "revision": "258f85a8",
                "target": "mvebu",
                "profile": "default",
                "description": "1.15.X (Built 20260613-1323 git@258f85a8)"
**PS - could this post be moved to the non-beta forum post? i accidentally clicked the wrong post to reply to! thanks!**

Lantis
Moderator
Posts: 7359
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia
Contact:

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by Lantis »

Generally high risk in updating core packages like that.
Any compiling you do needs to be cross compiled to suit the router, not your PC. It is generally easier and safer to use the full build environment.

But taking a few steps back, what specifically do you want to upgrade (from and to versions) and why? Perceived benefit or bugs resolved?
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
https://lantisproject.com/blog

karenmcd
Posts: 28
Joined: Tue Jan 26, 2016 8:41 pm

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by karenmcd »

im just trying to stay on this build of gargoyle i got updated to, the June one based on 24.10. duck.ai said you might have built 24.10 on versions of dropbear, dnsmasq and libopenssl3 that have the fixes backported, so i figured i'd ask here.

im hoping/looking to benefit from the fixes to dropbear: cve-2019-6111, cve-2026-35385, dnsmasq: CVE-2026-2291, and a slew of cve's from https://openssl-library.org/news/openss ... index.html

primarily because i use this router to host games servers, a synapse server, a file server for my home and recreational home lab use; it's WAN facing, so i'd like to make sure ive done all i can to keep out the trolls (o:

I was prompted to update when a disgruntled gamer someone managed a denial of service attack on my router. the DDoS was solved by updating to 1.15.x owrt 24.10 lantisproject build, and the individual updates are to mitigate the leftover vulnerable attack surfaces, at least according to duck.ai and what i can gleen from privilege escalation attacks/rec CVEs that seem indeed credible and reasonable. duck.ai had a lot to say that ive tried to parse through the bullshit and focus on what i think actually matters.

should i copy your repo and just try learning to build it then? i have built aosp and lineageos for my own device trees in the past, and might need some handholding, but down to try this too!

Lantis
Moderator
Posts: 7359
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia
Contact:

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by Lantis »

If you do a compile off my latest code you'll be good to go for most of it. I've just bumped to the latest OpenWrt commit and am doing a test build on my end. If that's ok I'll push that up too.
https://github.com/ericpaulbishop/gargoyle

I'm working with Eric to be able to do a new release version. It will take a bit of time as this will be the first time we exercise this method. Hoping within a few weeks.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
https://lantisproject.com/blog

Post Reply