Changes between Initial Version and Version 1 of Ticket #13953, comment 24


Ignore:
Timestamp:
Aug 12, 2016, 1:01:34 PM (3 years ago)
Author:
s7r
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13953, comment 24

    initial v1  
    11On second thought, won't be possible to make this warning automatically go away with this simple logic:
    22
    3 If the address explicitly configured with ORPort, if and only if, is a '''public IP address'''  - let's call this '''or-address'''' (and it also matches the DirPort address?), Tor will automatically assume `Address == or-address` and `OutboundBindAddress == or-address`. This requires that the ORPort line to be used must not contain a `NoAdvertise` option.
     3If the address explicitly configured with ORPort, if and only if, is a '''public IP address'''  - let's call this '''or-address'''' (and it also matches the DirPort address?), Tor will automatically assume `Address == or-address` and `OutboundBindAddress == or-address`. This requires that the ORPort line to be used must not contain a `NoAdvertise` option. I think this could be a sane default, since it's clearly the intent of any user that specially configures an ORPort <public IP address>:<port> line in torrc.
     4
     5This will ensure:
     61. We are not breaking any existing torrcs.
     72. We avoid an additional warning in the log file which could confuse users who don't know so much about networking stuff.