[Bug 1608447] Re: identify a device via its subchannel

2022-04-29 Thread Lukas Märdian
Migrating this to the "netplan" project. "nplan" is no more. ** Also affects: netplan Importance: Undecided Status: New ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Wishlist ** Changed in: nplan (Ubuntu) Status:

[Bug 1608447] Re: identify a device via its subchannel

2016-08-17 Thread Martin Pitt
** Changed in: nplan (Ubuntu) Status: New => Triaged ** Changed in: nplan (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608447 Title: identify

[Bug 1608447] Re: identify a device via its subchannel

2016-08-01 Thread ChristianEhrhardt
Yes, as I stated before that would do it. As I said it would be just about eliminating the remaining "en" portion and sound more platform aware which appears as a saner configuration to the end user. So right on parsing this: match: subchannel: "c000" Could be converted internally to:

[Bug 1608447] Re: identify a device via its subchannel

2016-08-01 Thread Martin Pitt
Err sorry, that was copy'd from the mailing list. So it seems that *is* exposed as part of the name, so match: name: "en*c000*" might just do what you want? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1608447] Re: identify a device via its subchannel

2016-08-01 Thread Martin Pitt
I'm afraid I don't know what that means, this might be a z series specific concept? This isn't exposed by networkd or NM directly, but it might be possible that the subchannel is part of the ifnames generated name so that you can use a name glob? ** Changed in: nplan (Ubuntu) Status: New