> On 24 Jan 2017, at 14:39, Kevin Beranek wrote:
>
>> 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.
To disable the warning, the temp
> 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
> On 24 Jan 2017, at 12:42, Kevin Beranek wrote:
>
> I can answer your questions because I'm the one that filed the issue
> previously referenced by nusenu.
>
>> What are the exact torrc lines?
>
> One relay where I see these log messages has a public address of
> 51.15.48.254 while the releva
I can answer your questions because I'm the one that filed the issue
previously referenced by nusenu.
> What are the exact torrc lines?
One relay where I see these log messages has a public address of
51.15.48.254 while the relevant torrc lines are as follows:
ORPort 10.8.169.135:443
ORPort [200
> On 23 Jan 2017, at 09:16, nusenu 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
> a
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 '
