Mailinglist Archive: opensuse-bugs (2746 mails)

< Previous Next >
[Bug 821879] udev update breaks network

--- Comment #32 from Marius Tomaschewski <mt@xxxxxxxx> 2013-06-07 04:32:19 UTC
(In reply to comment #30)
(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.

Only when some error occurs and duplicate addresses are definitely errors.
The status isn't checked per address, but per interface and rcnetwork
reports failure when there is an error on mandatory interfaces.
You can use STARTMODE=hotplug or ifplugd for all "nice to have" interfaces.

Also eth0 is set to DHCP4 so no dhcpv6 client should run.

When BOOTPROTO=dhcp4 is set, dhcp6 will be not started/used, but this does
not mean IPv6 is disabled -- it is enabled by default (static and autoconf).
You can disable a) DAD or b) IPv6 at all via ifsysctl or set IPV6_DAD_WAIT="0"
to disable it the check (each one per-interface or globally).

(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
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?

I don't know/remember what it exactly does here.

What is the difference in meaning of "active (running)" and "active (exited)"
systemd/network states?

/etc/init.d/network is using "X-Systemd-RemainAfterExit: true" LSB tag:
Takes a boolean value that specifies whether the service shall be
considered active even when all its processes exited. Defaults to no.

"active (exited)" means the network.service cgroup is empty. You'll see
this in static configurations (systemctl status network.service).
"active (running)" means, there is some process in the cgroup, that is
in e.g. dhcp mode where dhcp client is running.

Are you using dhcp and get "active (exited)"? Did the dhcpcd die?

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >