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 !!!

[Festusdog]

Jan 6, 2026 beta. Possible issue with QOS Upload when in wireless bridge repeater mode.

Config: 2 identical wrt3200acm, one as main router, one as wireless bridge repeater. Both using Jan 6 beta firmware. Main router is configured to isolate wireless clients but otherwise standard config. Repeater has QOS upload enabled and set. qOS download isn't set (default)

Trying to use QOS on the wireless bridge repeater to limit UPLOAD speed on all devices that connect to the repeater

It doesn't seem to be working as I expect.

On the repeater, I enabled QOS, deleted the Fast rule leaving only the normal rule.

Set the upload speed connection to 1 kbps. (Tried other speeds too, such as 50, 100, 200)

Saved settings. Tested, didn't seem materially different.

Also next tried editing the NORMAL rule to set the minimum and maximum upload speed to 1, or 50, etc.

On the main router, I check the bandwidth usage by IP address and When I observe the bandwidth used by the IP address of the device connected to the repeater, the amount of data uploaded in an hour exceeds what I would expect for a QOS upload limited to, for example, 1 kbps.

For example, I am seeing approximately 1MB still getting uploaded per minute. I might be wrong, but that seems to be exceeding the 1kbps that I set it to. I actually haven't tested to see if more is getting thru, but I know for sure that is getting thru just watching the upload bandwidth graph for that IP on the main router.

Of course, 1kbps is probably not practical but I set it to the minimum just to see if the upload was effectively shut off, and it doesn't seem to be.

Am I doing this wrong?
Does QOS work when the device is being used as wireless bridge repeater mode?

I researched the topic and I was pretty sure that QOS should be useable even in repeater mode.

Thanks.

[Lantis]

QoS is only coded to work on WAN. The menu item should be hidden.
I suppose in theory it could be made to work but at the moment all of the code explicitly expects a WAN connection, which a bridge repeater is not.