[Bug 1713226] [NEW] systemd-networkd messes up networking

[msaxl]

Public bug reported:

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

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: artful

-- 
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 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/systemd/+bug/1713226/+subscriptions