[Bug 1747455] Re: netplan does not support defining route with scope 'link'

Wed Dec 5 18:47:48 UTC 2018

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

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

  * Fix idempotency in renaming: bond members should be exempt from rename, as
    they may all share a single MAC for the bond device. (LP: #1802322)
  * tests/integration.py: add test designed to catch the above regression.

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>  Wed, 21 Nov 2018
14:42:59 -0500

** 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/1747455

Title:
  netplan does not support defining route with scope 'link'

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]
  netplan.io users who define custom routes

  [Test case]
  1) Configure netplan.
  2) Add a route:
    [...]
    routes:
      - to: 10.10.10.0/24
        scope: link

  3) Validate that the route is correctly added to the routing table
  (using 'sudo ip route').

  [Regression Potential]
  Adding a feature to allow setting scope for routes or other route parameters lead to additional complexity in the configuration for the routes. As such the additional setting may confuse systemd-networkd if set incorrectly in attempting to add routes that would be invalid or useless. Any issues with adding routes (as evidenced in logs from systemd-networkd) should be investigated as possible regressions caused by the addition of the 'scope' parameter.

  ---

  I have an hosted server and for some reason, I only have a single
  global ipv6 with prefix /128.

  To be able to reach the world using IPv6, I have to declare a route to
  the router, and then the default route:

  In traditionnal ifupdown, this is done using the following lines:

  post-up /sbin/ip -family inet6 route add 2001:41d0:8:8fff:ff:ff:ff:ff dev eth0
  post-up /sbin/ip -family inet6 route add default via 2001:41d0:8:8fff:ff:ff:ff:ff

  I think that in networkd it should be declare as:

  [Route]
  Destination=2001:41d0:8:8fff:ff:ff:ff:ff
  Scope=link

  [Route]
  Gateway=192.168.0.1

  Actually, I don't find anyway to express such route in netplan. I can
  easily define the gateway route setting 0.0.0.0 as 'to', but it look
  like there is currently now way to define the "link" scoped route.

  netplan "route" should support a scope attribute that match networkd
  Scope attribute.

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