Comment 4 for bug 2060778
Revision history for this message
| Csillagszemű Pityesz (hippi-viking) wrote Re: netplan, multiple dhcp route with metric failure | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
As far as I know I am not using NetworkManager, 'nmcli dev' shows the following:
DEVICE TYPE STATE CONNECTION
virbr0 bridge nem kezelt --
vm-br0 bridge nem kezelt --
lan ethernet nem kezelt --
lo loopback nem kezelt --
iscsi vlan nem kezelt --
vm vlan nem kezelt --
('nem kezelt' means not managed; the 'iscsi' interface is a statically configured vlan device to access the VM storage backend)
My usecase is somewhat special as I use the desktop distribution with a somewhat more complicated setup than usual because I need to use networked VMs for my work. I am using networkd as I thought it would be more appropriate than NetworkManager.
Upon further investigation to the original matter I believe it is really an issue with systemd-resolved instead of netplan, so sorry for taking your time. My local router resolves hostnames differently for the host and the VM networks. After startup or issuing a 'netplan apply' after resume the resolver for the host ('lan' network) is being used as primary, BUT after resume not issuing a 'netplan apply' command somehow the resolver for the VM network takes precedence - which is bad. Then the host will obviously try to access the 'misresolved' systems through the wrong gateway, which is really only the symptom not the cause.