Try netviz in your browser

Each diagram below is one netviz render -f html run over the inventory of the same name in examples/. They are self-contained files — the same ones the command writes — so everything works offline: pick a layer from the switcher, filter by VLAN or namespace, hover or focus a node to read its interfaces, addresses, VLANs and cabling.

To draw your own the same way: netviz -i my-network render -f html -o network.html. Getting started builds an inventory from nothing in about ten minutes.

• home-lab

  A house: a router, a switch, an access point, three computers, a server and a USB-to-Ethernet adapter, with VLANs, addresses and one wireless association. Start here.

  layers: l1 · l2 · l3 · identity

• quickstart

  The three devices docs/getting-started.md builds, one file at a time.

  layers: l1 · l2 · l3

• campus

  Several sites, a routed core, BGP and OSPF, and a firewall on the West core. The one to open namespace collapsing, the routing layer and the security layer on.

  layers: l1 · l2 · l3 · ipam · routing · security

• overlay

  Tunnels, including VXLAN over IPsec — encapsulation drawn as its own layer.

  layers: l1 · l3 · overlay

• patch-room

  Patch panels, racks and power feeds: the layers a diagram usually leaves out.

  layers: physical · l1 · rack · power

• containers

  What is inside a machine: five network namespaces, one nested inside another, joined by veth pairs. The one to open the netns layer on.

  layers: l1 · l3 · netns

• docker

  A container runtime at the scale it really runs at: three Docker hosts, sixteen namespaces nested up to three deep, a swarm overlay, two networks that use no veth pair at all, and the firewall zones that decide what crosses.

  layers: l1 · l3 · ipam · netns · overlay · security