β Progress Tracker
Week 1
Network Basics & PDUs
β
Network Representation
2.2.4
β
TCP/IP & OSI Model
2.4.8
β
Topology & Small Network
2.6.1
β
Viewing Protocol Data Units
2.6.2
β
5 / 5 Complete
Skills Integration: Examining Packets
2.7.1 β 100%
Week 2
Application Layer β DNS & HTTP
β
Client-Server Interaction
3.2.3
β
Network Representation (DNS/HTTP)
3.3.2
β
3 / 3 Complete
Skills Integration: Hosts & Services
3.5.1 β 100%
Week 3
Transport Layer β TCP & UDP
β
UDP and TCP Port Numbers
4.1.6
β
TCP Session Establishment & Termination
4.2.5
β
UDP Operation
4.4.4
β
App & Transport Layer Protocols
4.5.3
β
5 / 5 Complete
Skills Integration: App & Transport
4.6.1 β 100%
Week 4
Network Layer & Routing
β
IP Packet Simulation
5.2.2
β
Packet Tracing Across Networks
5.3.4
β
Dynamic Routing Protocol Updates
5.4.3
β
Examining a Device's Gateway
5.5.1
β
Examining a Route
5.5.2
β
6 / 6 Complete
Skills Integration: Routing IP Packets
5.6.1 β 100%
π Concept Notes
ARP β Address Resolution Protocol
How IP addresses are mapped to MAC addresses, and why the first ping fails.
TCP Three-Way Handshake
SYN, SYN-ACK, ACK β how TCP establishes and terminates connections.
OSI vs TCP/IP Model
Layer-by-layer breakdown and how encapsulation works top-down.
DNS & HTTP
How a browser resolves a URL through DNS before making an HTTP request.
IP Routing
Routing tables, static vs dynamic routing, RIP, and common failure points.
π¬ Skills Integration Highlights
2.7.1 β ICMP Packet Examination
- PC sends ARP request to learn the gateway's MAC address.
- After ARP resolution, ICMP echo request is sent.
- Server replies with ICMP echo reply.
Encapsulation: ICMP β IP packet β Ethernet frame
3.5.1 β DNS + HTTP Workflow
- Browser sends DNS query to resolve hostname to IP.
- TCP connection established with server on port 80.
- HTTP GET request sent; server responds with the page.
DNS (UDP) for name resolution Β· HTTP (TCP) for content delivery
5.6.1 β Routing IP Packets
- Configured router interface with IP address.
- Added static route via GUI.
- Examined routing table and traced packet delivery.
Failure points: wrong interface config, missing routes, unreachable gateway