[tor-dev] log: ORPort/DirPort address does not match descriptor address

Kevin Beranek kevin at kberanek.com
Tue Jan 24 03:39:20 UTC 2017


> Is the Address option set on this relay?

Address is not set because it is generated from this template, which
does not set Address:
https://github.com/nusenu/ansible-relayor/blob/dev/templates/torrc.

> Maybe we need to change this part of the warning:
>> If you have a static public IPv4 address, use 'Address <IPv4>'

I'm not quite sure what you're proposing.  Are you suggesting dropping
just the "and 'OutboundBindAddress <IPv4>'" or the rest of the
message?

> If the address option isn't set, what does the relay identify as its
> public IP address in the logs?
>
> Look for log entries about testing ORPort or DirPort reachability, or
> any log entries containing its public IP address.

It definitely identifies the correct public IP address as you can see
from these logs:

Now checking whether ORPort 51.15.48.254:443 and DirPort
51.15.48.254:80 are reachable... (this may take up to 20 minutes --
look for log messages indicating success)
...
Self-testing indicates your DirPort is reachable from the outside. Excellent.
Self-testing indicates your ORPort is reachable from the outside.
Excellent. Publishing server descriptor.


More information about the tor-dev mailing list