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.

FTP

Web & applicationIntermediate

Separate the control channel from a passive data connection.

SIMULATION01 / 04
Loading topology…
0.0s / 4.2s
01
STEP 1 OF 4Server / peer → Client

220 Service ready

The control connection carries numeric replies and commands.

#TIMESOURCE → DESTINATIONMESSAGE
0.000198.51.100.20192.0.2.10220 Service ready
1.400192.0.2.10198.51.100.20USER + PASS
2.800192.0.2.10198.51.100.20PASV + RETR
4.200198.51.100.20192.0.2.10150 → data → 226

Separate the control channel from a passive data connection.

Explain 220 Service ready and distinguish it from 150 → data → 226.

Prerequisites: Ethernet

Ready to test your understanding?

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

Learn from the sourceRFC 959Protocol guide

FTP: protocol guide / panduan protokol

Separate the control channel from a passive data connection.

Pisahkan kanal kontrol dari koneksi data pasif.

Communication walkthrough / Alur komunikasi

  1. 220 Service ready

    The control connection carries numeric replies and commands.

    Koneksi kontrol membawa balasan numerik dan perintah.

  2. USER + PASS

    A teaching login is condensed here; classic FTP sends credentials without transport encryption.

    Login pembelajaran diringkas di sini; FTP klasik mengirim kredensial tanpa enkripsi transport.

  3. PASV + RETR

    After a passive endpoint is negotiated, the client opens a separate data connection.

    Setelah endpoint pasif dinegosiasikan, klien membuka koneksi data terpisah.

  4. 150 → data → 226

    The data connection transfers the file; the control channel reports completion.

    Koneksi data mentransfer file; kanal kontrol melaporkan selesai.

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 959 ↗