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

Mathieu Trudel-Lapierre mathieu.tl at gmail.com
Mon Mar 11 20:01:39 UTC 2019


This has landed already in Disco:

 netplan.io (0.95) disco; urgency=medium
 .
   * New upstream release:
     - Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
     - Added support for setting up IP tunnels; supporting the types: ipip,
       gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
       + Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
     - Add support to override networkd UseMTU setting (LP: #1807273)
     - Generate output files in dependency order
     - Refactored unit and integration tests, along with various cleanups.
     - Add DHCP overrides to control route usage and default metric for DHCP
       routes. (LP: #1776228)
     - Mitigate against bad matching on devices behind bonds then they share
       the same MAC from a physical interface. (LP: #1804861)
     - Added snapcraft.yaml.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
       Status: New

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

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

** Changed in: netplan
       Status: Fix Committed => Fix Released

** Changed in: netplan
     Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

** Description changed:

+ [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
+     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.
+ 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.

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

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



More information about the foundations-bugs mailing list