Gargoyle 1.15.x OpenWrt 24.10 beta - 2025-08-03

[Lantis]

Gargoyle 1.15.x based on OpenWrt 24.10 is a beta version switching Gargoyle to the latest stable release from OpenWrt. This also includes the previous beta changes switching from iptables to nftables (firewall3 to firewall4).

While I do not recommend keeping settings between OpenWrt 23.05 and 24.10 based versions of 1.15.x, in theory they are compatible for most devices. Proceed with caution.

Configs should generally not be preserved between 1.14 (and earlier) and 1.15.x. Do so at your own risk.

Please provide your feedback (positive or negative). If you do think you've found a problem it would be incredibly helpful if you also verified that the problem did not exist on the 23.05 based 1.15.x builds. I'm happy to fix bugs that also existed there, but will be focusing on regressions first.

Changes since "BETA - 2025-07-13":
- Fixes for PPPoE wan_6 interface not triggering the Gargoyle firewall rules to reassert
- Fixed firewall port range rules not working (incorrect separator)
- Add additional handling for wan_6 through several firewall scripts
- Fix PPPoE masquerading
- Fix port forwarding loopback rules not applying due to syntax error
- Fixed some QoS rules not applying due to tcp/udp protocol syntax error
- Fixed the iptables version of webmon not loading old data (to help out our friends over at Tomato64)

Changes since "BETA - 2025-07-02":
- Added Raspberry Pi 5 support (bcm2712)
- Fixed scanning for a wifi network to connect to
- Fixed wireless clients not showing in the GUI
- Updated packet steering options in GUI (thanks @aimacintyre)
- Silenced an error when IPv6 WAN/LAN addresses are not present
- Fixed restriction/whitelist firewall rules not generating if more than 1 IP or MAC address was specified
- Fixed WebMon not starting if the WAN was down
- Cleaned up some parameter quoting in the nftables ruleset printing for custom modules
- Fixed OpenVPN rules not clearing on restart
- Fixed webMon not restarting correctly if the firewall restarts (due to ifup of interface other than WAN)
- Reduced the number of rules generated by restrictions/whitelists when multiple IP or MAC addresses are specified

"BETA - 2025-07-02" Notable changes:
- Switched Gargoyle to OpenWrt 24.10
- Switched OpenVPN to version 2.6
- Switched mbedtls-clu to 1.1.0dev
- Switched to nftables and firewall4 (fw4)
- Bulk updated many packages


Known Issues
- Samba shares utilising ksmbd will not work if "Same folder on all disks" option is selected


Downloads
Please find the downloads here
The plugin repositories are also found in the same location.

Blog Post
Click here to read this article on Tales from @Lantis

[rg66]

Did a new build based on the latest commit (5575828) and no real issues so far after 24+ hrs. Runs the same as the first 24.10 and the latest 23.05. Still getting the IPv6 errors when saving though.

Thanks

[angus]

Hi Lantis,
Meet an issue after using this firmware on my WRT3200ACM. Please take a look. Thanks.

• Nothing is seen from the WebUI Status/Connected Hosts/Connected Wireless Hosts even if there are Wi-Fi clients connecting to the router.
  https://mega.nz/file/GV4jUB6Q#C_ACYMmxl ... B9sO3qgbQA

[Lantis]

I’ll look at silencing the IPv6 error, it is however harmless.

The ssh error is likely a local issue, assuming that you are using password login and not ssh keys. You need to check your ssh client has appropriate ciphers available. PuTTY (latest) has no issues, for your reference.

I will look at the wifi client list thanks.

[angus]

The ssh error is likely a local issue, assuming that you are using password login and not ssh keys. You need to check your ssh client has appropriate ciphers available. PuTTY (latest) has no issues, for your reference.

Indeed. Issue is resolved since PuTTY is upgraded. Thanks.

[angus]

I will look at the wifi client list thanks.

Thanks Lantis. I'm used to check Connected Wireless Hosts for the band steering functionality. Any other means to achieve same?

[rg66]

I’ll look at silencing the IPv6 error, it is however harmless.

No worries. You mentioned they were harmless when I first reported it and, as you said, they cause no issues at all. I just figured you'd want to know.

Cheers

[Lantis]

The wifi client list is fixed by this patch. It also fixes scanning for networks to connect to.
https://github.com/ericpaulbishop/gargo ... 3b8eb1f7c0

[angus]

Client list is back after applying the patch. Thanks.

[angus]

Hi Lantis,
Access restrictions via MAC addresses are not working. Can you please take a look at this?
Thanks.