Gargoyle Forum

Made your proposed changes (1 line add + 1 line change). No change in behaviour. Summary of behaviour I've observed: #1 - AllowedIPs = x.x.x.x/xx - all is good #2 - AllowedIPs = x.x.x.1/32,x.x.x.0/24 - no routes added #3 - AllowedIPs = x.x.x.0/24,x.x.x.x1/32 - route only added for /24 entry In all 3...

The following is a line from the uploaded config file in the peer section: AllowedIPs = 192.168.14.0/24,192.168.21.1/32 A route does get added for the 192.168.14.0/24 but without the mask (in the gui > 192.168.14.0 instead of 192.168.14.0/255.255.255.0). No other routes are added. As a workaround, I...

More info after some testing:

Issue 1 - it seems like a route is created for only the first item of the AllowedIPs parameter.

Issue 2 - seems to be resolved with my current config. I did not track the various changes to determine what exactly caused the issue. Consider it resolved.

Thank you.

Issue 1 - referring to downloadable config file. Issue 2 - Gargoyle is the client. Raspberry Pi OS running bullseye is the server. I tried both drop down options in gargoyle gui (allow non-wireguard and not). Behaviour was the same for both. Tunnel traffic was good. All other traffic was blocked. As...

v1.13.0 and wireguard working well on WDR4300 v1.7. Enjoying the excellent firmware on several different devices. I noticed a couple of minor issues with the wireguard implementation. Issue #1: It seems you can only include one network in the AllowedIPs line of the Peer section in the wireguard conf...