Resume from Standby vmnet1/8 connected instead of Wired LAN

Bug #2064877 reported by Peter Stein
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Netplan
New
Undecided
Unassigned
netplan.io (Ubuntu)
Triaged
Medium
Unassigned
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

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.

Revision history for this message
Peter Stein (stein.peter) wrote :
Revision history for this message
Peter Stein (stein.peter) wrote :
Revision history for this message
Lukas Märdian (slyon) wrote :

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.

tags: added: foundations-todo
Changed in netplan.io (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Peter Stein (stein.peter) wrote :
Revision history for this message
Peter Stein (stein.peter) wrote :
Revision history for this message
Peter Stein (stein.peter) wrote :

Hy, I found a workaround for me to copy a file /etc/NetworkManager/system-connections/LAN-Homenet.nmconnection from my old Jammy installation AND do not apply any changes in kde-settings. There are only one lan-connection without vmnet1/8 an resume from standby reconnect correctly

Revision history for this message
Scott Kenney (scott-kenneyok) wrote :

Same issue for me. Was using a script for Proton VPN loaded into the LAN connection. Deleted the custom connection and rebooted. VMnet1 and 8 stopped trying to connect, and as a bonus now my KDE weather widget is working again. Will use the GUI ProtonVPN application to make changes to VPN.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.