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

[Lukas Märdian]

Netplan generates configuration snippets to make sure an interface is
only handled by the backend renderer (networking-daemon: sd-networkd or
NetworkManager) that is instructed to control that interface nowadays.
This logic has been improved recently:
https://github.com/canonical/netplan/pull/276

Please re-open if this is still an issue.

** Changed in: nplan (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nplan (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ifupdown (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[msaxl]

The example 2 in my first posting is not an bug since the package
contains /lib/systemd/network/80-container-host0.network. As I wrote
this only affects systemd-nspawn containers

the unexpected "thing" is that when you upgrade you do not expect a
system wide configuration that is active in parallel to the "old"
ifupdown configuration. To keep your old configuration someone can for
example touch /etc/systemd/network/80-container-host0.network

I have no idea how to deal with that "problem", but I think that not
many have such configurations and less do a container upgrade instead of
a clean update. With luck the rest will be directed here by google ;)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  New
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/ifupdown/+bug/1713226/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[msaxl]

Here are the files of the networkmanager systemd-networkd conflict (I
already removed ifupdown, the problem is the same, so we say for sure
networkmanager or systemd-networkd causes the problem)

the output of ip a is the following:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth1:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 00:1d:7d:c3:a3:a1 brd ff:ff:ff:ff:ff:ff
inet6 fd12:2017:8387:0:8d6:b5ff:bf63:6389/64 scope global mngtmpaddr 
noprefixroute dynamic 
   valid_lft 86396sec preferred_lft 14396sec
inet6 fd12:2017:8387:0:21d:7dff:fec3:a3a1/64 scope global mngtmpaddr 
noprefixroute dynamic 
   valid_lft 86304sec preferred_lft 14304sec
inet6 fe80::21d:7dff:fec3:a3a1/64 scope link

   
   valid_lft forever preferred_lft forever

the profile that should come up has addr-gen-mode=stable-privacy, so
somehow it adds another ipv6 address, but it totally ignores ipv4...

** Attachment added: "files.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713226/+attachment/4941430/+files/files.tar.xz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  New
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/ifupdown/+bug/1713226/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

also, we got new network-manager in artful which may have regressed.

** Also affects: ifupdown (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  New
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/ifupdown/+bug/1713226/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

@msaxl

for both examples, can you please attach the existing configs for
ifupdown, network-manager, and networkd? As in the contents of
/etc/network/interfaces /etc/NetworkManager and output of udevadm info
on the interface and contents of /etc/systemd/network?

I want to reproduce these bugs and verify what the current behaviour is
both for upgrade and clean-install cases, and figure out all the bugs /
inconsistencies present to fix any upgrade/clean-install issues.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  New
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/ifupdown/+bug/1713226/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

Steve,

It seems that unconditional enablement and start of networkd in
src:systemd.postinst has side-effects, especially when netwokr-manager
is directly managing desktop systems, without netplan.

I think we should not unconditially enable and start entworkd in
src:systemd.postinst, and instead have networkd enable baked into cloud-
images and/or done by netcfg or the netplan generator on boot.

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager 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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [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 Desktop
Packages, which is subscribed to network-manager 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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

Is this on upgrades to artful? or clean-install / clean-bring up of
artful?

Note that artful will no longer have ifupdown installed on clean-install, and 
thus /etc/network/interfaces changes for clean-installs will have no effect at 
all. And one should instead use netplan e.g. $ sudo netplan ifupdown-migrate
to move the system over to networkd.

The router advertisement vs networkmanager is interesting case. In
practice networkd should not have configured the interface imho, if it
was not told to manage it via netplan configuration. Or e.g.
NetworkManager should still consider interface for management, even if
it has acquired RA ipv6.

** Also affects: nplan (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager 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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp