[Bug 1355813] Re: Interface MTU management across MAAS/juju

[Mark Shuttleworth]

Do we need to take into account any overhead being added by the protocol
stack along the way?

For example, if the underlying MAAS machine can be told to use 9000 byte
MTUs and jumbo frames, then each layer up could adopt that, but might
need to chop off some of that for protocol / tunnel / encapsulation
overhead. I've seen cases where your "internal" interface needs to have,
say 20 byte smaller MTUs than the host. Perhaps THAT's the bit that we
should focus on specifying. So MAAS gets told "just jumbo frames here"
and then everything else focuses on understanding and allowing for
overhead, but maximising MTU subject to that overhead.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1355813

Title:
  Interface MTU management across MAAS/juju

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions