any eta on udp static routing?

[Ferixy]

‌

[kubrickfr]

At this point why use wireproxy and not just a wireguard client?

[GalayZloy]

I also need UDP support because voice communication does not work in Discord (web).

[GalayZloy]

At this point why use wireproxy and not just a wireguard client?

Because the WG client tunnels all traffic in the system, there is no way to choose which application will work through the VPN and which directly, as can be done in the Android client.

[kubrickfr]

Because the WG client tunnels all traffic in the system, there is no way to choose which application will work through the VPN and which directly, as can be done in the Android client.

This is simply not true.

Assign your wg configuration to a specific routing table (one line of configuration) and 🎉 it doesn't affect anything unless you specifically make it target this table.

Then launch the apps you want routed via wg in a cgroup that has this table assigned to it.

[mid-kid]

@kubrickfr can you elaborate on your method? I can't find any documentation on this that I understand. I found wireproxy significantly more convenient (every relevant app suppports socks proxying), but I'm hitting the limits of TCP-only.

[windtf]

Supported added in #187

[kubrickfr]

@mid-kid It looks like the cleaner way to do this nowadays is with network namespaces rather than with cgroup CLS. Great documentation can be found here: https://www.wireguard.com/netns/

This way you can launch a wireguard connection affecting nothing but what you launch in that namespace, which can be a browser or whatever you want.

[mid-kid]

@kubrickfr Thanks! Everyone I've asked pointed me to it, but I really can't make heads or tails of it. Network routing is utterly confusing to me, and that documentation assumes you know how it works. Namespaces don't make it any easier to understand...

What I found somewhat worked is setting Table = off in the wireguard configuration. Some applications support then selecting the wg0 interface to connect to (e.g. curl --interface wg0), but support for that isn't as ubiquitous as socks5 support in applications is. There's no documentation on this method anywhere on the internet, I had to poke some people on discord...
It works for my current use-cases at least, and I can use wireproxy for everything else <3