Gargoyle Forum

On the latest versions of Gargoyle you would also turn on Packet Steering to help with spreading the load.

Yes that’s the one.
Note to the original posters who were INSISTING it was supported in 2020… support was merged in 2024.

I think it should handle it… do you have QoS or anything else enabled that might impact that?
My Flint2 has handled the upgrade just fine.
I could probably unpack my wrt32x and check, but it is a slightly different cpu so it would not be a fair test. Would you like to see that comparison?

The 3 zeroes in a row stands out to me. We save the bandwidth data to disk every 4 hours. I am aware at the moment that the firewall gets torn down much more regularly than it did in fw3 and we aren't able to grab the bw data when this happens, and you'll lose up to 4 hours of data each time. I need...

j6mm wrote: ↑

Wed Sep 10, 2025 4:17 pm

There seems to be a problem with saving of bandwidth monitor data in this version. For most intervals the values are 0.000. It works correctly in 1.15.x owrt 23.05.

Does it show correctly in the UI and the download is corrupt or wrong everywhere?

Nice one!
Patch 102 simply enables VHT80P80 mode which is 80+80MHz (or 160MHz split).
Your device is capable of this mode, but it’s not that useful as it cuts the number of spatial streams in half.
Up to you if you want to fix it to apply properly, I’d probably leave it out

Yep I reckon you can just swap that out no problem. Merge the configs to get the NSS components. The custom feeds I’d probably just clone those and merge them into the Gargoyle packages folder for simplification. Or you can copy the method that Gargoyle used for “build custom” where it grabs all Ope...

Can you link the fork so I can take a look? Basically the way Gargoyle build scripts work: 1. Establishes global variables (language settings, target and profile) 2. Shrinks JavaScript and CSS to minimise space 3. Downloads OpenWrt source code to the “target-src” folder 4. Copies the right config in...

I believe that host name will always resolve to these 4 IPs I’ve listed, that’s why I had hoped the rule is allowed to be this simple. There are definitely more complicated rules we can implement with domains, but we need to swap out dnsmasq for a fully featured version and while I was testing the s...

So I was thinking more on this and blocking the domain name may not be necessary (at least for cloudflare). We can probably achieve this with simple IP based rules. Try this out. nft insert rule inet fw4 forward_lan tcp dport 853 reject; nft insert rule inet fw4 forward_lan ip daddr { 1.1.1.3,1.0.0....