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

Re: [tor-dev] Potential regression when binding sockets to interface without default route

René Mayrhofer schrieb am Montag, dem 19. September 2016:

> Update: After a hint by Peter Palfrader, I now set the Address option as
> well:
> 
> root@tor2 ~ # grep Address /etc/tor/torrc
> Address 193.171.202.146
> OutboundBindAddress 193.171.202.150
> 
> This seems to work with 0.2.8.7-1, so we should be up and running with a
> recent version now. However, we did not set Address before, exactly
> because we have two addresses assigned for the Tor exit node on this
> host (as opposed to being behind a NAT gateway with port forwarding with
> different internal and externally visible addresses, which might be the
> more common case). Is a setup like ours supported with explicitly
> setting Address?

The address set via the Address configuration option is the one that you
want to see published in the server descriptor.  If it's not set, then
tor will start guessing, and in your case the guess went wrong [1], or
at least changed.

I have Address set even on my non-multihomed, single-IP-address relays.

Cheers,
Peter

[1] And that may be a regression; I haven't looked at that part.
-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev