Therefore the internet application will attempt to do the DNS resolution itself using the system, not using the proxy. The complication (and also advantage/feature) with transparent proxying is, that the internet application (browser, etc.) is not aware of the proxy.

Rather redsocks can convert UDP DNS queries to TCP DNS queries. If you were to use a http proxy (no https, without connect-method, see proxy article), you could access only http sites, no https sites. Redsocks can also accept 'Trans data streams' and can forward them to http s, socks4 and socks5 proxies. You must also keep in mind, that Tor does not support UDP, although it offers a DnsPort. Tor is a socks proxy and also has a TransPort. Below we discuss a few tools which help here, not all are required, depending on what you want to do. Because most proxies are either http or socks we need to translate this. In most other cases, you need to translate the different kinds of data.ĭue to the nature of Transparent Proxying, we need to redirect with iptables and end up with a 'Trans data stream'. Unfortunately very few applications, do offer a TransPort. In case you redirect the network layer directly with iptables, you need a TransPort. There are CGIproxies, http(s) proxies and socks4/4a/5 proxies.

You always have to keep in mind, which kind of data and which kind of proxy you are using. Use case: a user wants to ensure all traffic goes through Tor (by using Whonix-Gateway ™) and want to additionally ensure, all traffic goes through a proxy choosen by the user after the Tor link, i.e. This section is about configuring Whonix-Workstation ™ also to act as a Transparent Proxy. Whonix-Gateway ™ is already serving as a Transparent Proxy, which means, that all applications not explicitly configured to use a SocksPort, can connect through Tor without any settings. 4 How to setup proxy tunnel-link after Tor (User→Tor→Proxy→Internet).

Can you use tails as a tor proxy