Update iptables to block BGP (TCP 179) traffic on eth0 - 202505 #19351
+2
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…est_cacl_application for PR test
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
11 tasks
ZhaohuiS
approved these changes
Jul 3, 2025
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of PR
Summary: Original PR: #18834
This PR updates the iptables and ip6tables rules to block incoming BGP (TCP port 179) traffic on the
eth0interface. This change ensures that BGP sessions are only allowed on non-management interfaces.Fixes: N/A
Type of change
Back port request
Approach
What is the motivation for this PR?
To support test updates in this PR: sonic-host-services#197.
Additionally, it ensures BGP port 179 is not exposed on the management interface (
eth0).How did you do it?
How did you verify/test it?
On t0-64 testbed
Any platform specific information?
None
Supported testbed topology if it's a new test case?
N/A
Documentation
No new documentation required.