FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

TCP

NetworkingBeginner

Establish a reliable byte stream with the three-way handshake.

SIMULATION01 / 05
Loading topology…
0.0s / 5.6s
01
STEP 1 OF 5Client → Server / peer

SYN

The client proposes initial sequence 1000. SYN consumes one sequence number.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20SYN
1.400198.51.100.20192.0.2.10SYN, ACK
2.800192.0.2.10198.51.100.20ACK
4.200192.0.2.10198.51.100.20Application data
5.600198.51.100.20192.0.2.10Cumulative ACK

Establish a reliable byte stream with the three-way handshake.

Explain SYN and distinguish it from Cumulative ACK.

Prerequisites: IPv4

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 9293Protocol guide

TCP: protocol guide / panduan protokol

Establish a reliable byte stream with the three-way handshake.

Bangun aliran byte andal melalui handshake tiga arah.

Communication walkthrough / Alur komunikasi

  1. SYN

    The client proposes initial sequence 1000. SYN consumes one sequence number.

    Klien mengusulkan sequence awal 1000. SYN memakai satu nomor sequence.

  2. SYN, ACK

    The server acknowledges 1001 and proposes its own sequence 5000.

    Server mengakui 1001 dan mengusulkan sequence sendiri, 5000.

  3. ACK

    The client acknowledges 5001. Both endpoints can now send application bytes.

    Klien mengakui 5001. Kedua endpoint kini dapat mengirim byte aplikasi.

  4. Application data

    Five bytes start at 1001; the next expected sequence becomes 1006.

    Lima byte dimulai pada 1001; sequence berikutnya adalah 1006.

  5. Cumulative ACK

    The receiver confirms all bytes before 1006, not each individual packet.

    Penerima mengonfirmasi semua byte sebelum 1006, bukan setiap paket.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 9293 ↗