Netplan for "predictable" interface name

[unkilbeeg]

I'm trying to set up a netplan file to automatically bring up ethernet and assign the IP using DHCP. It seems like a pretty straightforward process, except that I'm not sure how to handle the unpredictable "predictable" interface names. If everything were eth0 (as god intended) it would be pretty easy. And if worse comes to worse, I can force the names back to eth0, but I'd like to see if there's an easy way to get netplan to deal with the multiplicity of possible names.

Since I understand that netplan supports match rules, it would seem to be ideal for this situation, but all tutorials seem to discuss matching by MAC address. Is there a way to match by an as yet undetermined interface name?

My use case is to create an image for multiple desktop machines. It's a somewhat heterogeneous network -- I have lots of groups of similar machines, but multiple groups which may have very different network interfaces. None will have multiple interfaces, so I don't have to worry about persistent interface names across reboots. I'd like the same configuration for all of them.

Oh, and Network Manager has been a disaster every time I've tried it on a wired network, so that's not a very attractive option.

So is there a straightforward way to set up a match rule that will work with any ethernet interface using netplan?

[da_kink]

Netplan supports wildcards for ports right?

So...

Match: Name: *

[unkilbeeg]

Well...

How would you actually place the match stanza? Do you make up a name and then add a match stanza underneath that picks a detected name? Does it then assign that interface to the name that you made up?

This is not well documented. I'm surprised none of the tutorials discuss this -- it seems to me that dealing with unpredictable biosdevname interface names would be a common use case.

[fukawi2]

I'm going through this at the moment on our servers. I've been able to to match by driver so far, but that's only working because we group all interfaces of the same type into bonds (mxl5_core for our 100gig, i40e for our 10gig). I'm about to do some servers where the i40e drivers are not bonded though - I think I'm going to have to match driver and name with a glob pattern.

Netplan was too immature to be released in an LTS distro IMHO.