Skip to content

Ensure we use a stable DUID for DHCPv6 exchanges#267

Draft
bnaecker wants to merge 1 commit intomainfrom
ben/consistent-dhcpv6-duids
Draft

Ensure we use a stable DUID for DHCPv6 exchanges#267
bnaecker wants to merge 1 commit intomainfrom
ben/consistent-dhcpv6-duids

Conversation

@bnaecker
Copy link
Copy Markdown
Contributor

@bnaecker bnaecker commented May 8, 2026

  • Package ndpd.conf in the switch zone with defaults that preclude DHCPv6 on any interface.
  • After fetching the correct, stable MAC addresses from the switch SP, dpd now uses the base MAC to write out a DUID to a file where illumos's dhpcagent can pick it up and use it later in exchanges.
  • For the VLANs representing the techports, tfportd now creates both a link-local address and allows DHCPv6 to run on the interface as well. This should trigger dhcpagent, which would pick up the stable DUID from the previous item.
  • Some misc cleanup, logging improvements, IdOrdMap over BTreeMap

@bnaecker bnaecker marked this pull request as draft May 8, 2026 18:10
- Package `ndpd.conf` in the switch zone with defaults that preclude
  DHCPv6 on any interface.
- After fetching the correct, stable MAC addresses from the switch SP,
  `dpd` now uses the base MAC to write out a DUID to a file where
  illumos's `dhpcagent` can pick it up and use it later in exchanges.
- For the VLANs representing the techports, `tfportd` now creates both
  a link-local address and allows DHCPv6 to run on the interface as
  well. This should trigger `dhcpagent`, which would pick up the stable
  DUID from the previous item.
- Some misc cleanup, logging improvements, `IdOrdMap` over `BTreeMap`
@bnaecker bnaecker force-pushed the ben/consistent-dhcpv6-duids branch from 658e37b to 5bece81 Compare May 8, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant