rsp VS transocks

BTW, here is SSH proxy which uses pool of steady connections: https://github.com/Snawoot/rsp

I used this feature pretty often, but it has one downside: all connections are multiplexed into single one which is not good for performance.

So I've implemented own client which decouples connections from each other: https://github.com/Snawoot/rsp#performance

Basicly, you get working proxy with speed almost as native connection as soon as you have SSH access somewhere.

I don't think you can generally expect all processes to transparently use a SOCKS proxy? You might be able to finagle a custom vpn around it, I suppose. But AFAIK SOCKS isn't 100% transparent at the IP layer allowing all protocols to transparently layer on top?

I guess SOCKS5 handles tcp and udp - so you might get away with redsocks (which explicitly recommends against using with TOR):

https://github.com/darkk/redsocks

See also transocks (SOCKS4 tcp only): https://transocks.sourceforge.net

And transocks (in go) https://github.com/cybozu-go/transocks

There are solutions which allow to redirect transit TCP connections into SOCKS proxy transparently: https://github.com/cybozu-go/transocks

So, yes, VM/router solution will work for TCP connections.

Also there are wrappers which can intercept connect calls to libc from applications on Linux (which is useful if you need to redirect only one application which doesn't support SOCKS proxies): https://linux.die.net/man/8/tsocks