Why does the tor guide uses the transparent proxy (transproxy) for tcp intercept instead of the socks5 proxy?

This guide https://openwrt.org/docs/guide-user/services/tor/client

Why not the socks5 proxy?

I haven't tried using socks5 to be honest, but I don't think I'll find out if I do. (Like if it doesn't work and I lose internet connection, I would still not know why it doesn't work)

I would like to use socks5 for consistency sake and because it might be faster (I don't think it's significantly beneficial)

@vgaetera tag because you are a main contributor to that article? So you did it? I am not sure if it's okay to tag you

Because, the 2 are not the same.

Tor has support for transparent proxy connections in addition to SOCKS connections.

~ from: https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TransparentProxy

(Feel free to look directly at the TOR manual too.)

1 Like

oh, I read that same page but I misunderstood. I thought the transparent proxy was the tor https proxy

I am reading more on it now through other sites, this is a new term for me. Thanks

Edit: After reading multiple websites, I still don't understand why socks5 can't be used to intercept all tcp connections. The only thing I am told by these websites is that transparent proxy is designed for this but socks5 is not, but some websites also tell me that socks5 can do tcp interception. (note: I didn't mean to post this edit, I wanted to try it first)

The idea is to force client traffic to Tor no matter the client side settings.
Using SOCKS5 requires explicit configuration and support by all client apps.

1 Like