Page MenuHomePhabricator

Add support for global-parameters, shared-network-parameters, subnet-parameters and static-mapping-parameters in dhcpv6-server as already implemented in (v4) dhcp-server
In progress, Requires assessmentPublicFEATURE REQUEST

Description

As mentioned in the title:
service dhcpv6-server shared-network-name [name] subnet [subnet] static-mapping [mapping-name] static-mapping-parameters
This would be very useful for e.g. setting custom client DNS options, etc.

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close

Event Timeline

jjakob created this task.Jun 12 2019, 1:58 PM
pasik added a subscriber: pasik.Jun 13 2019, 7:42 PM
jjakob claimed this task.Jun 16 2019, 5:55 PM
jjakob changed the task status from Open to In progress.
jjakob renamed this task from Add support for static-mapping-parameters in dhcpv6-server as it's already implemented in (v4) dhcp-server to Add support for global-parameters, shared-network-parameters, subnet-parameters and static-mapping-parameters in dhcpv6-server as already implemented in (v4) dhcp-server.Jun 16 2019, 5:57 PM

Looking at the dhcp_server.py for reference, I see the *-parameters were considered to be deprecated:

# HACKS AND TRICKS
#
# check for 'raw' ISC DHCP parameters configured by users
# actually this is a bad idea in general to pass raw parameters
# from any user
#
# deprecate this and issue a warning like we do for DNS forwarding?
if conf.exists('shared-network-parameters'):
    config['network_parameters'] = conf.return_values('shared-network-parameters')

Now I'm not sure whether this would be a welcome addition to dhcpv6 server.
My particular use-case that I considered this for is assigning per-static-mapping DNS server config (manually migrating clients enrolled into a IPA domain means I have to have some clients pointed to old DNS servers and some to new, currently I get by with setting static v6 addresses on the clients)