Why is the Tor proxy running on 0.0.0.0:9050 and not on IPfromIPfire:9050? Also in the log there is the warning
Tor[10169]: You specified a public address ‘0.0.0.9050’ for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
When I connect to the Tor proxy, the website https://check.torproject.org/ does not recognize that I am using Tor.
With other external Tor proxies it works and with the Tor browser too.
Why is the Tor proxy running on 0.0.0.0:9050 and not on IPfromIPfire:9050?
this is because restricting access to Tor’s proxy port is currently done via firewall rules, not via the listening directives in Tor’s configuration.
When you start Tor as a client, access to it will be automatically restricted to the CIDRs you specified by the firewall engine. Tor, however, can’t know about this, so it logs this warning either way.
Thanks for your fast answer.
ok, that means that the Tor proxy will always be started in the network that I enter under access control
of the allowed subnets, or what IP does the SOCKS proxy get assigned otherwise?
I have now simply entered the IP of the proxy in the config of Tor, that also works.
That seems to be resolved, my first attempts showed that I am not using Tor (“Sorry. You are not using Tor.”) but now it shows me “Congratulations. This browser is configured to use Tor.” All fine now.
Is this actually a transparent proxy?
Because I use the IpfireTorProxy on a different port than the TorBrowserbundel itself.
I also have several SSH tunnels configured to HTTP proxies, some of which also use Tor.
The wiki says you should turn off the integrated proxy when using the TorBrowser to avoid a Tor-over-Tor, but the linked HowTo talks about a transparent proxy for Tor-over-Tor. But if I use different ports, it’s all separated, isn’t it?
