[Bug 1717471] Re: networkd does not accept / set advertised mtu
Dimitri John Ledkov
launchpad at surgut.co.uk
Fri Sep 15 09:11:00 UTC 2017
xnox> wgrant, t0mb0, veebers - i think i will just change ubuntu compiled in default for systemd-networkd to be honest.
<wgrant> xnox: That sounds perilous.
<xnox> wgrant, had to google that word.
<xnox> wgrant, alternatives is to bake that into nplan, or bake that into the cloud-image alone
<wgrant> xnox: nplan makes the most sense, IMO, rather than changing a confusing non-configurable upstream default silently in a distro patch.
<xnox> wgrant, i did that to accept search domains in resolved =/ because there is no easy way to set defaults for that, as it needs to go into the network file, and systemd only considers the first matching network file and ignores the rest (or some such)
<wgrant> Er yeah, I meant .network in the ticket when I said .link. The .link is fine.
<wgrant> systemd is so lovely.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1717471
Title:
networkd does not accept / set advertised mtu
Status in nplan package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
<wgrant> Right, so as far as I can tell the neutron-api on lcy01 is
configured to advertise an instance interface MTU of 1400, though
that's lower than it has to be, and the new DHCP setup with networkd
just doesn't respect that DHCP option.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions
More information about the foundations-bugs
mailing list