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

Test Plan: Add IPv6 tunnel encapsulation limit option header

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      ( ) The new test plan is aligned with the epic's acceptance criteria

      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 test plan/test case pass successfully on all non blocking functions of the feature

      Show
      ( ) The new test plan is aligned with the epic's acceptance criteria 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 test plan/test case pass successfully on all non blocking functions of the feature
    • None
    • rhel-net-ovs-dpdk

      This task is tracking the test case writing activities to cover 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-triage ovsdpdk triage
              nstbot NST Bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: