You don't even need wireguard really, you could just use ssh -D by itself, then either your browser (or foxyproxy) or individual app can point to the local socks proxy, or you can use tun2socks to make a tun(4) network interface out of it. Optionally you can use a network namespace to only route certain apps through it.
Or ssh -w can do the tun(4) interface for you, and supports both layer 2 and layer 3.
True that it won't be using UDP (or sshuttle can fix TCP-in-TCP issues for you), but for my usecase it works out better anyway, as many places I frequent restrict UDP usage. Even China doesn't block SSH.
You don't even need wireguard really, you could just use ssh -D by itself, then either your browser (or foxyproxy) or individual app can point to the local socks proxy, or you can use tun2socks to make a tun(4) network interface out of it. Optionally you can use a network namespace to only route certain apps through it.
Or ssh -w can do the tun(4) interface for you, and supports both layer 2 and layer 3.
True that it won't be using UDP (or sshuttle can fix TCP-in-TCP issues for you), but for my usecase it works out better anyway, as many places I frequent restrict UDP usage. Even China doesn't block SSH.