CCNA lab 16 of 46
DHCP snooping and dynamic ARP inspection
A rogue DHCP server is handing out its own gateway and a laptop is about to poison everyone's ARP cache. Stop the first with DHCP snooping, fix the option 82 side effect, then use the snooping bindings for dynamic ARP inspection and watch a spoofed ARP get dropped.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 5,632 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 16 - DHCP snooping and dynamic ARP inspection
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
At Kingsmere Recruitment, staff complain that "the Internet is weird" in the mornings. Someone has connected a small router in the meeting room (ROGUE) whose DHCP server answers faster than the real one on R1 and hands out itself (10.16.10.66) as the default gateway: a perfect man-in-the-middle. And the hot-desk laptop (H1) belongs to a contractor who likes security tools. You'll harden the access switch S1 with DHCP snooping and dynamic ARP inspection.
| Device | Port on S1 | Address |
|---|---|---|
| R1 (real DHCP server and gateway) | Gi0/0 | 10.16.10.1/24, pool STAFF from .100 |
| PC1, PC2 | Gi0/1, Gi0/2 | DHCP |
| ROGUE (unauthorised) | Gi0/3 | 10.16.10.66, offers .200+ with gateway .66 |
| H1 (contractor laptop) | Gi1/0 | static 10.16.10.50/24, MAC 02:00:00:00:16:50 |
What you’ll practise
- Explain rogue DHCP and ARP spoofing attacks
- Configure DHCP snooping with trusted and untrusted ports and rate limits
- Recognise and fix the option 82 problem with an IOS DHCP server
- Read the DHCP snooping binding table
- Configure dynamic ARP inspection, an ARP ACL for a static host and validation checks
The tasks
- See the rogue DHCP server win
- Turn on DHCP snooping
- Fix the option 82 side effect
- Read the binding table
- Prepare the static host
- Turn on dynamic ARP inspection
- Launch the attack and watch it fail
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
Gi0/0to S1Gi0/0 - S1
Gi0/1to PC1eth0 - S1
Gi0/2to PC2eth0 - S1
Gi0/3to ROGUEGi0/0 - S1
Gi1/0to H1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| ROGUE | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| S1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNA 200-301 guided labs.Open
16 - DHCP snooping and dynamic ARP inspectionand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More CCNA labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.