Gargoyle Forum

Assuming your PC is 192.168.1.2?
In the download direction your PC is the destination, not source. That should fix it

Thanks for the feature suggestion, it's not something I'm likely to add here but I'll look at it in another space. If you are maintaining your own builds, I would create a new patches-generic which patches the file target/linux/ipq40xx/base-files/etc/board.d/02_network, Line 67 ucidef_set_interface_...

Then clear the half-built libnftnl so it re-extracts from scratch, otherwise you will keep hitting the corrupted Makefile: rm -rf /data/gargoyle/mediatek-src/build_dir/target-aarch64_cortex-a53_musl/libnftnl-1.2.8 and rebuild. This is not sufficient. The netfilter patching routine runs once for a b...

This is a little out of the scope of Gargoyle unfortunately as you're now adding additional networks which aren't UI supported. It can be done but it might be very quickly undone the next time you press Save Changes anywhere. What you're wanting to do is a bit like what we used to use Hamachi for ba...

Yes you should be able to
Thanks ispyisail for spotting the issue.

I just noticed your WAN is 192.168.1.1. Is your work laptop on that subnet at the work location as well? It may be trying to send replies out to WAN instead of back out the tunnel. To isolate this I would check over a cellular connection (if you can) or try a WireGuard client on a phone. The phone c...

Maybe we should check your firewall and network configs look ok. Set up WireGuard as you did, then cat /etc/config/firewall cat /etc/config/network Be sure to redact your WireGuard keys and any passwords that might be precious to you. One thing I’d try quickly is setting “use for all traffic” rather...

So while we work on the code to help stop you (and others) from shooting yourself in the foot, let's explain what the feature actually does so you know why you didn't need to touch it. If your WireGuard client is another router, and that router has another subnet behind it, and you want them to be a...

Do you have a more complete description of how you configured it? The couple of ways I know for really locking yourself out are: - setting the WireGuard subnet to the same as your existing subnet (just leave it as the default) - setting a client routed subnet to the same as any subnets Gargoyle alre...

Also I was surprised to see patch 022 still in the tree? APK hates non standard package naming. Was something done to fix this?