-
Notifications
You must be signed in to change notification settings - Fork 9
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
No ability to set accept_ra nor allow-hotplug #9
Comments
I think that you are right. Can you open a pull request? |
I don't think I can make changes that are backward-compatible. The first problem, as far as I can see, is that currently
or
There is also another interface selection stanza,
AFAIU, it can be combined with another selection stanza for the same interface, so you can have these 2 non exclusive stanzas:
So really, this boolean should be dropped, and instead of having
Also, lots of other options keywords have been left out: accept_ra is one, but then there is privext, dhcp (as an option, not as a method to bring the interface up as in Now I am a complete beginner with ansible (I have never written a role nor a template). But IIUC, instead of listing all the possibilities explicitly, it would maybe be more productive to simplify the template device.j2 to something like:
I am ok to write a PR, but since this is potentially a lot of work for me, I want to make sure that you would be ok with my changes before I invest the time and energy. |
Hi,
As far as I can see, this role does not let me set the option accept_ra. In the case of ipv6, it would be nice if it let me.
Also, you can only declare an interface as 'auto', but not as 'allow-hotplug'. For non pci interfaces this would be useful.
Cheers,
Christophe-Marie
The text was updated successfully, but these errors were encountered: