Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
| Zesty |
Fix Released
|
Undecided
|
Unassigned | ||
| Artful |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
networkd cannot manage interface names with ':' in them. As used commonly, by convention, by other tools.
[Fix]
Update networkd validation routines and test-suites to accept network interface names with ':' in it.
[Testcase]
Create an inteface with ':' in its name and use it anywhere where systemd validates ifname. E.g. Socket BindToDevice definition, nspawn network zone info, Label= in [Address] section in networkd.
[Regression Potential]
This fix will change validation routines, and thus commands or settings that were previously rejected or ignored will now take effect. Specifically Label= settings in networkd may lead to networking conflicts. The justification for this change is that networkd should really use the sensible ':' ifnames that the user is requesting systemd to use.
[Original Bug Reprot]
PR: https:/
issue: https:/
Before the networkd from 231 was backported, it was possible to use interface alias names that contained a colon, e.g. eth0:1. This is commonly used to make legacy tools like "ifconfig" work, because they *expect* a colon in the interface name.
Martin told me to file a bug for this.
Merging networkd from 231 lead to a regression where valid configs were not accepted anymore after the backport. Please merge that fix for the regression.
| summary: |
- Xenial: Please merge upstream fix for networkd to "accept colons in - network interface names" + Xenial: Please roll SRU with upstream fix for networkd to "accept colons + in network interface names" |
| Changed in systemd (Ubuntu Artful): | |
| status: | New → Fix Released |
| description: | updated |
| Changed in systemd (Ubuntu Zesty): | |
| status: | New → In Progress |
| Changed in systemd (Ubuntu Xenial): | |
| status: | New → In Progress |
| Brian Murray (brian-murray) wrote Please test proposed package | #1 |
| Changed in systemd (Ubuntu Xenial): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed verification-needed-xenial |
| Tobias Wolf (towolf) wrote | #2 |
| tags: | added: verification-done-xenial |
| tags: | removed: verification-needed-xenial |
| Dimitri John Ledkov (xnox) wrote | #3 |
| Brian Murray (brian-murray) wrote | #4 |
| Changed in systemd (Ubuntu Zesty): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed-zesty |
| Dimitri John Ledkov (xnox) wrote | #5 |
| tags: |
added: verification-done verification-done-zesty removed: verification-needed verification-needed-zesty |
| Launchpad Janitor (janitor) wrote | #6 |
| Changed in systemd (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Łukasz Zemczak (sil2100) wrote Update Released | #7 |
| Launchpad Janitor (janitor) wrote | #8 |
| Changed in systemd (Ubuntu Zesty): | |
| status: | Fix Committed → Fix Released |
Hello Tobias, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/