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.

SOCKS5

Security & VPNAdvanced

Negotiate a proxy method before opening a remote connection.

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

Method offer

The client lists supported authentication methods.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20Method offer
1.400198.51.100.20192.0.2.10Method selection
2.800192.0.2.10198.51.100.20CONNECT request
4.200198.51.100.20192.0.2.10Success reply

Negotiate a proxy method before opening a remote connection.

Explain Method offer and distinguish it from Success reply.

Prerequisites: Ethernet

Ready to test your understanding?

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

Learn from the sourceRFC 1928Protocol guide

SOCKS5: protocol guide / panduan protokol

Negotiate a proxy method before opening a remote connection.

Negosiasikan metode proxy sebelum membuka koneksi jarak jauh.

Communication walkthrough / Alur komunikasi

  1. Method offer

    The client lists supported authentication methods.

    Klien mencantumkan metode autentikasi yang didukung.

  2. Method selection

    The server selects a mutually supported method.

    Server memilih metode yang sama-sama didukung.

  3. CONNECT request

    A domain-name address asks the proxy to connect to a remote service.

    Alamat domain meminta proxy menghubungkan ke layanan jarak jauh.

  4. Success reply

    The proxy returns its bound endpoint; SOCKS alone does not encrypt relayed traffic.

    Proxy mengirim endpoint bound; SOCKS sendiri tidak mengenkripsi lalu lintas relay.

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