© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Caught by this too. I get enp3s0, and have set net.ifnames=0 as a workaround.
I agree with the suggestion that the script should be simplified to match XXXX.N, where X is any alphanumeric. More conservatively: the first X could match a-z only, and the last X could match 0-9 only.
Question is, was there a reason for originally matching only specific patterns like ethM.N, wlanM.N etc? Was it to exclude certain other valid interface names which contain a dot but are not VLAN capable? Or perhaps it was just being overly cautious?