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.

IPsec

Security & VPNAdvanced

Negotiate security associations before protected IP traffic.

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

IKE_SA_INIT request

IKEv2 negotiates algorithms, exchanges Diffie-Hellman data and a nonce.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20IKE_SA_INIT request
1.400198.51.100.20192.0.2.10IKE_SA_INIT response
2.800192.0.2.10198.51.100.20IKE_AUTH exchange
4.200198.51.100.20192.0.2.10ESP tunnel packet

Negotiate security associations before protected IP traffic.

Explain IKE_SA_INIT request and distinguish it from ESP tunnel packet.

Prerequisites: Ethernet

Ready to test your understanding?

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

Learn from the sourceRFC 4301Protocol guide

IPsec: protocol guide / panduan protokol

Negotiate security associations before protected IP traffic.

Negosiasikan security association sebelum lalu lintas IP terlindungi.

Communication walkthrough / Alur komunikasi

  1. IKE_SA_INIT request

    IKEv2 negotiates algorithms, exchanges Diffie-Hellman data and a nonce.

    IKEv2 menegosiasikan algoritma, data Diffie-Hellman, dan nonce.

  2. IKE_SA_INIT response

    The responder contributes its nonce and key exchange data.

    Responder menyumbang nonce dan data pertukaran kunci.

  3. IKE_AUTH exchange

    Protected authentication establishes identities and a first Child SA; reply is condensed.

    Autentikasi terlindungi membentuk identitas dan Child SA pertama; balasan diringkas.

  4. ESP tunnel packet

    ESP protects the inner IP packet in tunnel mode.

    ESP melindungi paket IP dalam pada mode tunnel.

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