netplan does not allow dhcp client identifier type to be specified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
High
|
Mathieu Trudel-Lapierre | ||
nplan (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Users of Ubuntu dealing with a DHCP server based on Windows Server, Solarwinds IPAM, or possibly other DHCP server products that do no support RFC 4361.
[Test case]
-- requires a Windows Server DHCP setup, or another product without support for client identifier DUIDs.
1) Configure a reservation for the device, using the device's MAC address.
2) Configure the device for DHCP:
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: yes
dhcp-
3) Run 'netplan apply'
4) Verify that 'netplan apply' completes successfully, and that the expected IP address is received as part of the reservation. It may be required to clear the DHCP server's cache of DHCP requests/responses.
[Regression potential]
These DHCP behavior changes may lead to systems not receiving the same IP as they previously did on reservations from a DHCP server; the default is not changing from using DUIDs so unchanged configurations should not be affected at all, but changes to add the new feature will likely change the IP address returned to the client from the DHCP server. Additionally, failure to parse netplan configuration or invalid DHCP behavior should be investigated as possible regressions coming from this SRU.
Changed in netplan: | |
status: | Triaged → In Progress |
importance: | Wishlist → High |
description: | updated |
description: | updated |
Triaging.
This is a feature that exists in networkd, but it doesn't look to exist for NetworkManager. It doesn't mean that it is then something we won't implement, but it raises the question of how useful it will be to people in general.
Maybe it would be just as good to simply default to using DUID for the DHCPv4 client identifier, and that seems to be the default in networkd anyway.
What option do you actually need there? Is this that using DUID for DHCPv4 breaking with whatever DHCP server you are using?