[vs-test]: not forward routes with no-export community #1774
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Sihui Han [email protected]
- What I did
Add vs test to verify that the device doesn't forward routes with no-export community.
- How I did it
Establish two exabgp neighbors, and let one neighbor announce two routes, 1.1.1.1/32 (with no-export community) and 2.2.2.2/32 (without no-export community). The DUT should only announce 2.2.2.2/32 to the other neighbor
- How to verify it
Run the test.
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)