[Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

[Dimitri John Ledkov]

** Description changed:

+ [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.

** Changed in: systemd (Ubuntu Zesty)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  New
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