🌐 NETWORKING BOOTCAMP
HOW THE INTERNET WORKS
DAY 3
DNS · TCP · UDP · HTTP
How data travels across the internet
DAY 4
HTTPS · TLS · Ports
Keeping your data SAFE
DAY 5
DHCP · ARP · Routing · Firewall
Connect, communicate & stay safe
Client
Server
Router
DNS
Firewall
SCROLL TO EXPLORE ↓
DAY 3
TCP · UDP · HTTP · DNS
How data travels across the internet 🌍
01 / DNS — OSI Layer 7 (Application)
📁 Domain Name System
The Big Idea
- Computers talk using numbers (IP)
- Humans remember names, not numbers!
- DNS = the internet's phone book 📖
google.com → 142.250.80.46
Real-Life Analogy
- You want to call your friend "Ahmed"
- You don't remember his number...
- So you check your phone contacts!
- DNS does the same thing for websites
🔴 LIVE SIMULATION — DNS Resolution
You
Your Browser
query
Local Cache
Check memory first
miss →
DNS Resolver
Ask your ISP's server
asks
Root DNS
Who handles .com?
asks
Google DNS
Get the IP address!
google.com
⟹
???
💻 Try it yourself — Terminal Commands
$ nslookup google.com → Asks DNS: what is the IP of google.com?
$ nslookup facebook.com → Try another website!
$ ping google.com → Sends a test message to Google's server
$ nslookup 8.8.8.8 → Reverse lookup: who owns this IP?
💡 DNS happens EVERY time you visit a website — usually in less than 1 second!
02 / TCP — OSI Layer 4 (Transport)
🤝 Transmission Control Protocol
What is TCP?
- Like sending a certified letter
- Checks all data arrives safely ✅
- Sender → "Are you ready?"
- Receiver → "Yes, ready!"
- Use when: File download, Email, Web pages
The 3-Way Handshake
- SYN → "Hello, are you there?"
- SYN-ACK → "Yes! I'm here!"
- ACK → "Let's talk!"
- Connection is now ESTABLISHED ✅
🔴 LIVE SIMULATION — 3-Way Handshake
CLIENT
Your Browser
IDLE
Step 1
SYN
seq=0
SYN-ACK
seq=0, ack=1
Step 2
Step 3
ACK
ack=1
SERVER
facebook.com
LISTEN
03 / UDP — OSI Layer 4 (Transport)
⚡ User Datagram Protocol
What is UDP?
- Like shouting in a room!
- No "hello" or "are you ready"
- Just SEND the data... FAST!
- Some packets may get lost 📦❌
- Speed > Perfection
- Use for: Video calls, Games, Streaming
TCP vs UDP — Quick Compare
| Feature | 🤝 TCP | ⚡ UDP |
|---|---|---|
| Reliable? | ✅ Yes | ❌ No |
| Speed | Slower | 🚀 Faster |
| Order | Guaranteed | Not guaranteed |
| Handshake | 3-way | None |
| Use for | Files, Web | Video, Games |
🔴 LIVE SIMULATION — UDP Packet Stream
CLIENT → SERVER (no handshake, no confirmation)
🧑💻
🖥️
04 / HTTP — OSI Layer 7 (Application)
🌐 HyperText Transfer Protocol
What is HTTP?
- Language browsers & servers use
- You ask → Server answers
- Like ordering at a restaurant! 🍽️
- GET = "Give me something"
- POST = "Take this from me"
Request & Response Flow
→ REQUEST
GET /index.html HTTP/1.1
Host: google.com← RESPONSE
HTTP/1.1 200 OK
<html>...page...</html>🔴 LIVE SIMULATION — HTTP Status Codes
Click a button to send a request →
📦
—
Waiting...
✅ 2xx Success
⚠️ 3xx Redirect
🔍 4xx Client Error
💥 5xx Server Error
💡 HTTP Status Codes: 200 OK · 404 Not Found · 500 Server Error
DAY 4
HTTPS · TLS · Ports
Keeping your data SAFE on the internet 🔐
05 / HTTPS — OSI Layer 7 (Application)
🔒 HTTPS — Secure Web Browsing
HTTP
Port 80
- Data is PLAIN TEXT
- Anyone can read it! 😱
- No padlock in browser
- URL starts with http://
- NEVER enter passwords!
password=ahmed123
cardno=1234-5678
👁️ INTERCEPTED!
VS
HTTPS
Port 443
- Data is ENCRYPTED
- Nobody can read it! ✅
- 🔒 Padlock in browser
- URL starts with https://
- Safe for passwords & cards
x7k#@!9mP2qL...
Yr3nQ!kW9...$
🔒 ENCRYPTED
💡 Always check for 🔒 before entering passwords! HTTPS = HTTP + TLS encryption. Always use HTTPS on public WiFi! 📶
🏖️ Group Discussion: You're at a coffee shop using their WiFi. You need to log into your bank. Is it safe? What should you check? Why?
06 / TLS — OSI Layer 4-5 (Transport/Session)
🔐 TLS — How Encryption Works
💡 Think of TLS like putting your letter in a locked box — only the receiver has the key!
🔴 LIVE SIMULATION — TLS Handshake
Your Browser
Not connected
Step 1
ClientHello
Browser says hi to server — lists supported cipher suites & TLS version
Step 2
Certificate
Server proves who it is — sends SSL certificate signed by trusted CA (Certificate Authority)
Step 3
Key Exchange
Create a secret session key together — using asymmetric cryptography (RSA/ECDHE)
Step 4
Encrypted!
All data is now locked — HTTPS tunnel established! 🎉
🔓
Server (facebook.com)
Listening...
07 / PORTS — OSI Layer 4 (Transport)
🚪 Ports — The Doors of Your Server
What is a Port?
- Think of a building with many doors
- IP = the building address
- Port = which door to knock on
- Each service uses a different door
- Range: 0 to 65,535 doors!
🔴 INTERACTIVE — Click a Port Door
🖥️ SERVER — 192.168.1.100
:80HTTPOPEN
:443HTTPS 🔒OPEN
:22SSHOPEN
:53DNSOPEN
:25SMTPOPEN
:23Telnet ⚠️🔥 DANGER
:3306MySQL ❌BLOCKED
👆 Click any door to learn about the port
💻 Try it yourself
$ curl -I http://google.com → See HTTP headers
$ curl -I https://google.com → See HTTPS headers
$ nmap -p 80,443 google.com → Check open ports
DAY 5
DHCP · ARP · Routing · Firewall
How devices connect, communicate & stay safe 🛡️
08 / DHCP — OSI Layer 7 (Application)
📲 DHCP — Getting Your IP Automatically
What is DHCP?
- DHCP = Dynamic Host Configuration Protocol
- You join a WiFi network → need an IP
- DHCP gives you one automatically!
- Like hotel reception: "Here's your room number" 🏨
- Also gives: Gateway, DNS server, Subnet mask
🔴 LIVE SIMULATION — DORA Process
Your Device
No IP yet...
D
DISCOVER
"Anyone have an IP for me?"
Broadcast to 255.255.255.255
Broadcast to 255.255.255.255
📡
O
OFFER
"Yes! Here, take 192.168.1.5"
DHCP Server responds
DHCP Server responds
💌
R
REQUEST
"OK, I'll take that IP!"
Formal request sent
Formal request sent
📨
A
ACKNOWLEDGE
"Great! It's yours for 24h"
Lease confirmed ✅
Lease confirmed ✅
✅
DHCP Server
192.168.1.1
IP: —
Gateway: 192.168.1.1
DNS: 8.8.8.8
Lease: 24 hours
💻 Try it yourself
$ ipconfig → See your IP address (DHCP assigned)
$ ifconfig → Linux/Mac equivalent
09 / ARP — OSI Layer 2 (Data Link)
🗣️ ARP — Finding Devices by IP
What is ARP?
- ARP = Address Resolution Protocol
- You have an IP → need the MAC address
- MAC = physical hardware address (permanent)
- ARP shouts: "Who has 192.168.1.5?"
- Device replies: "That's me! Here's my MAC"
- Like shouting a name in a room 📣
IP vs MAC Address
| Feature | IP Address | MAC Address |
|---|---|---|
| What? | Logical address | Physical address |
| Example | 192.168.1.5 | A1:B2:C3:D4:E5:F6 |
| Changes? | Yes (DHCP) | No (permanent) |
| OSI Layer | Layer 3 | Layer 2 |
🔴 LIVE SIMULATION — ARP Broadcast
Your PC
192.168.1.10
192.168.1.2AA:11:22...?
192.168.1.1AA:BB:CC...?
ROUTER
192.168.1.20BB:CC:DD...?
192.168.1.30CC:DD:EE...?
Click "Broadcast ARP" to ask "WHO HAS 192.168.1.1?"
💻 Try it yourself
$ arp -a → See your ARP table (real MAC addresses!)
10 / ROUTING — OSI Layer 3 (Network)
🗺️ Routing — How Data Crosses the Internet
What is Routing?
- Data jumps between many routers
- Router = a smart traffic director
- Finds the BEST path to destination
- Like GPS for your data packets! 🛰️
- Each router knows nearby routes only
🔴 LIVE SIMULATION — Packet Journey: Cairo → USA
Your PC
Cairo, Egypt
10.0.0.1
Home Router
Local ISP
192.168.1.1
ISP Router
International
203.0.113.5
Core Router
Transatlantic
8.8.8.1
Google Server
USA
142.250.80.46
📦
Click "Trace Route" to watch the packet travel...
HOP: —
LATENCY: —
LOCATION: —
💻 Try it yourself
$ traceroute google.com → See each router hop in real-time!
$ tracert google.com → Windows version
11 / FIREWALL — OSI Layer 3-4 (Network/Transport)
🛡️ Firewall — Your Network Security Guard
What is a Firewall?
- Guards all traffic entering/leaving
- Like a security guard at a building
- Has a list of ALLOW / DENY rules
- Filters by IP address or Port number
- Blocks suspicious or unknown traffic
📋 Firewall Rules Example
✅ ALLOW Port 443 (HTTPS) from anywhere
✅ ALLOW Port 80 (HTTP) from anywhere
✅ ALLOW Port 22 (SSH) from admin IP only
❌ DENY Port 23 (Telnet) — insecure!
❌ DENY All other ports — blocked
🔴 LIVE SIMULATION — Traffic Through Firewall
INCOMING TRAFFIC
🛡️
FIREWALL
Checking rules...
✅ ALLOWED IN
❌ BLOCKED
💻 Try it yourself
$ netstat -an → See open ports on your machine
⚡ FULL SCENARIO
What Happens When You Open facebook.com?
Every single visit goes through ALL these steps — in milliseconds.
1
DNSLayer 7
DNS Lookup
Your PC asks DNS: 'What's the IP for facebook.com?'
DNS replies:
DNS replies:
157.240.221.352
TCPLayer 4
TCP Handshake
Your browser does 3-way handshake with Facebook's server
SYN → SYN-ACK → ACK ✅
SYN → SYN-ACK → ACK ✅
3
TLSLayer 4-5
TLS Encryption
Browser & server agree on encryption keys
All traffic is now locked with HTTPS 🔒
All traffic is now locked with HTTPS 🔒
4
HTTPLayer 7
HTTP Request
Browser sends:
Host: facebook.com (Port 443) 🚪
GET / HTTP/1.1Host: facebook.com (Port 443) 🚪
5
ROUTINGLayer 3
Server Response
Facebook sends back:
(Via Routing through many routers!) 🗺️
200 OK + HTML page(Via Routing through many routers!) 🗺️
6
✅ DONEApp
Display!
Your browser reads the HTML and shows you the Facebook page! 🎉
🧱 OSI Layer Reference
7ApplicationHTTP, HTTPS, DNS, DHCP, FTP, SSH
6PresentationTLS/SSL, Encryption
5SessionTLS handshake, Session management
4TransportTCP, UDP, Ports
3NetworkIP, Routing, ICMP
2Data LinkARP, MAC addresses, Ethernet
1PhysicalCables, WiFi signals, Hardware
🏆
YOU MADE IT!
Day 3DNS · TCP · UDP · HTTP
Day 4HTTPS · TLS · Ports
Day 5DHCP · ARP · Routing · Firewall
🔑 Key Idea: The internet is just devices
talking to each other — with rules!