http://bugzilla.suse.com/show_bug.cgi?id=933092 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@opensuse.org, | |jengelh@inai.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=933092 Pawel Wieczorkiewicz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com, | |pwieczorkiewicz@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=933092 Jan Engelhardt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bnc-team-gnome@forge.provo. | |novell.com, | |wicked-maintainers@suse.de --- Comment #3 from Jan Engelhardt ---

This is the way wicked and NetworkManager work too. Otherwise it is unknown which service handles the network.

The upstream NetworkManager package does not have that Alias, it is instead a SUSE-specific patch that adds said Alias= line. wicked is a SUSE-produced (open)SUSE-specific (only used there) software, as well.

The systemd-networkd.service file must contain an alias to network.service.

I do not think it does, and I do not think NM or wicked should, either. Networking does not have to consist of a single service. A service which wants networking should Wants=network.target (or network-online.target). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=933092 --- Comment #5 from Marius Tomaschewski --- We would also need something like "Conficts" with other providers of network.service (something like Conflicts=network.service each service aliasing it -- preferably without a need to hardcode the other service names in each of them). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=933092 --- Comment #7 from Pawel Wieczorkiewicz --- (In reply to Marius Tomaschewski from comment #5)

We would also need something like "Conficts" with other providers of network.service (something like Conflicts=network.service each service aliasing it -- preferably without a need to hardcode the other service names in each of them).

I tested adding 'Conflicts=network.service' to wicked.service and NetworkManager.service (and also systemd-networkd.service when present) and then start/stop/restart and switching between those two services on latest TW and 13.2. It allows to start one service what automatically stops a conflicting service and vice versa. However after short playing with enable/disable the services I got systemd to crash: Jun 03 15:55:40 c159 dhclient[1640]: Received signal 15, initiating shutdown. Jun 03 15:55:40 c159 NetworkManager[1489]: Received signal 15, initiating shutdown. Jun 03 15:55:40 c159 NetworkManager[1489]: <info> (ens3): canceled DHCP transaction, DHCP client pid 1640 Jun 03 15:55:41 c159 NetworkManager[1489]: <info> startup complete Jun 03 15:56:40 c159 kernel: systemd[1]: segfault at 7f3c9cec7760 ip 00007f3c9cec7760 sp 00007ffc8f405b08 error 15 Jun 03 15:57:07 c159 dbus[537]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out So it seems it's not an option. Shall we maintain the Conflicts= as a list of well known (and default?) tools like wicked, NetworkManager, systemd-networkd, ... ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=933092 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.suse.com/sh | |ow_bug.cgi?id=984444 -- You are receiving this mail because: You are on the CC list for the bug.