tinc - Oct 2018 - Tinc invite options

Dear All,



We are trying the Tinc invites to let nodes join the network.

This is working as described but we want to push some configuration for
some nodes but this seemed not to be working.



What is working is the following invite:



Name = test_invite

NetName = test_VPN

ConnectTo = test_hub01

Ifconfig = 172.16.1.4/24

Subnet = 172.16.1.4

#---------------------------------------------------------------#

Name = test_hub01

Address = test_hub01.foo.bar

Subnet = 172.16.1.1

Subnet = 172.16.1.0/24

Port = 6555

-----BEGIN RSA PUBLIC KEY-----



Following the next line in the documentation:
*the **tinc join**command on the client will automatically separate
statements based on whether they should be in **tinc.conf** or in a host
config file*

We wanted to add “TunnelServer = yes” to the invitation hoping Tinc would
know to put it into the tinc.conf file.



But thinc told us it did not understand the parameter.



Do we do something wrong, or are not all “experimental” features supported
in the invitation files?



Many thanks,

Wouter Verstraeten
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20181010/4696f9f3/attachment.html>

On Wed, Oct 10, 2018 at 01:55:28PM +0200, Wouter Verstraeten wrote:
> We are trying the Tinc invites to let nodes join the network.
> 
> This is working as described but we want to push some configuration for
> some nodes but this seemed not to be working.
[...]
> We wanted to add “TunnelServer = yes” to the invitation hoping Tinc would
> know to put it into the tinc.conf file.
> 
> But thinc told us it did not understand the parameter.
> 
> Do we do something wrong, or are not all “experimental” features supported
> in the invitation files?
Actually, only a subset of the options are considered to be safe to be
used for invitation files. These are:

AutoConnect, Broadcast, BroadcastSubnet, ConnectTo, Mode, Subnet and
Weight.

Many options don't make sense to push in an invitation, but the list
could perhaps by extended by some options, such as TunnelServer,
StrictSubnets, and some others. I've also had a request to support the
--force option for joins, to allow any statement to be pushed in an
invitation. I'll add these things and update the documentation in the
next release.

-- 
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: 833 bytes
Desc: not available
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20181011/15eaea40/attachment.sig>