Skip to content

Add README for Double GUE Decapsulation#5081

Closed
mellowdrifter wants to merge 1 commit intomainfrom
mellowdrifter-patch-1
Closed

Add README for Double GUE Decapsulation#5081
mellowdrifter wants to merge 1 commit intomainfrom
mellowdrifter-patch-1

Conversation

@mellowdrifter
Copy link
Copy Markdown

@mellowdrifter mellowdrifter commented Feb 11, 2026

No description provided.

@mellowdrifter mellowdrifter requested a review from a team as a code owner February 11, 2026 17:49
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @mellowdrifter, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new test entry into the test registry. The primary goal is to formally register a test for double GUE decapsulation, ensuring that this specific network functionality is covered and trackable within the existing test framework.

Highlights

  • New Test ID Added: A new test entry with ID "PF-1.24" and description "Double GUE Decapsulation" has been added to the testregistry.textproto file.
Changelog
  • testregistry.textproto
    • Added a new 'test' block for "Double GUE Decapsulation" with ID "PF-1.24".
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@OpenConfigBot
Copy link
Copy Markdown

OpenConfigBot commented Feb 11, 2026

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new test entry for 'Double GUE Decapsulation' with ID 'PF-1.24' to the test registry. The change is straightforward, but I've noted that the new test entry is missing a readme field, which is important for test documentation and maintainability. Please add a link to the corresponding README file.

@coveralls
Copy link
Copy Markdown

coveralls commented Feb 11, 2026

Pull Request Test Coverage Report for Build 22145898347

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall first build on mellowdrifter-patch-1 at 10.076%

Totals Coverage Status
Change from base Build 22145251219: 10.1%
Covered Lines: 2300
Relevant Lines: 22826

💛 - Coveralls

@mellowdrifter mellowdrifter changed the title Add ID for Double GUE Decapsulation Add README for Double GUE Decapsulation Feb 11, 2026
| Flow Type | Header Layer | Source IP | Destination IP | UDP Port | DSCP | TTL |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| **Flow Type #1 (IPv6/IPv6/IPv4)** | Outer IP | ATE-P1-IP | DECAP-DST-OUTER | 6081 | 35 | 70 |
| | Middle IP | IPV6-MID-SRC | DECAP-DST-INNER | 6081 | 32 | 60 |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per https://datatracker.ietf.org/doc/html/draft-ietf-intarea-gue-09, the default port is UDP:6080. We should have all our tests using 6080 unless there is a test which is proving that the NOS allows for ports other than 6080 too. Currently NOSs lacks support for ports other than 6080. If more FNTs request tests of 6081, lot of our FNTs will fail rather than just one which is expected.

@sachendras
Copy link
Copy Markdown
Contributor

I have started a document offline. Lets close on that before we move forward with the Pull

* Perform a Longest Prefix Match (LPM) lookup on the inner IP header and forward the packet towards the destination.
* Ensure the packet arrives at the destination as `[Inner_IP_header][PAYLOAD]`.
* Support these operations potentially via sequential VRF lookups or a single pipeline operation if supported by the vendor.
* Performance caveats are acceptable as this is for probing traffic.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this statement, we don't want to give out the details on how Google is using this feature.

* Decap Aggregates: Configure DUT:Port3 with an aggregate IPv4 /28 and IPv6 /60 block address.
* Soft-Loop: Enable software loopback on DUT Port 3.
* Forwarding Rules:
** Configure dual decap policies on the DUT to facilitate the decapsulation of Header 1 and Header 2 (UDP 6080). The decap policies for Header 1 (IPv6) and Header 2 (IPv4 and IPv6) must target specified aggregates: for Header 2, utilize the IPv4 /28 and IPv6 /60 blocks assigned to DUT Port 3; for Header 1, use a /60 subnet of the destination address.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems the markdown needs to be fixed

| | Middle IP | IPV6-MID-SRC | DECAP-DST-INNER | 6080 | 32 | 60 |
| | Inner IP | IPV6-SRC-HOST | IPV6-DST-HOST | N/A | 20 | 50 |

### Traffic Generation:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Markdown needs correction

@sachendras sachendras self-requested a review March 9, 2026 19:00
Copy link
Copy Markdown
Contributor

@sachendras sachendras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have highlighted the sections that needs Markdown update. Please review your changes in the "Preview" Section.

@sachendras
Copy link
Copy Markdown
Contributor

/gcbrun

@ksgireesha ksgireesha requested a review from ram-mac March 20, 2026 14:09
* Decap Aggregates: Configure DUT:Port3 with an aggregate IPv4 /28 and IPv6 /60 block address.
* Soft-Loop: Enable software loopback on DUT Port 3.
* Forwarding Rules:
** Configure dual decap policies on the DUT to facilitate the decapsulation of Header 1 and Header 2 (UDP 6080). The decap policies for Header 1 (IPv6) and Header 2 (IPv4 and IPv6) must target specified aggregates: for Header 2, utilize the IPv4 /28 and IPv6 /60 blocks assigned to DUT Port 3; for Header 1, use a /60 subnet of the destination address.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mellowdrifter - I think the policy can be broken down into points for easy understanding. Seems too dense

@mellowdrifter mellowdrifter force-pushed the mellowdrifter-patch-1 branch 2 times, most recently from 59c8630 to 13359df Compare March 26, 2026 12:40
Signed-off-by: Darren O’Connor <mellowd@google.com>
@mellowdrifter mellowdrifter force-pushed the mellowdrifter-patch-1 branch from 13359df to b3cd1da Compare March 26, 2026 12:55
@mellowdrifter mellowdrifter requested review from a team as code owners March 26, 2026 12:55
@mellowdrifter mellowdrifter requested review from a team as code owners March 26, 2026 12:55
@mellowdrifter
Copy link
Copy Markdown
Author

Closing in favor of the new clean PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants