Check non-inclusive DHCP overrides #305
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
networkd renamed section DHCP=>DHCPv4. Two options had been documented at the time, they include DHCPv6:
systemd/systemd@4f7331a - Not so most of the others. They need to move to DHCPv6 section.
Any guidelines on such breaking change?
This will cause trouble with incompletely applied (yet not generating warnings) configurations that, by chance, work now, e.g.:
It won't suffice to just teach
combine_dhcp_overrides()
that most options must and all options should go into separate sections. Admins must somehow be able to discover why their effective configuration changed.References:
man 5 systemd.network
https://github.com/canonical/netplan/tree/main/src/networkd.c
https://github.com/systemd/systemd/tree/main/src/network/networkd-network-gperf.gperf
DHCP.UseHostname => DHCPv4.UseHostname
systemd/systemd@1346b1f
systemd/systemd#13006
DHCPv6.UseFQDN => DHCPv6.UseHostname
systemd/systemd#18543
systemd/systemd#18668