[Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Dan Streetman]

> The header of debian/patches/lp1845909/0001-network-rename-
linux_configure_after_setting_mtu-to-linux.patch in the eoan upload
appears to be a lie;

sorry, I didn't change the patch description from upstream, where my
patch actually did only change the function name.  This patch includes
some change from upstream commit
4ff296b02411bb4f0dc38f48cbab06f8645d2a08 because it is the proper way to
handle errors in the mtu handler function, but it's a large patch that I
didn't want to fully backport without reason.

Do you need me to update the patch description with that text and re-
upload, or should I separate out the specific change from the other
commit into a separate patch?

> And the statement in the description of this bug that "that commit is
already included in Eoan so this sru is needed only for Disco" is at
odds with the 5 patches related to this bug that are in this debdiff.

will update the sru template.

-- 
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/1845909

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Incomplete
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  when a networkd interface is configured with LinkLocalAddressing=no,
  networkd still assigns a link-local address to it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.

  [regression potential]

  this moves the point when ipv6ll is configured; regressions would most
  likely involve failure to correctly configure an ipv6ll address when
  desired.

  [other info]

  this bug was attempted to be fixed by 'debian/patches/networkd-honour-LinkLocalAddressing.patch' from upstream issue 9890, using a commit that does not correctly fix the issue and was never accepted upstream:
  https://github.com/systemd/systemd/issues/9890#issuecomment-455168751

  this SRU completely reverts that patch, and adds the correct fix which
  was merged upstream:
  https://github.com/systemd/systemd/commit/0e2fdb83bb5e22047e0c7cc058b415d0e93f02cf

  that commit is already included in Eoan so this sru is needed only for
  Disco.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845909/+subscriptions