> On 23 Jan 2017, at 09:16, nusenu <nusenu@xxxxxxxxxxxxxxx> wrote: > > 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 What are the exact torrc lines? I don't think this warning should be triggered in the setup you describe, but I'll need to re-read the code to check. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev