Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tinc_host_configuration needs to be reconsidered #14

Open
hvisage opened this issue Oct 8, 2015 · 2 comments
Open

tinc_host_configuration needs to be reconsidered #14

hvisage opened this issue Oct 8, 2015 · 2 comments

Comments

@hvisage
Copy link

hvisage commented Oct 8, 2015

in router mode, there is a need for multiple subnet: lines. having tinc_host_configuration only a dictionary, makes only only Subnet: line "valid".

Yes, I've resorted to using capitalization to hack passed this problem (see below), but that's not clean and intuitive:

#There is a problem in the debops.tinc: subnet must be unique keys as it's a dict, not a list,
#so use capitilization to unique them...
tinc_host_configuration:
  subnet: '10.255.253.0/24'
  Subnet: '{{tinc_host_net_ip}}' 
@drybjed
Copy link
Member

drybjed commented Oct 8, 2015

Try this:

tinc_host_configuration:
  subnet: [ '10.255.253.0/24', '{{ tinc_host_net_ip }}' ]

@ypid
Copy link
Member

ypid commented Aug 27, 2016

@hvisage I don’t see an issue here either. Can you close this? Refer to: https://docs.ansible.com/ansible/YAMLSyntax.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants