Network+ lab 21 of 27
Switch security: stopping rogue DHCP and ARP spoofing
Attack a small office LAN from a Linux host, then defend it. A rogue DHCP server hijacks a client's gateway until DHCP snooping stops it, ARP spoofing is blocked by dynamic ARP inspection, MAC spoofing trips port security, and user ports stop negotiating trunks.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 3,328 MB in total. That fits the free demo too.
In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 21 - Switch security - stopping rogue DHCP and ARP spoofing
- Level
- Advanced
- Time
- About 70 minutes
- Nodes need
- 5 vCPU, 3,328 MB
- Smallest plan
- Lite
The scenario
A visitor at Harbour Logistics plugged a laptop into the hot desk (SW1 Gi0/3). Nothing stops it from pretending to be the DHCP server or the default gateway. You'll play both sides: first ROGUE attacks the LAN, then you harden SW1 so the same attacks fail, with evidence for each.
| Device | Port | Address | Role |
|---|---|---|---|
| R1 | SW1 Gi0/0 | 10.10.10.1/24 | gateway and legitimate DHCP server |
| H1 | SW1 Gi0/1 | DHCP | staff Linux PC (the victim) |
| PC1 | SW1 Gi0/2 | DHCP | staff PC |
| ROGUE | SW1 Gi0/3 | 10.10.10.66/24 | attacker's laptop |
| (internet) | R1 Loopback0 | 203.0.113.1 | test target |
Only do this in a lab. Running these attacks on a network you don't own is illegal in most countries.
What you’ll practise
- Explain rogue DHCP, ARP spoofing/poisoning, MAC flooding and VLAN hopping attacks
- Configure DHCP snooping with trusted ports, and fix the option 82 side effect
- Configure dynamic ARP inspection based on the snooping bindings
- Configure port security with a maximum, sticky learning and a violation mode
- Harden access ports against trunk negotiation
- Read the evidence: bindings, drop counters, violations and logs
The tasks
- Prepare the attacker
- Attack 1, a rogue DHCP server
- Defend with DHCP snooping
- Attack 2, ARP spoofing, and the defence
- Attack 3, MAC spoofing, and port security
- Stop VLAN hopping
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 SW1Gi0/0 - SW1
Gi0/1to H1eth0 - SW1
Gi0/2to PC1eth0 - SW1
Gi0/3to ROGUEeth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| SW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| ROGUE | 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
CompTIA Network Plus N10-009 guided labs.Open
21 - Switch security - stopping rogue DHCP and ARP spoofingand 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 Network+ labs
Related labs in other courses
CloudLabBox is independent of CompTIA, Cisco and Netgate. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.