Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-466

Add IPv6 tunnel encapsulation limit option header

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • ovs-dpdk
    • Add IPv6 tunnel encapsulation limit option header
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      Given a system administrator is configuring OVS with ip6gre tunnels, 

      When they set up and use ip6gre tunnels through the OVS userspace implementation,

      Then the packets transmitted should include the IPv6 "Tunnel Encapsulation Limit" option header to make sure that the packet format matches that of the kernel space implementation.

      ( ) The epics work is available in a downstream build (nightly/async or other)

      ( ) Test coverage is available in downstream CI if applicable

      ( ) All cards under the epic have been moved to Done

      ( ) Failed Test Plans have bugs added as children to the epic/feature.

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given a system administrator is configuring OVS with ip6gre tunnels,  When they set up and use ip6gre tunnels through the OVS userspace implementation, Then the packets transmitted should include the IPv6 "Tunnel Encapsulation Limit" option header to make sure that the packet format matches that of the kernel space implementation. ( ) The epics work is available in a downstream build (nightly/async or other) ( ) Test coverage is available in downstream CI if applicable ( ) All cards under the epic have been moved to Done ( ) Failed Test Plans have bugs added as children to the epic/feature.
    • rhel-net-ovs-dpdk
    • 100% To Do, 0% In Progress, 0% Done
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the feature request described below.
       
      BZ2140500
      reported that for ip6gre tunneled mirrors OVS userspace and kernel space there are different packet formats.

      On inspection it is seen that the kernel space tunnels adds an IPv6 Destination Options extension header.

      The option is the "Tunnel Encapsulation Limit" [0]. This limits the Nested encapsulations and defaults to 4. This is used to help guard against misconfigured networks where there is are recursive encapsulations of a packet.

      It is not a bug to not have option this with userspace but it is not best practice to have different packet formats from userspace and kernel space.

      This RFE is to align userspace and kernel space for ip6gre so that packet formats are matching. Most likely this will be through adding the "Tunnel Encapsulation Limit" header to userspace.

      [0]
      https://www.rfc-editor.org/rfc/rfc2473.html#section-4.1.1

              ovsdpdk-bot ovsdpdk bot
              rhn-support-ktraynor Kevin Traynor
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: