Skip to content
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

TCP-FIN, TCP-FIN-ACK Messages handling in blaster. #246

Open
DharmendraShetty opened this issue Apr 1, 2024 · 0 comments
Open

TCP-FIN, TCP-FIN-ACK Messages handling in blaster. #246

DharmendraShetty opened this issue Apr 1, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@DharmendraShetty
Copy link

Problem Description:

TCP-FIN, TCP-FIN-ACK Messages handling in blaster is not in the expected sequence.

Solution:

If user triggers "stop tcp stream/flow"

  • traffic stream should be stopped
  • tcp-fin should be sent by end-A(blaster) to end-B(blaster)
  • on receiving tcp-fin, tcp-fin-ack should be sent by end-B(blaster) to end-A(blaster)
  • on receving tcp-fin-ack, tcp-fin-ack should be sent by end-A(blaster) to end-B(blaster)

Expectation:

It helps to test TCP Flows ageing in our CGNAT test coverage with graciously stopping TCP Flows.

Thanks,
Dharmendra

@DharmendraShetty DharmendraShetty added the enhancement New feature or request label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants