-
Notifications
You must be signed in to change notification settings - Fork 927
[dhcp_relay] change ptfutils to tcpdump for better result #21706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Blueve
merged 1 commit into
sonic-net:master
from
Xichen96:dev/xichenlin/fix-dhcp-stress
Dec 18, 2025
Merged
[dhcp_relay] change ptfutils to tcpdump for better result #21706
Blueve
merged 1 commit into
sonic-net:master
from
Xichen96:dev/xichenlin/fix-dhcp-stress
Dec 18, 2025
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
Signed-off-by: Xichen Lin <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Blueve
approved these changes
Dec 16, 2025
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
approved these changes
Dec 18, 2025
selldinesh
pushed a commit
to selldinesh/sonic-mgmt
that referenced
this pull request
Dec 18, 2025
…21706) On some testbeds, we have observed around 25% packet loss with dhcp relay stress test. We have confirmed that packets were sent out of dut intf fine, but packets were dropped at 1. before reaching server and 2. after reaching server and during ptf packet capture. For large packet amounts ptfutils tends to drop packets and the amount goes up as packet amount increase. By switching using tcpdump directly, 25% packet loss can be reduced to around 10%. What is the motivation for this PR? This pr reduces packet loss during ptf packet capture and makes result better How did you do it? Replace ptfutils packet capture with tcpdump capture How did you verify/test it? Run test Signed-off-by: Xichen Lin <[email protected]> Signed-off-by: selldinesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…21706) On some testbeds, we have observed around 25% packet loss with dhcp relay stress test. We have confirmed that packets were sent out of dut intf fine, but packets were dropped at 1. before reaching server and 2. after reaching server and during ptf packet capture. For large packet amounts ptfutils tends to drop packets and the amount goes up as packet amount increase. By switching using tcpdump directly, 25% packet loss can be reduced to around 10%. What is the motivation for this PR? This pr reduces packet loss during ptf packet capture and makes result better How did you do it? Replace ptfutils packet capture with tcpdump capture How did you verify/test it? Run test Signed-off-by: Xichen Lin <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
vrajeshe
pushed a commit
to Akshath-17/sonic-mgmt
that referenced
this pull request
Jan 4, 2026
…21706) On some testbeds, we have observed around 25% packet loss with dhcp relay stress test. We have confirmed that packets were sent out of dut intf fine, but packets were dropped at 1. before reaching server and 2. after reaching server and during ptf packet capture. For large packet amounts ptfutils tends to drop packets and the amount goes up as packet amount increase. By switching using tcpdump directly, 25% packet loss can be reduced to around 10%. What is the motivation for this PR? This pr reduces packet loss during ptf packet capture and makes result better How did you do it? Replace ptfutils packet capture with tcpdump capture How did you verify/test it? Run test Signed-off-by: Xichen Lin <[email protected]> Signed-off-by: Venkata Gouri Rajesh Etla <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
On some testbeds, we have observed around 25% packet loss with dhcp relay stress test. We have confirmed that packets were sent out of dut intf fine, but packets were dropped at 1. before reaching server and 2. after reaching server and during ptf packet capture. For large packet amounts ptfutils tends to drop packets and the amount goes up as packet amount increase. By switching using tcpdump directly, 25% packet loss can be reduced to around 10%.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
This pr reduces packet loss during ptf packet capture and makes result better
How did you do it?
Replace ptfutils packet capture with tcpdump capture
How did you verify/test it?
Run test
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation