Fundamentals · browser room
TCP 3-Way Handshake
Objective
See SYN → SYN-ACK → ACK open a reliable lab session.
Cyber Flow Explorer · 3 steps · Network / Sequence / Packet / Code.
Answer panel
Challenge workspace
Complete the room tasks, then submit here to mark the room done.
Teaching simulation · not live capture
Lab hosts only. Never flood systems outside written scope.
Real world · Every HTTPS page load starts with a TCP handshake to port 443 before TLS or HTTP can run.
Attack · Attackers may SYN-flood or spoof RSTs — outside this module’s scope; focus on the happy path first.
Defense · Stateful firewalls track handshake state; incomplete handshakes are rate-limited.
- Control · SYN cookies / connection rate limits on public listeners
- Control · Allow only expected ports (80/443) from untrusted zones
- Control · Monitor half-open connection spikes
1. SYN
Client
192.168.1.10:52344seq=1000 ack=—
Server
10.0.0.5:80seq=1000 ack=—
- #1 client → server SYN seq=1000 ack=—
Space · ← → · R restart
Hint
Client speaks first; server answers with SYN+ACK.
Why this is correct
SYN → SYN-ACK → ACK before application data. Sequence numbers are simplified for learning.