[Bug 1799487] Re: Support for sit (ipv6) tunnels

[Steve Langasek]

A possible SRU regression has been reported against netplan.io
0.96-0ubuntu0.18.10.2 in LP: #1825206.  This version has been rolled
back to -proposed while the investigation is ongoing.

** Changed in: netplan.io (Ubuntu Cosmic)
       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/1799487

Title:
  Support for sit (ipv6) tunnels

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu users who need to configure IP tunnels for their network.

  [Test case]
  1) Sign-up / set up an Hurricane Electric tunnel at www.tunnelbroker.net.
  2) Configure netplan for the new tunnel. e.g.

  network:
    version: 2
    renderer: networkd
    ethernets:
      eth0:
        addresses:
          - 1.1.1.1/24
          - "2001:cafe:face::1/64"  # provided by HE as routed /64
        gateway4: 1.1.1.254
    tunnels:
      he-ipv6:
        mode: sit
        remote: 2.2.2.2
        local: 1.1.1.1
        addresses:
          - "2001:dead:beef::2/64"
        gateway6: "2001:dead:beef::1"

  
  3) Run 'netplan apply' or reboot to apply the new configuration.

  [Regression potential]
  None; this adds a new type of device not previously available to users.

  ---

  Like many I use tunnelbroker.net for IPv6 connectivity on servers that
  lack native IPv6 connectivity through their provider.

  Back in ifupdown, this was done with a nice and short snippet that looked like this:
  ```
  auto he-ipv6
  iface he-ipv6 inet6 v4tunnel
      address 2001:470:1c:1d7::2
      netmask 64
      endpoint 216.66.38.58
      local 192.222.186.156
      mtu 1480
      ttl 64
  ```

  There is however no equivalent in netplan that I could find (on 18.04
  at least), instead I had to do the following to get networkd to setup
  the tunnel.

  1) Define a netdev (/etc/systemd/network/he-ipv6.netdev)
  ```
  [NetDev]
  Name=he-ipv6
  Kind=sit
  MTUBytes=1480

  [Tunnel]
  Local=54.39.107.213
  Remote=216.66.38.58
  TTL=64
  ```

  2) Define a network (/etc/systemd/network/he-ipv6.network)
  ```
  [Match]
  Name=he-ipv6

  [Network]
  Address=2001:470:1c:b62::2/64
  Gateway=2001:470:1c:b62::1
  ```

  3) Setup a dependency between my WAN interface and the tunnel (/etc/systemd/network/10-netplan-eth0.network.d/tunnel.conf)
  ```
  [Network]
  Tunnel=he-ipv6
  ```

  This then all works fine but has the very annoying side-effect of
  splitting my network config into a bunch of different pieces with
  everything in my netplan.yaml except for that tunnel which I have to
  configure directly in networkd and use systemd unit overrides to add
  the needed Tunnel statement to the netplan managed wan interface.

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