TCP Three-Way Handshake Connection Establishment
These flashcards cover the TCP three-way handshake — the process establishing reliable connections between two hosts before data transfer begins. Critical for CompTIA Network+, CCNA, and networking courses, this mechanism trips up students who confuse SYN, SYN-ACK, and ACK sequence numbers or misunderstand TCP's stateful design. Each card reinforces exact flag sequences, port state transitions, and the role of ISN randomization, so you can answer exam questions confidently without second-guessing the order.
Interactive Deck
5 CardsWhy does TCP use three steps instead of two?
What happens if the SYN-ACK is never received by the client?
Master this topic effortlessly.
Study G helps you master any topic effortlessly using proven learning algorithms and smart review timing
Download Study GFrequently Asked Questions
What is the TCP three-way handshake?
The three-way handshake is the process TCP uses to establish a reliable connection before data transfer. The client sends a SYN, the server replies with SYN-ACK, and the client completes the exchange with an ACK. Only then do both sides consider the connection open.
What is the difference between TCP and UDP connection setup?
TCP uses a three-way handshake to establish a stateful, reliable connection before sending data. UDP has no handshake — it sends datagrams immediately with no guarantee of delivery or order.
- Use TCP for: web browsing, email, file transfers
- Use UDP for: video streaming, DNS lookups, online gaming
How does a SYN flood attack exploit the three-way handshake?
An attacker sends thousands of SYN packets with spoofed source IPs. The server allocates resources and replies with SYN-ACK but never receives the final ACK, filling its SYN backlog queue until it cannot accept legitimate connections. Mitigated using SYN cookies, which avoid allocating resources until the ACK arrives.
Why does TCP randomize the Initial Sequence Number?
Random ISNs prevent TCP sequence prediction attacks where an attacker could forge packets with a guessed sequence number to inject data or reset connections. RFC 6528 requires ISNs be cryptographically unpredictable.
