[tor-dev] log: ORPort/DirPort address does not match descriptor address
nusenu
nusenu at openmailbox.org
Sun Jan 22 22:16:00 UTC 2017
Hi,
how bad is it to simply ignore ORPort/DirPort address mismatch log entry
on a relay behind (1:1) NAT?
I assume tor figures out the public IPv4 address anyway, no?
The IPv4 ORPort address 192.168.1.1 does not match the descriptor
address 1.2.3.4. If you have a static public IPv4 address, use 'Address
<IPv4>' and 'OutboundBindAddress <IPv4>'. If you are behind a NAT, use
two ORPort lines: 'ORPort <PublicPort> NoListen' and 'ORPort
<InternalPort> NoAdvertise'.
I'm explicitly specifying (private) IP addresses in ORPort/DirPort (and
OutboundBindAddress) lines to avoid binding to the same ports when
running >2 instances (with >1 public IP).
https://github.com/nusenu/ansible-relayor/issues/101
thanks,
nusenu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20170122/f85afe1d/attachment.sig>
More information about the tor-dev
mailing list