About this tool
TCP sends a stream of bytes inside segments and uses acknowledgments to track delivery. This simulator separates that story into handshake, data transfer, congestion control, teardown, retransmission and reset scenarios. It helps students see why flags, sequence numbers and ACK values change together. These are fixed teaching scenes, not traffic captured from your device.
How it works
- Select the TCP scenario you want to study.
- Play the exchange and follow the segment direction.
- Inspect flags, sequence values and acknowledgments.
- Compare the normal flow with retransmission or reset.
Worked example
A sender transmits 500 bytes starting at sequence 2001. The receiver can acknowledge 2501, the next expected byte. If that segment is lost, retransmitting the same bytes uses the same sequence range. A repeated packet does not automatically mean those bytes were delivered twice to the application.
Common mistakes
TCP sequence numbers count bytes, not packets. An ACK does not prove the application has processed the data. Avoid treating a single simplified congestion scene as the exact behavior of every operating system or congestion-control algorithm.
FAQ
Does TCP preserve message boundaries?
No. TCP delivers an ordered byte stream. Applications need their own framing, such as a length field or delimiter, to identify individual messages within that stream.