https://bugzilla.novell.com/show_bug.cgi?id=821879 https://bugzilla.novell.com/show_bug.cgi?id=821879#c28 --- Comment #28 from Marius Tomaschewski <mt@suse.com> 2013-06-05 08:14:39 UTC --- (In reply to comment #27)
Created an attachment (id=542777) --> (http://bugzilla.novell.com/attachment.cgi?id=542777) [details] journal
it seems on boot there are two dhcpcd processes running at the same time
No, there are multiple stages: dhcpcd gets a lease and calls dhcpcd-hook with "up", "new", "down", "complete" [which results in "ifdown -o dhcp", "netconfig" and "ifup -o dhcp"]. Then it forks. Basically the problem is, that when /etc/init.d/network reports !0 to systemd, systemd will stop it again and not start services requiring it. When it does not report failure on error conditions, other services will fail. 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). (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). -- 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.