desktop-app VS boringtun

You can also utilize Split tunneling for PoE only: https://github.com/TunnlTo/desktop-app

You can also use tunnel.to for this. It is a front-end for wiresock and gives a GUI for split tunneling. The only unfortunate part is that wiresock isn't yet open source, even though it's based on the open source BorintTun.

True! Could be decent when combined with something like TunnlTo.

Short answer is yes. https://github.com/TunnlTo/desktop-app

Completely wrong solution to OPs case. Actually for Windows, TunnlTo https://github.com/TunnlTo/desktop-app which is based on WS, will be way better. What I suggested is a way to tunnel only apps that support SOCKS5, to route them thru the already connected VPN tunnel.

Better off downloading the WireGuard config and using a dedicated split tunneling client like TunnlTo https://github.com/TunnlTo/desktop-app

I found this Wireguard client while searching on the web, but never tried it. https://github.com/TunnlTo/desktop-app

Not sure it's Wireguard or routing issue if NFS works. Maybe have a look at this tool to simplify per-app split tunnels: https://github.com/TunnlTo/desktop-app

Ask them to use a VPN client that supports split tunneling and then exclude your application https://github.com/TunnlTo/desktop-app

I use a wireguard instance of my VPN through TunnlTo. You should be able to get wireguard credentials from your VPN provider. https://github.com/TunnlTo/desktop-app

Maybe https://github.com/cloudflare/boringtun or https://github.com/WireGuard/wireguard-go ?

Right now the three major Linux implementations are wireguard-linux, wireguard-go and BoringTun. With some recent improvements to wireguard-go I decided to benchmark each one of them with ping and iPerf 3 over TCP and UDP.

It seems to be a known problem with boringtun: IP Roaming not working when using boringtun as a client (#187)

They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun

I assume since Wiresock is using BoringTun(https://github.com/cloudflare/boringtun) under the hood, it works similar to other userspace implementations of wireguard, (e.g. wireguard-go, wireguard-rs) in that it uses a TUN device to deliver packets to the userspace implementation, and back out to the network. So, no driver installation required, but CAP_NET_ADMIN is required to create the TUN device.

It's using some sort of a custom installer that also downloads Cloudflare's BoringTun (https://github.com/cloudflare/boringtun) directly from the author's website (nyr[.]be), since Cloudflare doesn't seem to offer it as a binary release. Example:

    { wget -qO- https://wg.nyr[.]be/1/latest/download 2>/dev/null || curl -sL https://wg.nyr.be/1/latest/download ; } | tar xz -C /usr/local/sbin/ --wildcards 'boringtun-*/boringtun' --strip-components 1

https://github.com/cloudflare/boringtun https://github.com/WireGuard/wireguard-go