16 hands-on IPv4 scenarios you build in your own Cisco Modeling Labs instance and grade against the answer key. Focused IPv4 configuration and troubleshooting practice for CCNA and CCNP.
Practice deterministic VLSM planning and interface addressing on two Cisco IOS routers. Starting from a single /24, allocate three right-sized IPv4 subnets (two LANs represented by loopbacks and one router-to-router WAN) and configure exact interface addresses and masks. No routing protocols or static routes are configured; verification focuses on directly connected reachability and show commands.
Advanced CCNP lab focused on diagnosing and correcting IPv4 interface addressing issues on Cisco IOS routers. The lab ships pre-broken with two independently failing faults that the learner must find and fix using show commands and directed pings. No routing protocols or static routes are used — verification is limited to directly-connected neighbor and gateway reachability.
Configure a Cisco IOS router to host two IPv4 /24 subnets on a single physical LAN interface using a secondary address. Verify directly-connected reachability only (no routing protocols, no static routes). This simulates a readdressing coexistence period where both old and new subnets must operate concurrently on the same segment.
Configure and verify dual-stack IPv4 and IPv6 addressing on Cisco IOS router interfaces. R1-R2 share a /30 IPv4 and /64 IPv6 point-to-point transit, while R1 provides a dual-stack user LAN gateway. No routing protocols or router static routes are permitted; verify only directly connected reachability.
Build confidence addressing IPv4 point-to-point WAN links on Cisco IOS using /30 and /31 masks. Two routers are connected by two parallel links: one classic /30 and one RFC 3021 /31. No routing protocols or static routes are configured — the goal is deterministic, correct interface addressing and verification of directly connected reachability. A small LAN off R1 with two hosts allows additional verification (host-to-gateway only).
Hands-on IPv4 subnetting and interface addressing on three IOS routers and one client. You will split a /24 into four equal /26s, assign the correct /26 mask to each link, and configure deterministic lowest-usable addressing on router interfaces. No routing protocols or static routes are used; verification is strictly directly-connected reachability.
Configure PAT on an edge router so only PC-A is translated using a standard ACL as the traffic selector. PC-B remains untranslated and fails to reach the ISP, illustrating that NAT occurs only for traffic explicitly matched by the ACL. Validate using host pings and IOS show commands, and interpret ACL hit counters and NAT tables.
Diagnose and repair an ACL + NAT policy on a small branch-to-DC topology. Implement PAT on the branch edge, correctly place an extended ACL to filter pre-NAT traffic, prove a permitted flow and a denied flow from the end host, and validate with show commands.
Deploy a numbered extended ACL on a router-on-a-stick topology to allow HTTP from a single approved client to a web server while denying all other TCP attempts to that server from the same user VLAN. Apply the ACL inbound near the source, verify with real client traffic, and troubleshoot using ACL hit counts and test flows.
Beginner CCNA lab focusing on IPv4 addressing and basic Layer 3 verification on a small branch network. You will assign IP addresses to router interfaces, confirm end-host default gateways, and verify connected reachability using host-based pings. You will also learn to read 'show ip interface brief' and 'show ip route' to confirm operational state before any routing beyond directly-connected networks is configured.
Archive preview only
Deploy and verify multiple IPv4 ACLs on a single router that terminates three distinct LANs (Client, Server, and Management). You will place an extended ACL inbound on the Client interface to allow only specific services to the Server and block access to Management, a standard ACL outbound on the Management interface to enforce destination-side protection by source, and a VTY access-class to restrict router SSH to the Management subnet only. Validate with end-host tests that permitted flows succeed while denied flows are provably blocked, and use ACL hit counts and logs to troubleshoot.
Dual-router Branch/HQ lab with a branch client and an HQ server. You will apply an extended IPv4 ACL inbound near the source on the Branch LAN to block specific traffic (TCP/80) while permitting others (ICMP), and a standard IPv4 ACL outbound near the destination on the HQ LAN to admit only the approved source. Validate from real hosts, confirm ACL hitcounts, and keep inter-site connectivity via static routes over a /30 transit.
Build a two-router, one-access-switch lab with a client and a server. Establish basic IP connectivity with static routing, then implement an extended IPv4 ACL inbound on the client-facing interface to permit SSH and HTTP to the server while denying Telnet and ICMP echo. Validate from the client and review ACL hit counters for proof.
Configure a default route on a branch edge router and a return static route on an upstream core router to enable full bidirectional connectivity between a stub branch LAN and a core server LAN. Verify the S* default route, gateway of last resort, and end-to-end reachability from real hosts. Troubleshoot missing default or return paths.
Design and implement a 3-router full-mesh with two edge LANs using static IPv4 routes only. Edges use primary defaults toward the core plus floating (higher AD) backup defaults; the core uses specific routes for the edge LANs. Validate bidirectional reachability, path choice, and failover behaviors from real hosts.
Deploy a compact two-site topology with a WAN core and two end hosts to practice IPv4 static host routes (/32) versus subnet routes (/24). You will configure a specific /32 host route to steer one destination host over the direct R1–R3 path while a broader /24 for the same remote LAN is sent via the R1–R2–R3 core. Validate with show commands and traceroute, then troubleshoot longest-prefix match and return-path issues.
Looking for something else? Browse the full lab archive or see today's daily lab.