CCNA v2.0, section 1.0, lab 3, in slides: design VLSM subnets for three LANs and two links from 10.10.0.0/24, assign every port and host its address, and classify every address as public or private; build the three-site network in Packet Tracer with its routes given ready-made, check it from the hosts and from your own computer with ipconfig, ip addr, ifconfig, ping and traceroute; then make six addressing faults and find each one.
The slides
The lab is twenty-one slides in four parts, after an introduction, one step each.
- Introduction: what the lab does, and what it needs.
- 1. Designing the addresses: each subnet sized for its hosts, the subnets placed in
10.10.0.0/24 largest first, the answer to check against, the address plan, and every address classified as public or private. - 2. Building the network: four routers, three switches and six hosts placed and cabled, the routers' ports addressed, the provider's configuration and the routes pasted from the repository, the hosts addressed, and the routers checked.
- 3. Checking from the hosts:
ipconfig /all, ping, tracert and nslookup on the Packet Tracer PCs, then your own computer's settings and a traceroute. - 4. Breaking the addressing: a wrong mask, a wrong gateway, overlapping subnets, a network and a broadcast address given to a port and a host, a duplicate address, and a private address expected to reach the internet without NAT; then a table comparing the six.
The buttons on the left and right edges move between slides. So do the arrow keys and a swipe.
The files
- The network it starts from: a new file; the network is built in part 2.
- The files it uses:
ISP.txt, the provider's configuration, and the routes in R1.txt, R2.txt and R3.txt, in the
ccna repository, with each device's configuration as plain text. - The network it builds:
lab3.pkt; the fault round starts from it. - The lesson:
IPv4 Addressing and Subnetting explains every step.
Sources
- Private addresses:
RFC 1918.
- The stand-in public addresses:
203.0.113.0/24 and 198.51.100.0/24 are reserved for documentation by
RFC 5737.