[Bug 1807273] Re: netplan not respecting mtu
Launchpad Bug Tracker
1807273 at bugs.launchpad.net
Wed May 8 00:00:42 UTC 2019
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---------------
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
pass; it breaks "default" renderer behavior when multiple files may set
a global renderer and expect the last to take effect globally.
(LP: #1825206)
* debian/patches/git_reorg_netdef_validation_181b583.patch: correct the
fallout from the above change: validate netdefs in a single pass at the
very end of parsing, once we know which is the applicable renderer. This
makes sure tunnels get validated correctly.
netplan.io (0.96-0ubuntu0.18.04.3) bionic; urgency=medium
* debian/patches/disable-networkd-tunnels-ipip-gre.patch: disable IPIP and
GRE tunnel tests; those appear to be broken because neither the kernel nor
networkd bring up the device automatically as in other releases.
netplan.io (0.96-0ubuntu0.18.04.2) bionic; urgency=medium
* d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-online.target, as in some
minimal setups there might be no job requiring network-online.target,
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)
netplan.io (0.96-0ubuntu0.18.04.1) bionic; urgency=medium
* Backport netplan.io 0.96 to 18.04.
* debian/patches/glib_changes.patch: Patch tests to work again on older GLib.
* debian/control: adjust Depends for bionic / re-add nplan package.
netplan.io (0.96-0ubuntu1) disco; urgency=medium
* New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
* debian/control: Update Maintainer for ubuntu upload.
netplan.io (0.95-2) unstable; urgency=medium
* Set Priority to optional (Closes: #920327).
netplan.io (0.95-1) unstable; urgency=medium
* New upstream release.
* Update autopkgtests from the upstream.
* Add debian/watch following GitHub releases.
* Add Homepage (Closes: #917233).
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.
netplan.io (0.90.1) disco; urgency=medium
* Do not assume /etc/network exists in postinst, as netbase 5.5 no longer
creates it.
* netplan/cli/commands/ip.py: fix a flake.
netplan.io (0.90) disco; urgency=medium
* New upstream release:
- build: fixes for building on RPM-based distros
- build: code prettiness changes (make indentation consistent)
- Fix device name-changes detection (LP: #1770082)
- Add support for IPv6 Privacy Extensions (LP: #1750392)
- Add dhcp{4,6}-overrides to control DNS, NTP, hostname updates via DHCP
(LP: #1759014)
- Clarify MAC and MTU setting requirements (LP: #1800668)
- Various documentation fixes (LP: #1800669)
- Improve error reporting to give clearer messages and context
(LP: #1800670)
- Skip non-physical/bond interfaces when applying renames (LP: #1802322)
netplan.io (0.40.2-1) unstable; urgency=medium
* Upload to Debian (Closes: #882661).
netplan.io (0.40.2) cosmic; urgency=medium
* tests/integration.py: Mark regexes with r to pacify pycodestyle's
W605.
-- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com> Fri, 26 Apr 2019
15:19:47 -0400
** Changed in: netplan.io (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: netplan.io (Ubuntu Cosmic)
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/1807273
Title:
netplan not respecting mtu
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
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
More information about the foundations-bugs
mailing list