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

[fred38]

Hi Lantis,

I've been struggling with BETA - 2025-10-24 for quite a while trying to setup a wireguard server on my ASRock G10.
While my wireguard setup worked perfectly fine with openwrt 23.05 codebase, it fails with latest 24.10 builds. In fact, with 24.10-based builds, wireguard client can successfully connect to the router IP (I can properly browse gargoyle UI from my client). However, the client fails to connect to the WAN or to any other host on the LAN (no http, no ssh, no ping).
Nailing down the issue, it appears that the packets stop being routed to the WAN & LAN as soon as I turn on "Enforce DHCP assignments" and assign at least one static address.
I was able to reproduce this weird behavior on both a NetGear WNDR3700v4 and an ASRock G10. The behavior is same with 2025-10-24 and 2026-01-06 builds.
Indeed, the very same setup works perfectly, allowing smooth connection to both WAN & LAN, if I revert back to any 23.05 build (e.g. 2024-11-13) on any of the two routers.
I think openVPN shows same issue, even though I haven't had time to nail it down so clearly.
Cheers.

[Lantis]

Hi Lantis,

I've been struggling with BETA - 2025-10-24 for quite a while trying to setup a wireguard server on my ASRock G10.
While my wireguard setup worked perfectly fine with openwrt 23.05 codebase, it fails with latest 24.10 builds. In fact, with 24.10-based builds, wireguard client can successfully connect to the router IP (I can properly browse gargoyle UI from my client). However, the client fails to connect to the WAN or to any other host on the LAN (no http, no ssh, no ping).
Nailing down the issue, it appears that the packets stop being routed to the WAN & LAN as soon as I turn on "Enforce DHCP assignments" and assign at least one static address.
I was able to reproduce this weird behavior on both a NetGear WNDR3700v4 and an ASRock G10. The behavior is same with 2025-10-24 and 2026-01-06 builds.
Indeed, the very same setup works perfectly, allowing smooth connection to both WAN & LAN, if I revert back to any 23.05 build (e.g. 2024-11-13) on any of the two routers.
I think openVPN shows same issue, even though I haven't had time to nail it down so clearly.
Cheers.

Thanks for the feedback!
I'll need to look more closely at that one and figure out how to keep it working.
The rule isn't supposed to interfere, in theory it works like this:
- If your IP or MAC is not known to us, skip the next 2 rules
- If your IP is known and your MAC doesn't match, reject
- If your MAC is known and your IP doesn't match, reject
- Accept

So WireGuard (+OpenVPN) clients should be bypassing at that first rule, but clearly something is amiss.

It probably worked fine on the earlier versions because that Enforce DHCP Assignments function was pretty much broken

So for now leave it off if you can and I'll take a look. If I've got something to test I'll send you a PM

[fred38]

Thanks for this quick response.
I unfortunately need forced DCHP assignment and wireguard. For now, I have reverted back to some older 23.05-based image on my G10. Hence I am clearly not blocked.
Anyhow, feel free to share some trial WNDR3700v4 image, whenever you have time to look into it, and I'll be happy to give it a try

BTW, I forgot to mention that I had been running 24.10 images for the past 3 months, on the G10, in a trial configuration as a basic internet gateway (without wireguard or openvpn) and it proved to be very stable. This is great job already !!!