tinc - Dec 2014 - additional Port entry in tinc hosts key file

Hi,

I am using tinc version 1.1pre10, and I am generating the key file using
command below ...

/usr/local/sbin/tinc -n myvpn init hostname

In some of the host file I am seeing a new line  "Port = 29732"  added
at
the end of the host key file...

/etc/tinc/myvpn/hosts/hostname

Port = 29732

this line Port = 29732 is causing tinc to break. It all works fine once I
manually delete the Port entry in the key hosts file.

My tinc.conf looks like this....

Name = myhost
Mode = switch
ExperimentalProtocol = no
ProcessPriority = high
Port = 655
ConnectTo = otherhost

Any idea on what would cause that extra Port entry in the file?  How can I
ensure it not added automatically?

Thanks,
Anil
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20141218/f2161e0c/attachment.html>

On Thu, Dec 18, 2014 at 04:41:24PM +0530, Anil Moris wrote:
> In some of the host file I am seeing a new line  "Port = 29732" 
added at
> the end of the host key file...
[...]
> Any idea on what would cause that extra Port entry in the file?  How can I
> ensure it not added automatically?
This line is added automatically when you run tinc init and port 655 is
already in use. In that case, tinc automatically chooses a random unused
port, and adds it to its own host config file so it will use that port
in the future. It also prints a warning when this happens. For example:

$ sudo tinc -n foo init bar
Generating 2048 bits keys:
...+++ p
...................................................+++ q
Done.
Generating ECDSA keypair:
Done.
Warning: could not bind to port 655. Tinc will instead listen on port 28530.
> this line Port = 29732 is causing tinc to break. It all works fine once I
> manually delete the Port entry in the key hosts file.
What do you mean by "break"? Does tinc crash? Does it quit with an
error
message? I tested your configuration, and it works. It uses the Port
specified in tinc.conf. Of course, if port 655 really is in use already
it will exit with this error message:

Can't bind to 0.0.0.0 port 655/tcp: Address already in use
Can't bind to :: port 655/tcp: Address already in use
Unable to create any listening socket!

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20141220/d9ffea6f/attachment.sig>