debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #06443
[Bug 2060778] Re: systemd-resolved switches primary interface for name resolution after suspend/resume cycle
Marking invalid due to lack of response.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060778
Title:
systemd-resolved switches primary interface for name resolution after
suspend/resume cycle
Status in Netplan:
Invalid
Status in systemd package in Ubuntu:
Invalid
Bug description:
Hardware/network: PC with single NIC, multiple vlans:
- untagged: default LAN, should be used by the host
- vlan 15: VM network, should only be used by the VM(s) running on the host
Netplan config:
network:
version: 2
renderer: networkd
ethernets:
lan:
match:
macaddress: "XX:XX:XX:XX:XX:XX"
set-name: lan
mtu: 9000
dhcp4: yes
dhcp6: yes
ipv6-privacy: true
bridges:
vm-br0:
dhcp4: yes
interfaces: [vm]
dhcp4-overrides:
route-metric: 200
vlans:
vm:
id: 15
link: lan
(Using networkd as the renderer some apps [App Store, Settings/Online Accounts,...] thinks I'm offline in ubuntu.)
The main problem is with this setup is that after resume the route metrics get mixed up, and the host tries to use the VM network as its default route.
Adding a 'dhcp4-overrides: {route-metric: 10}' stanza to LAN - as the netplan documentation suggests - results in the interfaces not coming up. (Issuing 'netplan try' results in 'Warning: The unit file, source configuration file or drop-ins of netplan-ovs-cleanup.service changed on disk. Run 'systemctl daemon-reload' to reload units.'.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060778/+subscriptions