-
Notifications
You must be signed in to change notification settings - Fork 105
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
[Feature Request] Support ntp-server option (or arbitrary options?) #109
Comments
For DHCPv4, considering that most options share the same 4 or 5 different layouts (int, ip, ip list, strings, routes, ...) and we basically have support in the library already, a generic "arbitrary option" plugin would certainly be a good idea and save us some pain. In the meantime, we'd of course accept a plugin for setting the ntp servers that is just a basic copy-paste of DNS. And we'll remove it when we make a generic option plugin for most of the known option layouts. Or we'll keep it since it's also nicer to use than having to specify option codes and types by hand For DHCPv6 however, most option types have their own custom layout so it wouldn't be as easy. |
What @Natolumin said, plus the fact that we should revisit the configuration syntax as discussed in another issue, which may make it easier to implement "generic" options at least for v4 |
I'm also interested in this. My plan was to migrate to |
The current design seems like it necessitates a plugin for every potential DHCP option, which is interesting but ultimately inflexible.
My near-term need is to pass
ntp-server
to my DHCP clients, and it looks like the easiest path would be to take thedns
plugin and make anntp
version of it, since both are trivial options providing IP addresses.This RFE is intended to capture the lack of
ntp-server
option support, and raise the idea that a genericoption name/number
+arguments
plugin would greatly extend the usability of CoreDHCP.The text was updated successfully, but these errors were encountered: