[Bug 1713226] Re: systemd-networkd messes up networking

[msaxl]

this was a upgrade so the ifupdown problem should not happen with clean installs.
How is the migration planned?

If for example one will do a upgrade from 16.04 to the next 18.04 such
problems are a clear show stopper since breaking the network for most
servers will mean needing physical access.

On my system there is nothing that puts the interface to state up, so I blame systemd-networkd being it (normal desktop system, so /etc/network/interfaces contains only a lo entry).
But after all I consider having two systems that configure the same set of network interfaces will never work reliable.
I think the best would be systemd-networkd.service conflicts network-manager.service

What is the pro of enabling systemd-networkd on desktop systems? I see
advantages on server systems over ifupdown, but afaik neither gnome nor
plasma has systemd-networkd integration.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router advertisement), networkmanager does not configure the network anymore so you get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice versa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713226/+subscriptions