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: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 Ubuntu
Touch seeded packages, which is subscribed to systemd 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
