Network documentation that stays current: practical guides, compliance diagrams, honest comparisons, and help for students and homelabs.
Three homelab network diagrams with their VLANs, addresses and hardware: a segmented home network, a self-hosting lab with a DMZ, and a two-site routing lab.
Run one nmap command, drop the XML file into ApexDiagram, and get every live host as a device with its address, vendor and a guessed type. Then add the cables.
Pull Meraki devices and clients from the Dashboard API, import them into ApexDiagram, and get an editable diagram with every MX, MS and MR and their clients.
A physical diagram shows where things are and how they are cabled. A logical one shows how traffic moves. What goes on each, and why you need both.
NetBox holds the facts but does not draw them. How to turn NetBox devices, cables and prefixes into physical, network and data views that stay in step.
The same small-office network documented step by step in Visio, about two hours, and in ApexDiagram, about fifteen minutes.
Requirements 1.2.3 and 1.2.4 ask for a current network diagram and a data-flow diagram. Tag the cardholder data environment once and let the diagram work out the boundary.
Six things that go wrong with network diagrams drawn in Visio, Lucidchart or draw.io, and what a diagram that is a record instead of a picture does about each.
Follow along with the RSS feed.