| So at this point it is ready for passing traffic through a SOCKS proxy. Meaning we can `cargo run --release -- proxy` and redirect applications to use port `9150` for their network connections. Couple of related questions: - Does anyone know, in a Linux distro, how to pass all system traffic through a SOCKS proxy port? I'm not looking for intermediary proxy handlers but an official method to force all user and system apps to use an arbitrary port. - If it is not possible to do so, does `NetworkManager` have a setting for this? - Is it possible to at least change Chrome/Firefox ports via CLI to an arbitrary port? |
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
Ed: see also https://news.ycombinator.com/item?id=30684574