Add README for Double GUE Decapsulation#5081
Conversation
Summary of ChangesHello @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
Changelog
Using Gemini Code AssistThe 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
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 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
|
Pull Request Functional Test Report for #5081 / 13359dfVirtual Devices
Hardware Devices
|
There was a problem hiding this comment.
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.
Pull Request Test Coverage Report for Build 22145898347Details
💛 - Coveralls |
fdd4bda to
c25cb5b
Compare
| | 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 | |
There was a problem hiding this comment.
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.
|
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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: |
There was a problem hiding this comment.
Markdown needs correction
sachendras
left a comment
There was a problem hiding this comment.
I have highlighted the sections that needs Markdown update. Please review your changes in the "Preview" Section.
|
/gcbrun |
| * 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. |
There was a problem hiding this comment.
@mellowdrifter - I think the policy can be broken down into points for easy understanding. Seems too dense
59c8630 to
13359df
Compare
Signed-off-by: Darren O’Connor <mellowd@google.com>
13359df to
b3cd1da
Compare
|
Closing in favor of the new clean PR. |
No description provided.