Public bug reported:
Hi,
I have a home server running Ubuntu 20.04.
It is using KVM to run several VMs (router, Wi-Fi access point, NAS, ...).
Everything has been running fine for years now, very happy, very grateful for
all the work but...
On June 17th, on the hypervisor systemd upgraded from 245.4-4ubuntu3.6
to 245.4-4ubuntu3.7 and all the VMs lost network connectivity.
Packages that were upgraded on June 17th:
libnss-mymachines libnss-systemd libpam-systemd libsystemd0 libudev1
systemd systemd-container systemd-sysv systemd-timesyncd udev
Package installation log:
Log started: 2021-06-17 06:34:27
Preparing to unpack .../0-libnss-systemd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../1-systemd-timesyncd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd-timesyncd (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../2-systemd-sysv_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd-sysv (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../3-libnss-mymachines_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libnss-mymachines:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../4-systemd-container_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd-container (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../5-libpam-systemd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libpam-systemd:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../6-systemd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../7-libsystemd0_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libsystemd0:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.7) ...
Setting up systemd (245.4-4ubuntu3.7) ...
Setting up systemd-timesyncd (245.4-4ubuntu3.7) ...
Setting up systemd-container (245.4-4ubuntu3.7) ...
Setting up systemd-sysv (245.4-4ubuntu3.7) ...
Setting up libnss-systemd:amd64 (245.4-4ubuntu3.7) ...
Setting up libnss-mymachines:amd64 (245.4-4ubuntu3.7) ...
Setting up libpam-systemd:amd64 (245.4-4ubuntu3.7) ...
Processing triggers for libc-bin (2.31-0ubuntu9.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Log ended: 2021-06-17 06:34:34
Log started: 2021-06-17 06:34:35
Preparing to unpack .../udev_245.4-4ubuntu3.7_amd64.deb ...
Unpacking udev (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../libudev1_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libudev1:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Setting up libudev1:amd64 (245.4-4ubuntu3.7) ...
Setting up udev (245.4-4ubuntu3.7) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (245.4-4ubuntu3.7) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.3) ...
Processing triggers for initramfs-tools (0.136ubuntu6.5) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-74-generic
Log ended: 2021-06-17 06:35:03
I then tried to revert these packages.
apt-cache show libsystemd0
I find 2 versions, 245.4-4ubuntu3 & 245.4-4ubuntu3.7
Not sure why it is not 245.4-4ubuntu3.6 & 245.4-4ubuntu3.7 but anyway...
I reverted these packages to 245.4-4ubuntu3
sudo aptitude install libnss-systemd=245.4-4ubuntu3
systemd-timesyncd=245.4-4ubuntu3 systemd-sysv=245.4-4ubuntu3
libnss-mymachines=245.4-4ubuntu3 systemd-container=245.4-4ubuntu3
libpam-systemd=245.4-4ubuntu3 systemd=245.4-4ubuntu3 libsystemd0=245.4-4ubuntu3
sudo reboot
All the VMs have access to the network again.
My setup:
I have 2 NICs on the server:
- eno1 is my WAN plugged to my ISP's router and attached to the br-wan bridge
- enp2s0 is my LAN and is attached to the br-lan bridge
I use static addressing
The LAN is IPv4 and IPv6
The WAN is IPv4 only
wlx00c0caa5e44f is a USB Wi-Fi adapter attached to br-lan using hostapd
VMs use the classic vnet attachement
vi /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
# No DHCP and no addresses set for the ethernet NIC
eno1:
addresses: []
dhcp4: false
dhcp6: false
optional: true
enp2s0:
addresses: []
dhcp4: false
dhcp6: false
optional: true
# Prevent virtual networks and Wi-Fi NIC from acquiring link local IPv6
addresses (fe80::)
vnet:
match:
name: vnet*
link-local: [ ]
wlx00c0caa5e44f:
link-local: [ ]
bridges:
# Configure a static IPv4 address for br-wan
br-wan:
interfaces: [eno1]
addresses:
- 192.168.1.1/24
dhcp4: false
dhcp6: false
gateway4: 192.168.1.254
nameservers:
addresses:
- 9.9.9.9
search: []
# Isolate br-lan
br-lan:
interfaces: [enp2s0]
addresses: []
dhcp4: false
dhcp6: false
link-local: [ ]
optional: true
With this setup on systemd 245.4-4ubuntu3.6 the hypervisor and the VMs have
network access.
With the same setup on 245.4-4ubuntu3.7 the hypervisor has network access but
the VMs don't.
Workaround with systemd 245.4-4ubuntu3.7: allowing link-local on the
vnet interfaces
sudo vi /etc/netplan/01-netcfg.yaml
# vnet:
# match:
# name: vnet*
# link-local: [ ]
sudo netplan apply
sudo reboot
Now on systemd 245.4-4ubuntu3.7 the hypervisor and the VMs have network
access.
Thank you for your help
Tests performed with results:
On systemd 245.4-4ubuntu3 with no link-local addresses on the vnets
sudo aptitude install libnss-systemd=245.4-4ubuntu3 systemd-
timesyncd=245.4-4ubuntu3 systemd-sysv=245.4-4ubuntu3 libnss-
mymachines=245.4-4ubuntu3 systemd-container=245.4-4ubuntu3 libpam-
systemd=245.4-4ubuntu3 systemd=245.4-4ubuntu3 libsystemd0=245.4-4ubuntu3
sudo vi /etc/netplan/01-netcfg.yaml
vnet:
match:
name: vnet*
link-local: [ ]
sudo reboot
ip addr
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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master
br-lan state DOWN group default qlen 1000
link/ether 40:8d:5c:1d:92:b5 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UP group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
5: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-wan
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe1d:92b7/64 scope link
valid_lft forever preferred_lft forever
6: wlx00c0caa5e44f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
br-lan state UP group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-lan state UNKNOWN group default qlen 1000
link/ether fe:54:00:09:3f:92 brd ff:ff:ff:ff:ff:ff
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UNKNOWN group default qlen 1000
link/ether fe:54:00:98:c4:fe brd ff:ff:ff:ff:ff:ff
Results: OK. Hypervisor and VMs have network access
On systemd 245.4-4ubuntu3.7 with no link-local addresses on the vnets
sudo aptitude install libnss-systemd=245.4-4ubuntu3.7 systemd-
timesyncd=245.4-4ubuntu3.7 systemd-sysv=245.4-4ubuntu3.7 libnss-
mymachines=245.4-4ubuntu3.7 systemd-container=245.4-4ubuntu3.7 libpam-
systemd=245.4-4ubuntu3.7 systemd=245.4-4ubuntu3.7
libsystemd0=245.4-4ubuntu3.7
sudo vi /etc/netplan/01-netcfg.yaml
vnet:
match:
name: vnet*
link-local: [ ]
sudo reboot
ip addr
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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master
br-lan state DOWN group default qlen 1000
link/ether 40:8d:5c:1d:92:b5 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UP group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
5: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-wan
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe1d:92b7/64 scope link
valid_lft forever preferred_lft forever
6: wlx00c0caa5e44f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
br-lan state UP group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UNKNOWN group default qlen 1000
link/ether fe:54:00:09:3f:92 brd ff:ff:ff:ff:ff:ff
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UNKNOWN group default qlen 1000
link/ether fe:54:00:98:c4:fe brd ff:ff:ff:ff:ff:ff
Results: KO. Hypervisor has network access and the VMs don't
On systemd 245.4-4ubuntu3.7 with link-local addresses on the vnets
sudo aptitude install libnss-systemd=245.4-4ubuntu3.7 systemd-
timesyncd=245.4-4ubuntu3.7 systemd-sysv=245.4-4ubuntu3.7 libnss-
mymachines=245.4-4ubuntu3.7 systemd-container=245.4-4ubuntu3.7 libpam-
systemd=245.4-4ubuntu3.7 systemd=245.4-4ubuntu3.7
libsystemd0=245.4-4ubuntu3.7
sudo vi /etc/netplan/01-netcfg.yaml
# vnet:
# match:
# name: vnet*
# link-local: [ ]
sudo netplan apply
sudo reboot
ip addr
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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master
br-lan state DOWN group default qlen 1000
link/ether 40:8d:5c:1d:92:b5 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UP group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
5: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-wan
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe1d:92b7/64 scope link
valid_lft forever preferred_lft forever
6: wlx00c0caa5e44f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
br-lan state UP group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-lan state UNKNOWN group default qlen 1000
link/ether fe:54:00:09:3f:92 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe09:3f92/64 scope link
valid_lft forever preferred_lft forever
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UNKNOWN group default qlen 1000
link/ether fe:54:00:98:c4:fe brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe98:c4fe/64 scope link
valid_lft forever preferred_lft forever
Results: KO. Hypervisor and VMs have network access but with link-local
addresses on the vnet interfaces
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
Uname: Linux 5.4.0-74-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 19 15:44:06 2021
InstallationDate: Installed on 2020-04-25 (420 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
MachineType: Gigabyte Technology Co., Ltd. H97N-WIFI
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
TERM=xterm-256color
PATH=(custom, no user)
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic
root=UUID=a33535a5-f1fc-47b7-912f-548c5bef1b8e ro lockdown=confidentiality
slab_nomerge slub_debug=FZ mce=0 vsyscall=none
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97N-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H97N-WIFI
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
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/1933002
Title:
VMs lost network access after hypervisor upgraded to systemd
245.4-4ubuntu3.7
Status in systemd package in Ubuntu:
New
Bug description:
Hi,
I have a home server running Ubuntu 20.04.
It is using KVM to run several VMs (router, Wi-Fi access point, NAS, ...).
Everything has been running fine for years now, very happy, very grateful for
all the work but...
On June 17th, on the hypervisor systemd upgraded from 245.4-4ubuntu3.6
to 245.4-4ubuntu3.7 and all the VMs lost network connectivity.
Packages that were upgraded on June 17th:
libnss-mymachines libnss-systemd libpam-systemd libsystemd0 libudev1
systemd systemd-container systemd-sysv systemd-timesyncd udev
Package installation log:
Log started: 2021-06-17 06:34:27
Preparing to unpack .../0-libnss-systemd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../1-systemd-timesyncd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd-timesyncd (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../2-systemd-sysv_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd-sysv (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../3-libnss-mymachines_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libnss-mymachines:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6)
...
Preparing to unpack .../4-systemd-container_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd-container (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../5-libpam-systemd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libpam-systemd:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../6-systemd_245.4-4ubuntu3.7_amd64.deb ...
Unpacking systemd (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../7-libsystemd0_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libsystemd0:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.7) ...
Setting up systemd (245.4-4ubuntu3.7) ...
Setting up systemd-timesyncd (245.4-4ubuntu3.7) ...
Setting up systemd-container (245.4-4ubuntu3.7) ...
Setting up systemd-sysv (245.4-4ubuntu3.7) ...
Setting up libnss-systemd:amd64 (245.4-4ubuntu3.7) ...
Setting up libnss-mymachines:amd64 (245.4-4ubuntu3.7) ...
Setting up libpam-systemd:amd64 (245.4-4ubuntu3.7) ...
Processing triggers for libc-bin (2.31-0ubuntu9.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Log ended: 2021-06-17 06:34:34
Log started: 2021-06-17 06:34:35
Preparing to unpack .../udev_245.4-4ubuntu3.7_amd64.deb ...
Unpacking udev (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Preparing to unpack .../libudev1_245.4-4ubuntu3.7_amd64.deb ...
Unpacking libudev1:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ...
Setting up libudev1:amd64 (245.4-4ubuntu3.7) ...
Setting up udev (245.4-4ubuntu3.7) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (245.4-4ubuntu3.7) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.3) ...
Processing triggers for initramfs-tools (0.136ubuntu6.5) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-74-generic
Log ended: 2021-06-17 06:35:03
I then tried to revert these packages.
apt-cache show libsystemd0
I find 2 versions, 245.4-4ubuntu3 & 245.4-4ubuntu3.7
Not sure why it is not 245.4-4ubuntu3.6 & 245.4-4ubuntu3.7 but anyway...
I reverted these packages to 245.4-4ubuntu3
sudo aptitude install libnss-systemd=245.4-4ubuntu3
systemd-timesyncd=245.4-4ubuntu3 systemd-sysv=245.4-4ubuntu3
libnss-mymachines=245.4-4ubuntu3 systemd-container=245.4-4ubuntu3
libpam-systemd=245.4-4ubuntu3 systemd=245.4-4ubuntu3 libsystemd0=245.4-4ubuntu3
sudo reboot
All the VMs have access to the network again.
My setup:
I have 2 NICs on the server:
- eno1 is my WAN plugged to my ISP's router and attached to the br-wan bridge
- enp2s0 is my LAN and is attached to the br-lan bridge
I use static addressing
The LAN is IPv4 and IPv6
The WAN is IPv4 only
wlx00c0caa5e44f is a USB Wi-Fi adapter attached to br-lan using hostapd
VMs use the classic vnet attachement
vi /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
# No DHCP and no addresses set for the ethernet NIC
eno1:
addresses: []
dhcp4: false
dhcp6: false
optional: true
enp2s0:
addresses: []
dhcp4: false
dhcp6: false
optional: true
# Prevent virtual networks and Wi-Fi NIC from acquiring link local
IPv6 addresses (fe80::)
vnet:
match:
name: vnet*
link-local: [ ]
wlx00c0caa5e44f:
link-local: [ ]
bridges:
# Configure a static IPv4 address for br-wan
br-wan:
interfaces: [eno1]
addresses:
- 192.168.1.1/24
dhcp4: false
dhcp6: false
gateway4: 192.168.1.254
nameservers:
addresses:
- 9.9.9.9
search: []
# Isolate br-lan
br-lan:
interfaces: [enp2s0]
addresses: []
dhcp4: false
dhcp6: false
link-local: [ ]
optional: true
With this setup on systemd 245.4-4ubuntu3.6 the hypervisor and the VMs have
network access.
With the same setup on 245.4-4ubuntu3.7 the hypervisor has network access but
the VMs don't.
Workaround with systemd 245.4-4ubuntu3.7: allowing link-local on the
vnet interfaces
sudo vi /etc/netplan/01-netcfg.yaml
# vnet:
# match:
# name: vnet*
# link-local: [ ]
sudo netplan apply
sudo reboot
Now on systemd 245.4-4ubuntu3.7 the hypervisor and the VMs have
network access.
Thank you for your help
Tests performed with results:
On systemd 245.4-4ubuntu3 with no link-local addresses on the vnets
sudo aptitude install libnss-systemd=245.4-4ubuntu3 systemd-
timesyncd=245.4-4ubuntu3 systemd-sysv=245.4-4ubuntu3 libnss-
mymachines=245.4-4ubuntu3 systemd-container=245.4-4ubuntu3 libpam-
systemd=245.4-4ubuntu3 systemd=245.4-4ubuntu3
libsystemd0=245.4-4ubuntu3
sudo vi /etc/netplan/01-netcfg.yaml
vnet:
match:
name: vnet*
link-local: [ ]
sudo reboot
ip addr
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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master
br-lan state DOWN group default qlen 1000
link/ether 40:8d:5c:1d:92:b5 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UP group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
5: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-wan
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe1d:92b7/64 scope link
valid_lft forever preferred_lft forever
6: wlx00c0caa5e44f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
master br-lan state UP group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-lan state UNKNOWN group default qlen 1000
link/ether fe:54:00:09:3f:92 brd ff:ff:ff:ff:ff:ff
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UNKNOWN group default qlen 1000
link/ether fe:54:00:98:c4:fe brd ff:ff:ff:ff:ff:ff
Results: OK. Hypervisor and VMs have network access
On systemd 245.4-4ubuntu3.7 with no link-local addresses on the vnets
sudo aptitude install libnss-systemd=245.4-4ubuntu3.7 systemd-
timesyncd=245.4-4ubuntu3.7 systemd-sysv=245.4-4ubuntu3.7 libnss-
mymachines=245.4-4ubuntu3.7 systemd-container=245.4-4ubuntu3.7 libpam-
systemd=245.4-4ubuntu3.7 systemd=245.4-4ubuntu3.7
libsystemd0=245.4-4ubuntu3.7
sudo vi /etc/netplan/01-netcfg.yaml
vnet:
match:
name: vnet*
link-local: [ ]
sudo reboot
ip addr
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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master
br-lan state DOWN group default qlen 1000
link/ether 40:8d:5c:1d:92:b5 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UP group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
5: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-wan
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe1d:92b7/64 scope link
valid_lft forever preferred_lft forever
6: wlx00c0caa5e44f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
master br-lan state UP group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UNKNOWN group default qlen 1000
link/ether fe:54:00:09:3f:92 brd ff:ff:ff:ff:ff:ff
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UNKNOWN group default qlen 1000
link/ether fe:54:00:98:c4:fe brd ff:ff:ff:ff:ff:ff
Results: KO. Hypervisor has network access and the VMs don't
On systemd 245.4-4ubuntu3.7 with link-local addresses on the vnets
sudo aptitude install libnss-systemd=245.4-4ubuntu3.7 systemd-
timesyncd=245.4-4ubuntu3.7 systemd-sysv=245.4-4ubuntu3.7 libnss-
mymachines=245.4-4ubuntu3.7 systemd-container=245.4-4ubuntu3.7 libpam-
systemd=245.4-4ubuntu3.7 systemd=245.4-4ubuntu3.7
libsystemd0=245.4-4ubuntu3.7
sudo vi /etc/netplan/01-netcfg.yaml
# vnet:
# match:
# name: vnet*
# link-local: [ ]
sudo netplan apply
sudo reboot
ip addr
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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master
br-lan state DOWN group default qlen 1000
link/ether 40:8d:5c:1d:92:b5 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UP group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
5: br-wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 40:8d:5c:1d:92:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-wan
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe1d:92b7/64 scope link
valid_lft forever preferred_lft forever
6: wlx00c0caa5e44f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
master br-lan state UP group default qlen 1000
link/ether 00:c0:ca:a5:e4:4f brd ff:ff:ff:ff:ff:ff
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-lan state UNKNOWN group default qlen 1000
link/ether fe:54:00:09:3f:92 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe09:3f92/64 scope link
valid_lft forever preferred_lft forever
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master
br-wan state UNKNOWN group default qlen 1000
link/ether fe:54:00:98:c4:fe brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe98:c4fe/64 scope link
valid_lft forever preferred_lft forever
Results: KO. Hypervisor and VMs have network access but with link-
local addresses on the vnet interfaces
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
Uname: Linux 5.4.0-74-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 19 15:44:06 2021
InstallationDate: Installed on 2020-04-25 (420 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
MachineType: Gigabyte Technology Co., Ltd. H97N-WIFI
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
TERM=xterm-256color
PATH=(custom, no user)
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic
root=UUID=a33535a5-f1fc-47b7-912f-548c5bef1b8e ro lockdown=confidentiality
slab_nomerge slub_debug=FZ mce=0 vsyscall=none
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97N-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H97N-WIFI
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933002/+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
