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

Steve Langasek steve.langasek at canonical.com
Thu Nov 8 17:05:16 UTC 2018


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

-- 
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 Committed

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



More information about the foundations-bugs mailing list