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.
Created attachment 1346004[details]
Network management log file
Description of problem:
If a duplicate IPv4 address is detected it also prevents the IPv6 address from being set up
Version-Release number of selected component (if applicable):
NetworkManager-1.8.0-9.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create an environment with a duplicate IPv4 address and a unique IPv6 address
# cat /etc/sysconfig/network-scripts/ifcfg-ens3
NM_CONTROLLED=yes
TYPE=Ethernet
NAME=ens3
DEVICE=ens3
ONBOOT=yes
BOOTPROTO=none
PROXY_METHOD=none
BROWSER_ONLY=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
DNS1=192.168.1.1
# IPADDR=192.168.1.150
IPADDR=192.168.1.200
PREFIX=24
GATEWAY=192.168.1.1
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
UUID=21d47e65-8523-1a06-af22-6f121086f085
ARPING_WAIT=1
2. set ipv4.dad-timeout such that the duplicate IPv4 address will be detected
# nmcli con mod ens3 ipv4.dad-timeout 2001
3. reboot
Actual results:
# ip a l ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:8a:8b:6d brd ff:ff:ff:ff:ff:ff
Expected results:
# ip a l ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:8a:8b:6d brd ff:ff:ff:ff:ff:ff
inet6 2600:8800:78e:2000::8/128 scope global dynamic
valid_lft 3492sec preferred_lft 1692sec
inet6 2600:8800:78e:2000:5054:ff:fe8a:8b6d/64 scope global noprefixroute dynamic
valid_lft 86392sec preferred_lft 86392sec
inet6 fe80::5054:ff:fe8a:8b6d/64 scope link
valid_lft forever preferred_lft forever
Additional info:
Comment 2Beniamino Galvani
2017-11-02 13:33:55 UTC
Created attachment 1347023[details]
[PATCH 1/2] device: don't necessarily fail the connection when ipv4 DAD fails
Comment 3Beniamino Galvani
2017-11-02 13:34:17 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, 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-2018:0778
Created attachment 1346004 [details] Network management log file Description of problem: If a duplicate IPv4 address is detected it also prevents the IPv6 address from being set up Version-Release number of selected component (if applicable): NetworkManager-1.8.0-9.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create an environment with a duplicate IPv4 address and a unique IPv6 address # cat /etc/sysconfig/network-scripts/ifcfg-ens3 NM_CONTROLLED=yes TYPE=Ethernet NAME=ens3 DEVICE=ens3 ONBOOT=yes BOOTPROTO=none PROXY_METHOD=none BROWSER_ONLY=no DEFROUTE=yes IPV4_FAILURE_FATAL=no DNS1=192.168.1.1 # IPADDR=192.168.1.150 IPADDR=192.168.1.200 PREFIX=24 GATEWAY=192.168.1.1 IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no UUID=21d47e65-8523-1a06-af22-6f121086f085 ARPING_WAIT=1 2. set ipv4.dad-timeout such that the duplicate IPv4 address will be detected # nmcli con mod ens3 ipv4.dad-timeout 2001 3. reboot Actual results: # ip a l ens3 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:8a:8b:6d brd ff:ff:ff:ff:ff:ff Expected results: # ip a l ens3 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:8a:8b:6d brd ff:ff:ff:ff:ff:ff inet6 2600:8800:78e:2000::8/128 scope global dynamic valid_lft 3492sec preferred_lft 1692sec inet6 2600:8800:78e:2000:5054:ff:fe8a:8b6d/64 scope global noprefixroute dynamic valid_lft 86392sec preferred_lft 86392sec inet6 fe80::5054:ff:fe8a:8b6d/64 scope link valid_lft forever preferred_lft forever Additional info: