About this tool
TCP is a conversation with rules for opening, delivering bytes and closing. This animator connects packet flags to endpoint state changes, so the handshake becomes more than three names to memorise. Beginners can follow the normal connection, then explore the displayed FIN, RST and packet-loss actions. Sequence and acknowledgment values show how each endpoint tracks progress.
How it works
- Open the animator and follow its connection setup.
- Watch SYN, SYN-ACK and ACK alongside endpoint states.
- Compare sequence numbers with the next expected acknowledgment.
- Use the available loss or close actions to inspect a different outcome.
Worked example
If the client starts at sequence 1000, its SYN is acknowledged with 1001. A server SYN at 5000 is acknowledged with 5001. If the client then sends 100 data bytes starting at 1001, the receiver expects byte 1101 and can send ACK 1101.
Common mistakes
An ACK number normally identifies the next byte expected, not the last byte received. SYN and FIN each consume one sequence number. A reset is not the same as an orderly FIN-based close.
FAQ
Do these actions affect my real connections?
No. This is a browser teaching model, not a live TCP stack. Real timing, retransmission and application behavior depend on the endpoints and network.