Hi all,
I am currently working on testing a scenario of connection close using packetdrill.
For the sake of convenience, I am taking this state diagram as a reference [1].
In this case, the client is the packetdrill instance and the server is the TCP stack.
Client initiates connection close.
What I am trying to test is that if the LAST-ACK sent by client (client’s packet #2 in the diagram) gets lost, the server retransmits the FIN (server’s packet #1 in diagram) before 2*MSL of the client, in order to carry out proper connection close for the server.
The test script which I have made for this scenario is available here [2].
The tcpdump trace for the test is available here [3].
The tcpdump trace suggests that packetdrill (almost instantaneously) closes the connection by sending a RST, after the server sends a FIN. This in turn is not allowing to check for the appropriate behavior (timeout is not occurring).
Should packetdrill wait a bit and let server retransmit FIN before closing it all down by sending a RST?
Any suggestion will be greatly appreciated.
[1] - http://www.tcpipguide.com/free/diagrams/tcpclose.png
[2] - https://github.com/shivrai/TCP-IP-Regression-TestSuite/blob/master/close/close-last-ack-lost.pkt
[3] - https://github.com/shivrai/TCP-IP-Regression-TestSuite/tree/master/close#description
Thank you.
Regards,
Shivansh Rai
--
You received this message because you are subscribed to the Google Groups "packetdrill" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packetdrill+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.