Need to add support for structured options
name: Support for dhcp structured options
about: Dealing with eg. MAP-T configuration options by generating several environment variablesSome initial questions
- Are you sure your feature is not already implemented in the latest ISC DHCP version? It was not last time I had a look.
- Are you sure your feature is not already implemented in the latest Kea version? Perhaps it's a good time to consider migration?
- Are you sure what you would like to do is not possible using some other mechanisms?
- Have you discussed your idea on dhcp-users or dhcp-workers mailing lists?
Is your feature request related to a problem? Please describe. I'm trying to use dhcp to configure a MAP-T CE. This involves the DHCPv6 options as described in the RFC 7498. The idea is to then push the options as environment variables useable in shell scripts called upon lease recepit. If we take the S46 rule (option 89) as an example and use the S46RULE prefix, one could expect the following environment variables generated : S46RULE_FLAG S46RULE_EALEN S46RULE_IPV4PREFIX (network notation eg. 192.168.1.0/24) S46RULE_IPV6PREFIX S46RULE_OPTIONS (the latter giving rise to deeper structures).
This is actually what udhcpc already does (probable contribution from OpenWRT).
Describe the solution you'd like Upon receipt of an option, an environmen,t variable gets filled when a text representation is relevant. For structured options, the idea is to mimic the structure with the generation of autrtomatic environment variable using a "_" (underscore) syntax.
Describe alternatives you've considered The project I'm on would not be easy to migrate to other dhcp clients.
Additional context See RFC 7498
Funding its development I could implement the feature.
Participating in development I could implement the feature. Of course complying to the architecture team's directives.
Contacting you E-mail, github woiuld be relevant.