[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Binding Tor to Pseudo-Interface

That did it, thanks much! Obviously I need to do a better job of
R(ing)TFM. My apologies.

One more problem (at least at the moment), my three roommates are
getting the Google spyware/virus page. This isn't making them happy
for some strange reason. I would really lie to continue to have an
exit node that supports port 80. Is there anyway around this? None of
them are using Tor...


On Sat, Feb 23, 2008 at 5:47 PM, Arjan
<n6bc23cpcduw@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Jonathan Addington wrote:
>  [...]
> > My remaining problem is that while Tor listens and responds to other
>  > Tor clients via this pseudo-interface (and hence different IP) it
>  > still fetches information as an exit node from the
>  > non-pseudo-interface, making it much more difficult to filter (I don't
>  > want to deprioritize *my* web-browsing as well!).
>  >
>  > Is there a way to bind Tor so that it *only* uses the pseudo-interface?
>  Maybe this works:
>  OutboundBindAddress ip.of.pseudo.interface