DHCP client behavior

Patrick Williams patrick at stwcx.xyz
Thu Mar 9 15:33:57 AEDT 2017


I'm looking for feedback from any networking experts.  We had an issue
reported by Witherspoon system manufacturing that our DHCP client was
not sending MAC addresses as part of the DHCP request as legacy systems
did.  I tracked this down to newer behavior in DHCP clients called
'DUID's, which are intended to be system-specific rather than
interface-specific identifiers (MACs would be interface-specific).

There are three options for IPv4 DHCP clients and two for IPv6:
    * MAC address based client IDs (legacy behavior, IPv4 only).
    * System UUID based DUIDs (single ID per system).
    * IPv6 'link-layer' based DUIDs (single ID per interface?)

I'm curious if anyone has a perspective on how data-centers would like
a BMC to act based on the three options for IPv4.  IPv6 we will need to
decide between system or interface based IDs.  (ie. what should be our
default configuration; individual vendors can always change.)

I have created an issue on Github to track the long-term decision and
as a temporary solution I forced IPv4 to MAC.

Original issue is at [1], follow up for this assessment is at [2], "fix"
in Gerrit is at [3].

[1] https://github.com/openbmc/openbmc/issues/1272
[2] https://github.com/openbmc/openbmc/issues/1280
[3] https://gerrit.openbmc-project.xyz/#/c/2933/

Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170308/a99c5e5d/attachment.sig>

More information about the openbmc mailing list