Comment 9 for bug 2055333
Revision history for this message
| Danilo Egea Gondolfo (danilogondolfo) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
To get you configuration working you need to remove the match and set-name stanzas (which were never required really). Using the definition ID as the interface name (the "lo" inside "ethernets") is enough to configure an interface using its name. And by removing that it will work on Jammy.
As you noticed, there seem to be some change in behavior in newer versions of systemd.
The configuration that uses match.macaddress I wouldn't expect to work actually works on Noble. Although, I've found this by accident:
---
Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Could not set WakeOnLan to off, ignoring: Operation not supported
Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Failed to rename network interface 3 from 'dummy123' to 'lo': File exists
Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Failed to process device, ignoring: File exists
---
I also have a dummy interface in my configuration and it doesn't have a permanent mac address as well. Although, udev apparently tried to apply the set-name from ethernets.lo to this interface as if the match.macaddress matched both.