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

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.40.1~18.04.2

---------------
netplan.io (0.40.1~18.04.2) bionic; urgency=medium

  * Fix typo breaking rename on 'netplan apply'. (LP: #1770082)

netplan.io (0.40.1~18.04.1) bionic; urgency=medium

  * Backport netplan 0.40.1 to 18.04. (LP: #1793309)

netplan.io (0.40.1) cosmic; urgency=medium

  * tests/generate.py: use random.sample() instead of random.choices() to
    better support older pythons.
  * Deal gracefully with empty files on 'netplan apply' (LP: #1795343)

netplan.io (0.40) cosmic; urgency=medium

  * New upstream release:
    - networkd: route source is PreferredSource= not From=
    - Improve NetworkManager error reporting on unrenderable routes.
    - Don't render ipv4 dns-search unless we have an ipv4 address.
      (LP: #1786726)
    - Set permissive umask on networkd .network, .link and .netdev files
      (LP: #1736965, LP: #1768560)
    - Fix support for link-scope routes. (LP: #1747455)
    - Update man pages for deletion of replug code.
    - Spell Gratuitous ARP correctly and make it work. (LP: #1756701)
    - Many typo fixes for documentation. (LP: #1783940)
    - Various build system fixes.
    - Fix integration tests:
      - iproute2 output changes for link-scope routes
      - fix stability of networkd igmp-resend test
      - fix manual_addresses test now that networkd lists ~. domain
    - Deduplicate code for parsing interface options
    - Add support for optional-addresses.

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)

netplan.io (0.38) cosmic; urgency=medium

  * New upstream release:
    - Write udev .rules files to /run/udev/rules.d to enforce interface
      renaming. (LP: #1770082)
    - Don't traceback for 'netplan ip leases' when iface is not managed or
      doesn't DHCP (LP: #1768823)
    - Fix duplicate "/" path separator in error messages (LP: #1771440)
    - Fix incorrect terminal reset in 'netplan try' on Ctrl-C. (LP: #1768798)
    - Updated doc entries: mtu, fix fwmark->mark, cleanup optional.
      (LP: #1768783)
    - Added documentation validation at build.
    - Added configuration example for multi-ip interfaces.
  * tests/integration.py: fix test_eth_and_bridge autopkg test harder.
  * debian/control:
    - Add iproute2 to Depends.
    - Add python3-netifaces to Depends, Build-Depends.

 -- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com>  Mon, 22 Oct 2018
15:02:30 -0400

** Changed in: netplan.io (Ubuntu Bionic)
       Status: Fix Committed => 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:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ubuntu users who make use of IPv4 link-local addresses.

  [Test case]
  1) Add 'link-local: [ ipv4 ]' to the netplan configuration.
  2) Run 'sudo netplan apply'

  [Regression Potential]
  Enabling link local means additional addresses are available on the system, usually in the form "169.254.XXX.XXX". This is, in effect, a potential security issue if it is enabled on untrusted networks (it gives systems a fairly well known, discoverable IP address as attack surface). This is not considered a regression from previous releases of Ubuntu given that avahi has been available on desktop, with the same potential issue. The availability of extra addresses might however mean that the system is considered online or reachable via the additonal addresses earlier than previously possible, which may lead to confusion for the user.

  ---

  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