On 1/17/12 5:41 PM, Nick Mathewson wrote:
>>>
>>> ORPort 1337 no-advertise alladdrs
>>> ORPort tornode.example.com:443 no-bind alladdrs
>>
>> This drives home the issue with alladdrs: what would we do if that flag
>> isn't listed here?
This feature would allow a single node, for example,
On Sun, Oct 23, 2011 at 1:26 PM, Roger Dingledine wrote:
> [Quoting the original mail, but it's actually the file in git that I
> read and am commenting on.]
>
> On Wed, Sep 21, 2011 at 02:13:18PM -0400, Nick Mathewson wrote:
>> The 'AllAddrs' option tells Tor that if no address is given in the
[Quoting the original mail, but it's actually the file in git that I
read and am commenting on.]
On Wed, Sep 21, 2011 at 02:13:18PM -0400, Nick Mathewson wrote:
> The 'AllAddrs' option tells Tor that if no address is given in the
> PortDescription part, we should bind/advertise every one of ou
On Thu, Sep 22, 2011 at 3:43 AM, Karsten Loesing
wrote:
> Hi Nick,
>
> a few comments to proposal 186 below:
>
> On 9/21/11 8:13 PM, Nick Mathewson wrote:
>> In consonance with our changes to the (Socks|Trans|NATD|DNS)Port
>> options made in 0.2.3.x for proposal 171, I make a corresponding
>>
Hi Nick,
a few comments to proposal 186 below:
On 9/21/11 8:13 PM, Nick Mathewson wrote:
> In consonance with our changes to the (Socks|Trans|NATD|DNS)Port
> options made in 0.2.3.x for proposal 171, I make a corresponding
> change to allow multiple SocksPort options and deprecate
> Socks
Filename: 186-multiple-orports.txt
Title: Multiple addresses for one OR or bridge
Author: Nick Mathewson
Created: 19-Sep-2011
Supersedes: 118
Status: Draft
Overview:
This document is a proposal for servers to advertise multiple
address/port combinations for their ORPort.
It supersedes prop
