https://bugzilla.novell.com/show_bug.cgi?id=821879 https://bugzilla.novell.com/show_bug.cgi?id=821879#c30 --- Comment #30 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-06-06 15:24:15 CEST --- (In reply to comment #28)
For IPv6 it is ON by default and when there is a dup detected on the link local address, IPv6 is basically not usable on this interface (multicasts, ... also a dhcpv6 client which requires it will fail). Further, there is no check which address fails or if other services are using (binding it) or not. Either everything worked or not. As the failure happens on a mandatory interface, rcnetwork fails.
You can a) disable dad via ifsysctl file, b) disable IPv6 (per interface).
IPv6 dad is no more failing, as I workarounded this on the openstack side. So rcnetwork status always shows as green, but the udev bug can still occur. Also eth0 is set to DHCP4 so no dhcpv6 client should run.
(In reply to comment #25)
2. if there is a duplicate MAC address - shouldn't it then also refuse to do IPv4 networking? I guess our duplicate address detection code is less picky there. (admitted: IPv4 does more things in userspace than IPv6)
For IPv4 there is no duplicate address detection done by default for static IPs (see CHECK_DUPLICATE_IP & SEND_GRATUITOUS_ARP variables in network/config), but dhcpcd makes it (should be the "checking .. is available on attached networks" msg).
Does dhcpcd react to receiving its own gratuitous ARP packet? How? What is the difference in meaning of "active (running)" and "active (exited)" systemd/network states? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.