group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1714933@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 229-4ubuntu20

---------------
systemd (229-4ubuntu20) xenial; urgency=medium

  * resolved: recognize DNS names with more than one trailing dot as invalid
    (LP: #1600000)
  * Ignore failures to set Nice priority on services in containers.
    (LP: #1709536)
  * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
  * initramfs-tools: trigger udevadm add actions with subsystems first.
    (LP: #1713536)
  * networkd: Add support to set STP value on a bridge. (LP: #1665088)
  * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings.
    (LP: #1715131)
    - Drop cherrypick of uint16 config parser, superseeded by above commit.
  * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135)
    - networkd: add support to configure ARP, depedency of Primary/ActiveSlave.

 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>  Tue, 05 Sep 2017 14:01:51
+0100

** Changed in: systemd (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 Released
Status in systemd source package in Zesty:
  Fix Committed
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