[Bug 2064877] Re: Resume from Standby vmnet1/8 connected instead of Wired LAN
Lukas Märdian
2064877 at bugs.launchpad.net
Mon May 6 12:54:44 UTC 2024
Would you mind sharing your Netplan configuration from
/etc/netplan/*.yaml ? Feel free to redact sensitive information that
could be contained.
This sounds like it could be related to the NetworkManager-Netplan
integration getting confused about the ordering of the connection
profiles.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags added: foundations-todo
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/2064877
Title:
Resume from Standby vmnet1/8 connected instead of Wired LAN
Status in Netplan:
New
Status in netplan.io package in Ubuntu:
Triaged
Status in network-manager package in Ubuntu:
New
Bug description:
Resume from Standby vmnet1/8 connected instead of Wired LAN
Vmware Workstation 17.5 installed in Kubuntu 24.04 Noble. If I rename default wired network 1 to My-LAN or make any changes to default LAN connection, after reboot I have three connections shown in KDE Plasma. LAN is connected BUT after Standby and Resume is the wrong connection connected vmnet1 or vmnet8 bun not default wired lan (customized).
Workaround is to delete customized lan connection and reboot.
In Kubuntu 22.04 Jammy was the renamed lan not a such problem, vmnet1/8 not seen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2064877/+subscriptions
More information about the foundations-bugs
mailing list