51a697817d
The IPv6 header is twice the size of the IPv4 header, 40 vs 20 bytes, but the tunnel overhead constants are static, only accounting for an IPv4 header in all cases. In order to be correct it needs to treat the tunnel overhead different from the IP overhead at L3. This required removing the 20 byte IP overhead from the tunnel type overhead constants and creating a new option, ml2.overlay_ip_version, in order for the server to know which version will be used, since it calculates the MTU for the network. A version mis-match will now cause a tunnel sync to fail on the server. Moved all MTU tests to a common location to remove duplication. DocImpact Change-Id: Ia2546c4c71ff48b9fe2817fbad22b1fbf85f325b Closes-bug: #1584940
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.