Clarification on os-isc-dhcp plugin for 26.1

[vk2him]

Sorry if the following are obvious questions, hopefully someone can clarify please.

• I'm using native ISC DHCP on 25.7.11_2 and don't intend to migrate (yet) to the alternatives.
  I see the release notes for 26.1 says "ISC-DHCP moves to a plugin. It will be automatically installed during upgrades."
  
  Does this mean the existing ISC-DHCP configurations for IPv4 and IPv6 will be "imported" into the plugin, so I won't need to do any configuration changes?
  
  
• Regarding the release note comment which seems a bit ambiguous:
  
  "To accommodate the change away from ISC-DCHP defaults the "Track interface" IPv6 mode now has a sibling called "Identity Association" which does the same except it is not automatically starting ISC-DHCPv6 and Radvd router advertisements to allow better interoperability with Kea and Dnsmasq setups."
  
  As I'm remaining on ISC-DHCP, will I need to make any changes to "Track interface" as I'll need ISC-DHCPv6 and Radvd to autostart.
  
  

Many thanks

[Lumpy]

Does this mean the existing ISC-DHCP configurations for IPv4 and IPv6 will be "imported" into the plugin, so I won't need to do any configuration changes?

Yes, exactly.

As I'm remaining on ISC-DHCP, will I need to make any changes to "Track interface" as I'll need ISC-DHCPv6 and Radvd to autostart.

As I understand it, you don't need to change anything manually. The "Track Interface" option is still there (marked as "legacy" thoguh), and works as expected.

[franco]

> Yes, exactly.

It's important to know that all configuration exists within config.xml and a component moving to plugins simply keeps reading the same information.

> As I understand it, you don't need to change anything manually. The "Track Interface" option is still there (marked as "legacy" thoguh), and works as expected.

There may be use cases where you want "Identity association" with ISC-DHCP.  This is analogous to using the " Allow manual adjustment of DHCPv6 and Router Advertisements" option in "Track interface". At some point both IPv6 modes may start to drift feature-wise, but at the moment that's not the case either.

Specifically the problem with "Track interface" was just that it was closely tied to ISC-DHCPv6/Radvd auto-configuration which is different now that we have Dnsmasq DHCPv6+RA and Kea DHCPv6+Radvd as viable options we don't want to also manage automatically anymore. Even Dnsmasq DHCPv6+Radvd can be a viable option.


Cheers,
Franco

[vk2him]

Thanks guys for clarifying