[tahoe-dev] FAQ-type question about ports

[Vladimir Arseniev]

On 12-04-13 04:23 AM, sickness wrote:
> On Fri, Apr 13, 2012 at 04:07:12AM +0400, Vladimir Arseniev wrote:
>> On 12-04-12 04:53 PM, Marko Niinimaki wrote:
>>
>>> what tcp ports do I need to open in order to run Tahoe nodes
>>> and the introducer on different networks?
>>
>> They're in ~/.tahoe/client.port and ~/.tahoe/introducer.port.
>> _______________________________________________
>> tahoe-dev mailing list
>> tahoe-dev at tahoe-lafs.org
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>
> 
> iirc those files are now deprecated, the tahoe.cfg config
> file has to hold the port numbers instead, like this:
> 
>  The value is a comma-separated string of host:port location hints, like
>  this:
> 
>   123.45.67.89:8098,tahoe.example.com:8098,127.0.0.1:8098
> 
>  A few examples:
> 
>   Emulate default behavior, assuming your host has IP address 123.45.67.89
>   and the kernel-allocated port number was 8098:
> 
>    tub.port = 8098
>    tub.location = 123.45.67.89:8098,127.0.0.1:8098
> 
>   Use a DNS name so you can change the IP address more easily:
> 
>    tub.port = 8098
>    tub.location = tahoe.example.com:8098
> 
>   Run a node behind a firewall (which has an external IP address) that has
>   been configured to forward port 7912 to our internal node's port 8098:
> 
>    tub.port = 8098
>    tub.location = external-firewall.example.com:7912
> 
> same is for introducer.port

If that's the case, why do default 1.9.1 installs still write them, and
leave tub.port and tub.location commented out in tahoe.cfg? Is it for
backward compatibility?