Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
.The `nmstate` API now supports IPv6 link-local addresses as DNS servers
With this enhancement, you can use the `nmstate` API to set IPv6 link-local addresses as DNS servers. Use the `<link-local_address>%<interface>` format, for example:
----
dns-resolver:
config:
server:
- fe80::deef:1%enp1s0
----
DescriptionQuique Llorente
2022-06-09 09:56:55 UTC
Description of problem:
At some scenarios one of the nameserver entries at the resolv.conf can contain a suffix where the interface name is appended with an porcentage symbol "%".
cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.66.2
nameserver fd00::1
nameserver fe80::e880:55ff:fe96:6424%eth0
The nmcli view of this is
[vagrant@node01 ~]$ nmcli c show eth0 |grep DNS
IP4.DNS[1]: 192.168.66.2
IP6.DNS[1]: fd00::1
IP6.DNS[2]: fe80::e880:55ff:fe96:6424
This nameserver is being received by dhcp6
Jun 09 09:44:11 node01 NetworkManager[4947]: <info> [1654767851.3536] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jun 09 09:44:11 node01 NetworkManager[4947]: <info> [1654767851.3547] dhcp6 (eth0): dhclient started with pid 5000
Jun 09 09:44:11 node01 NetworkManager[4947]: <info> [1654767851.3552] policy: set 'eth0' (eth0) as default for IPv6 routing and DNS
Jun 09 09:44:11 node01 dhclient[5000]: XMT: Confirm on eth0, interval 1080ms.
Jun 09 09:44:11 node01 dhclient[5000]: RCV: Reply message on eth0 from fe80::e880:55ff:fe96:6424.
Jun 09 09:44:11 node01 dhclient[5000]: message status code Success: "all addresses still on link"
When trying to apply this dns-resolver configuration with nmstate:
dns-resolver:
config:
server:
- 192.168.66.2
- fd00::1
- fe80::e880:55ff:fe96:6424%eth0
We get the following error
libnmstate.error.NmstateValueError
Invalid IP address
'fe80::e880:55ff:fe96:6424%eth0' does not appear to be an IPv4 or IPv6 address
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. nmstatectl apply
dns-resolver:
config:
server:
- 192.168.66.2
- fd00::1
- fe80::e880:55ff:fe96:6424%eth0
Actual results:
libnmstate.error.NmstateValueError
Invalid IP address
'fe80::e880:55ff:fe96:6424%eth0' does not appear to be an IPv4 or IPv6 address
Expected results:
Nmstate is able to configure this special case of nameserver
Additional info:
We have found this at kubevirtci clusters and it's generated from NetworkManager but I don't find any reference for this syntax.
When IPv6 link local address is used as DNS resolve server, the interface name should be defined in the format of`<ipv6-link-local-address>%<interface_name>`.
Reporter agreed to targeting this bug in 9.2.
The acceptance criteria is allowing user to use IPv6 link local address as DNS resolver(e.g. fe80::e880:55ff:fe96:6424%eth0).
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 (nmstate 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:2190
Description of problem: At some scenarios one of the nameserver entries at the resolv.conf can contain a suffix where the interface name is appended with an porcentage symbol "%". cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.66.2 nameserver fd00::1 nameserver fe80::e880:55ff:fe96:6424%eth0 The nmcli view of this is [vagrant@node01 ~]$ nmcli c show eth0 |grep DNS IP4.DNS[1]: 192.168.66.2 IP6.DNS[1]: fd00::1 IP6.DNS[2]: fe80::e880:55ff:fe96:6424 This nameserver is being received by dhcp6 Jun 09 09:44:11 node01 NetworkManager[4947]: <info> [1654767851.3536] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds) Jun 09 09:44:11 node01 NetworkManager[4947]: <info> [1654767851.3547] dhcp6 (eth0): dhclient started with pid 5000 Jun 09 09:44:11 node01 NetworkManager[4947]: <info> [1654767851.3552] policy: set 'eth0' (eth0) as default for IPv6 routing and DNS Jun 09 09:44:11 node01 dhclient[5000]: XMT: Confirm on eth0, interval 1080ms. Jun 09 09:44:11 node01 dhclient[5000]: RCV: Reply message on eth0 from fe80::e880:55ff:fe96:6424. Jun 09 09:44:11 node01 dhclient[5000]: message status code Success: "all addresses still on link" When trying to apply this dns-resolver configuration with nmstate: dns-resolver: config: server: - 192.168.66.2 - fd00::1 - fe80::e880:55ff:fe96:6424%eth0 We get the following error libnmstate.error.NmstateValueError Invalid IP address 'fe80::e880:55ff:fe96:6424%eth0' does not appear to be an IPv4 or IPv6 address Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. nmstatectl apply dns-resolver: config: server: - 192.168.66.2 - fd00::1 - fe80::e880:55ff:fe96:6424%eth0 Actual results: libnmstate.error.NmstateValueError Invalid IP address 'fe80::e880:55ff:fe96:6424%eth0' does not appear to be an IPv4 or IPv6 address Expected results: Nmstate is able to configure this special case of nameserver Additional info: We have found this at kubevirtci clusters and it's generated from NetworkManager but I don't find any reference for this syntax.