TCP-FIN, TCP-FIN-ACK Messages handling in blaster. - Githubissues

rtbrick / bngblaster

The BNG Blaster is an open-source network tester for access and routing protocols.

https://rtbrick.github.io/bngblaster/

BSD 3-Clause "New" or "Revised" License

202 stars 32 forks source link

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

Open DharmendraShetty opened 5 months ago

DharmendraShetty commented 5 months ago

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