yahoo-eng-team team mailing list archive

[Brian Haley <1584940@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The MTU calculations are using using values from the ML2 constants file
like:

# Network Type MTU overhead
GENEVE_ENCAP_MIN_OVERHEAD = 50
GRE_ENCAP_OVERHEAD = 42
VXLAN_ENCAP_OVERHEAD = 50

But those values are assuming IPv4 - for example, IPv4 header of 20
bytes, VXLAN header of 30 bytes.

We should be calculating the IP overhead independent of the tunnel type
overhead in order to support an IPv6 data plane.

Since we know local_ip (tunnel endpoint) from ml2_conf.ini, we can
dynamically calculate this at startup time.

** Affects: neutron
     Importance: Undecided
     Assignee: Brian Haley (brian-haley)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1584940

Title:
  MTU calculations only support IPv4 tunnel endpoints don't account for
  IPv6

Status in neutron:
  In Progress

Bug description:
  The MTU calculations are using using values from the ML2 constants
  file like:

  # Network Type MTU overhead
  GENEVE_ENCAP_MIN_OVERHEAD = 50
  GRE_ENCAP_OVERHEAD = 42
  VXLAN_ENCAP_OVERHEAD = 50

  But those values are assuming IPv4 - for example, IPv4 header of 20
  bytes, VXLAN header of 30 bytes.

  We should be calculating the IP overhead independent of the tunnel
  type overhead in order to support an IPv6 data plane.

  Since we know local_ip (tunnel endpoint) from ml2_conf.ini, we can
  dynamically calculate this at startup time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1584940/+subscriptions