On 21 January 2014 21:23, Robert Collins <robe...@robertcollins.net> wrote:
> In OpenStack we've got documentation[1] that advises setting a low MTU > for tenants to workaround this issue (but the issue itself is > unsolved) - this is a problem because PMTU is fairly important :) > Lowering *every* tenant when one tenant somewhere hits a new tunnel > with a lower physical packet size limit isn't an answer. > The right answer is probably that (a) GRE drops packets it can't take (it used to return a spoofed PMTU exceeded, which was faintly naughty cos it's not a router, and it breaks non-IP protocols; sounds like it fragments now, which is probably no better), (b) we use the DHCP option to advertise the right MTU, and (c) we require Neutron plugins to work out the MTU, which for any encap except VLAN is (host interface MTU - header size). At this point we probably discover that nothing respects the MTU option in DHCP, mind you (I'm not saying it doesn't work; I'm just saying, have you ever tried it?) This solution is pedantically correct and I would actually like to see it implemented, but there's probably something more pragmatic that can be done. -- Ian.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
