[Bug 1771704] Re: support for ipv4 link-local addressing

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.39

---------------
netplan.io (0.39) cosmic; urgency=medium

  * New upstream release:
    - Allow link-local addresses to be configured. (LP: #1771704)
    - Forces bridges with no addresses to be brought online. (LP: #1736975)

 -- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com>  Mon, 16 Jul 2018
08:15:05 -0400

** Changed in: netplan.io (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1771704

Title:
  support for ipv4 link-local addressing

Status in netplan:
  In Progress
Status in netplan.io package in Ubuntu:
  Fix Released

Bug description:
  Per https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983,
  link-local address support was previously handled via integration
  between avahi-autoipd and dhclient.  systemd-networkd does not invoke
  dhclient.  It also has direct support for configuring link-local ipv4
  addresses.  But this support is not enabled by default.

  It should be possible for a system configured via netplan to make use
  of link-local ipv4 addresses, without needing to configure systemd-
  networkd directly.

  Historically we do not turn on link-local ipv4 support automatically
  on servers (avahi-autoipd not installed by default), and we use link-
  local addresses only as a fallback when dhcp gives no response.  So
  this should likely not be enabled by default, but instead be exposed
  as an additional configuration option in netplan yaml.

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