[Bug 1807273] Re: netplan not respecting mtu

Mon Mar 11 22:10:53 UTC 2019

Closing as Fix Released for upstream and for disco (netplan.io 0.95
contained the fix):

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.

** Description changed:

+ [Impact]
+ DHCP configurations where custom settings (MTU) need to be applied. This is a subset of the changes presented in bug 1759014.
+ 
+ [Test case]
+ 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza:
+ 
+ network:
+   version: 2
+   ethernets:
+     engreen:
+       dhcp4: true
+       dhcp4-overrides:
+         use-mtu: false
+ 
+ Additionally, if so required, add a custom MTU to the configuration.
+ e.g.
+ 
+       mtu: 1700
+ 
+ (See https://netplan.io/reference#dhcp-overrides for the available
+ options)
+ 
+ 2) Run 'netplan apply' or reboot to have the configuration applied.
+ 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values.
+ 
+ [Regression potential]
+ Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility.
+ 
+ ---
+ 
  This is very similar to https://bugs.launchpad.net/bugs/1724895, but I
  decided to open this as i have tried what has succeeded for others.
  Thanks for any assistance.

  I'm trying to set the MTU to 1500 and using a match on mac address, but
  after a netplan apply or reboot, it does not change or stick. This is on
  a EC2 T2.Medium instance. Actual configuration from a dev server:

  network:
-   version: 2
-   ethernets:
-     eth0:
-       match:
-         macaddress: 12:0f:ae:49:5d:06
-       mtu: 1500
-       dhcp4: true
-       nameservers:
-         search: [ devbuilds.vpc, ec2.internal ]
+   version: 2
+   ethernets:
+     eth0:
+       match:
+         macaddress: 12:0f:ae:49:5d:06
+       mtu: 1500
+       dhcp4: true
+       nameservers:
+         search: [ devbuilds.vpc, ec2.internal ]

  $> cat /var/run/systemd/network/10-netplan-eth0.link
  [Match]
  MACAddress=12:0f:ae:49:5d:06

  [Link]
  WakeOnLan=off
  MTUBytes=1500

  $> cat /var/run/systemd/network/10-netplan-eth0.network
  [Match]
  MACAddress=12:0f:ae:49:5d:06

  [Network]
  DHCP=ipv4
  Domains=devbuilds.vpc ec2.internal

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $> ip link show eth0
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP mode DEFAULT group default qlen 1000
-     link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
+     link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
  # manually set MTU
  $> sudo ip link set dev eth0 mtu 1500
  $> ip link show eth0
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
-     link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
+     link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
  $> sudo netplan generate
  $> sudo netplan apply
  $> ip link show eth0
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP mode DEFAULT group default qlen 1000
-     link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
+     link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff

  The last netplan commands could be replaced with a reboot with the same
  result. This configuration seemed to help others, so hopefully i'm
  simply missing something or perhaps this is related to EC2?

  Attaching output of cloud-init

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

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

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

** Changed in: netplan.io (Ubuntu)
       Status: New => In Progress

** Changed in: netplan.io (Ubuntu)
       Status: In Progress => 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/1807273

Title:
  netplan not respecting mtu

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  DHCP configurations where custom settings (MTU) need to be applied. This is a subset of the changes presented in bug 1759014.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza:

  network:
    version: 2
    ethernets:
      engreen:
        dhcp4: true
        dhcp4-overrides:
          use-mtu: false

  Additionally, if so required, add a custom MTU to the configuration.
  e.g.

        mtu: 1700

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility.

  ---

  This is very similar to https://bugs.launchpad.net/bugs/1724895, but I
  decided to open this as i have tried what has succeeded for others.
  Thanks for any assistance.

  I'm trying to set the MTU to 1500 and using a match on mac address,
  but after a netplan apply or reboot, it does not change or stick. This
  is on a EC2 T2.Medium instance. Actual configuration from a dev
  server:

  network:
    version: 2
    ethernets:
      eth0:
        match:
          macaddress: 12:0f:ae:49:5d:06
        mtu: 1500
        dhcp4: true
        nameservers:
          search: [ devbuilds.vpc, ec2.internal ]

  $> cat /var/run/systemd/network/10-netplan-eth0.link
  [Match]
  MACAddress=12:0f:ae:49:5d:06

  [Link]
  WakeOnLan=off
  MTUBytes=1500

  $> cat /var/run/systemd/network/10-netplan-eth0.network
  [Match]
  MACAddress=12:0f:ae:49:5d:06

  [Network]
  DHCP=ipv4
  Domains=devbuilds.vpc ec2.internal

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $> ip link show eth0
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP mode DEFAULT group default qlen 1000
      link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
  # manually set MTU
  $> sudo ip link set dev eth0 mtu 1500
  $> ip link show eth0
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
      link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
  $> sudo netplan generate
  $> sudo netplan apply
  $> ip link show eth0
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP mode DEFAULT group default qlen 1000
      link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff

  The last netplan commands could be replaced with a reboot with the
  same result. This configuration seemed to help others, so hopefully
  i'm simply missing something or perhaps this is related to EC2?

  Attaching output of cloud-init

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