RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2169869 - NetworkManager does not show actual DHCP settings for dhcp-client-id, dhcp-duid, dhcp-iaid
Summary: NetworkManager does not show actual DHCP settings for dhcp-client-id, dhcp-du...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.2
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: David Jaša
URL:
Whiteboard:
Depends On: 2152601 2167812
Blocks: 2171827 2171832
TreeView+ depends on / blocked
 
Reported: 2023-02-14 21:26 UTC by Thomas Haller
Modified: 2023-05-09 10:24 UTC (History)
12 users (show)

Fixed In Version: NetworkManager-1.42.2-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2152601
: 2171827 (view as bug list)
Environment:
Last Closed: 2023-05-09 08:17:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-305 0 None None None 2023-02-16 11:23:21 UTC
Red Hat Issue Tracker RHELPLAN-148665 0 None None None 2023-02-14 21:30:03 UTC
Red Hat Product Errata RHBA-2023:2485 0 None None None 2023-05-09 08:18:33 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1334 0 None opened bond: add scenarios for DHCP IDs presence in DBUS and /run 2023-02-27 11:14:17 UTC

Description Thomas Haller 2023-02-14 21:26:59 UTC 
+++ This bug was initially created as a clone of Bug #2152601 +++

NetworkManager allows configuring ipv4.dhcp-client-id, ipv6.dhcp-duid and ipv6.dhcp-iaid.

The properties support explicitly selecting the value (as hex-string or number). But they also support special keyworks, like "mac" or "per-mac" (check `man nm-settings`). This indicates to generate the values based on the chosen method. Note that if the properties are left unspecified, then a global default from NetworkManager.conf is consulted.

This means, when the profile does not explicitly select the used value (by either using one of the special keywords, or by allowing fallback to the global default), it's not immediately clear which value is used at time of activation

when the profile/device activates, the effectively used value gets generated (it sticks until a `nmcli device reapply` or the device goes down).

It is interesting to know, the actually used value.


We should expose the actually used value in the lease information. That is, both on D-Bus API, via `nmcli -f all device show $IFNAME` and in `/run/NetworkManager/devices/$IFINDEX`.


They keys are called:
 - dhcp4.dhcp_client_identifier
 - dhcp6.dhcp6_client_id
 - dhcp6.iaid


- for the dhclient plugin, those keys were already in the lease information, because with the dhclient plugin we get it via the environment variables of the hook script, and they were already there.

- for the internal plugin, they were not present. This was a missing feature (or regression compared to dhclient, if you want to call it like that).


Since commit [1], "dhcp4.dhcp_client_identifier" and "dhcp6.dhcp6_client_id" was fixed for the internal plugin. That is in upstream 1.41.8+ (rhel-9.2) and 1.40.10 (rhel-8.8).

[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/831b8f8e7e7c2660570bf36e3987f68047d1a91b

To support expose "dhcp6.iaid" (for the internal plugin), this is currently in progress at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1534


---

Optimally, we would have test that check this for the internal and the dhclient plugin. That seems cumbersome, because we don't have a convenient way to test both plugins (bug 2091891) and as dhclient is on the way out, maybe not worth it...
Comment 1 Thomas Haller 2023-02-21 08:53:27 UTC 
fixed upstream:

main:    https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/afbbfebfdbbccff6f01a30daf2626dd512758a4d
nm-1-42: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/422f086a680aa111ba1556d7e9ca70cf4fc4c34f
nm-1-40: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/b681bcec1d953c42c955faefd847afefe1b989f1
Comment 4 David Jaša 2023-02-27 11:14:17 UTC 
VERIFIED in NetworkManager-1.42.2-1.el9.x86_64, dhcp-client-identifier, dhcp6-client-id (as well as iaid) are exposed.

Tested by NM CI scenarios:
bond_expose_dhcp_client_identifier
bond_expose_dhcp6_client_id
bond_expose_iaid
Comment 6 errata-xmlrpc 2023-05-09 08:17:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2485
Note You need to log in before you can comment on or make changes to this bug.