Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check non-inclusive DHCP overrides #305

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

pajod
Copy link

@pajod pajod commented Dec 27, 2022

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.:

UseMTU=yes may causes interface reset for some hardware (e.g. Intel NIC) and infinite loop
-- Originally posted by @yuwata in systemd/systemd#23484 (comment)

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

find [DHCP] in netplan/src/networkd.c
compare systemd/src/network/networkd-network-gperf.gperf
also see systemd.network(5)
no change in generated configuration intended
@slyon slyon self-requested a review January 3, 2023 11:56
@slyon slyon added the community This PR has been proposed by somebody outside of the Netplan team and roadmap commitments. label Aug 16, 2023
@pajod pajod marked this pull request as draft December 5, 2023 10:17
@slyon slyon added question Further information is requested needswork Change looks good but requires a bit more work labels Sep 4, 2024
Copy link
Collaborator

@slyon slyon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for your contribution to Netplan. And my apologies, this PR fell through the cracks!

I see this PR is still pretty much in "Draft" state (as indicated) with plenty of commented lines and "FIXMEs" inside.

Your PR description sounds like a bug report to me, would you mind creating an official bug report on https://bugs.launchpad.net/netplan/+filebug Describing the new functionality available in networkd today and how it breaks Netplan's current behaviour?

@pajod
Copy link
Author

pajod commented Sep 4, 2024

@slyon (edit: incorrect ping) I had given up on a proper fix because systemd changed that code a few times and there was no way one netplan version could serve all of them in a simple fashion. Maybe this needs to be fixed in a only-to-be-used-with-systemd-v250+ version and after requesting systemd to document as stable everything netplan uses.
Created a somewhat more bug-report-like structured report here still: https://bugs.launchpad.net/netplan/+bug/2078954

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community This PR has been proposed by somebody outside of the Netplan team and roadmap commitments. needswork Change looks good but requires a bit more work question Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants