[FRR]Fixing route update on duplicate link up event in promiscuous mode #21805
+79
−0
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.
Why I did it
Fixing route update on duplicate link up event in promiscuous mode. When running tcpdump on interfaces which have BGP neighbors a duplicate link up event is received as the interface enters promiscuous mode. However these shouldn't trigger route updates. Due to the commit 58592be57783a3b24e7351af2a5afc61299768df route updates are published.
Work item tracking
How I did it
Reverted the commit that causes the issue and added as patch
How to verify it
Running tcpdump on bgp neighbor and verifying if there are no route updates.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)