DHCP Snooping: Trust Boundary Misconfiguration
Three switches run DHCP snooping. PC1 gets a lease, PC2 never does. Trace the trust boundary to the port dropping the server's replies.
What you'll practise
- Confirm DHCP snooping is enabled consistently across a small switched network
- Read show ip dhcp snooping and identify a switch's trusted interfaces
- Use show ip dhcp server statistics to prove the server is answering
- Recognize a DHCP snooping trust boundary problem from those two outputs together
- Apply ip dhcp snooping trust on the correct uplink and verify the fix
Set it up
- 1
Have the node image ready
Images are not included. The file expects your own licensed copy of:
i86bi_Linux-L2-Adventerprisek9-ms.SSA.high_iron_20190423.bin
If your copy has a different name, open each node's Edit dialog after importing and pick your image from the list.
- 2
Copy it to the server and fix permissions
Replace
<your-server>with the IP address or hostname of your EVE-NG or PNETLab server.$ scp dhcp-snooping-lab.unl root@<your-server>:/opt/unetlab/labs/ # then, logged in to the server: $ /opt/unetlab/wrappers/unl_wrapper -a fixpermissions - 3
Open it and start the nodes
The canvas notes list the objectives, and the workbook walks through the fix.
Free to use and share under CC BY 4.0. Please credit LabFabric with a link to this page.