Option to turn off listen port, e.g. client only mode

[Michael Tokarev]

14.05.2014 18:24, Kenth Andersson wrote:
> Hey,
> 
> I have this setup on my small test tinc-vpn.
> 
> HostA (runs on a server and is publicly accessible)
> 
> HostB (runs on my laptop (behind firewall) sometimes and connects to HostA)
> 
> HostC (runs on a Amazon AWS server (behind firewall) to test long uptime and connects to HostA)
> 
> This setup allows me to communicate from HostB to HostC thru HostA without any issues.
> 
> Everything works great, but I have a feature request I’m not sure if this is the correct place for it, but since HostA in my case is the only host that accepts incoming connections (both the other hosts are behind firewalls) I would like to set Port = -1 on both HostB and HostC in tinc.conf to tell them to NOT listen for incoming connections, since there is no way they will ever get one. 

The Port directive specifies 2 ports - one TCP for incoming _connections_,
and another, which is more important, is UDP to receive packets sent your
way for the inside-tunnel data.
> 
> Why do I want to do this? Basically I don’t want to take up a port just for having a listen socket on port 655 that no one is ever going to connect to.

Are you short of ports?  You have another 65535 - 1 ports to use.
Srsly, I just see no point.

Thanks,

/mjt