Confirming the fix. Thanks!
Before:
Sep 19 18:10:39 s1264 systemd-networkd[28308]:
[/etc/systemd/network/eth0.network:18] Interface label is not valid or too
long, ignoring assignment: eth0:1
Sep 19 18:10:39 s1264 systemd-networkd[28308]: Enumeration completed
Sep 19 18:10:39 s1264 systemd-networkd[28308]: eth0: Configured
After:
Sep 19 22:51:16 s1264 systemd-networkd[11832]: Enumeration completed
Sep 19 22:51:16 s1264 systemd-networkd[11832]: eth0: Configured
Sep 19 22:51:53 s1264 systemd-networkd[20544]: Enumeration completed
Sep 19 22:51:53 s1264 systemd-networkd[20544]: eth0: Configured
eth0:1 Link encap:Ethernet HWaddr 00:25:90:86:71:4c
inet addr:10.251.0.1 Bcast:10.251.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:dfb00000-dfbfffff
** Tags added: verification-done-xenial
** Tags removed: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714933
Title:
Xenial: Please roll SRU with upstream fix for networkd to "accept
colons in network interface names"
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Zesty:
In Progress
Status in systemd source package in Artful:
Fix Released
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://github.com/systemd/systemd/pull/5117
issue: https://github.com/systemd/systemd/issues/4057
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714933/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
