Topology and VLANs
Solid links are wired (with negotiated speeds), dashed are Wi-Fi, and dotted links are containers pinned to their host.
The Topology tab is an interactive graph of your network (Cytoscape).
- Drag nodes to arrange them — the layout is saved.
- Click a node to open its host detail panel.
- Node color reflects device type (router, server, container, workstation, camera, tv, AP…); the legend explains the colors.
- Connections between hosts can be drawn and labeled — wired / wifi / fiber / DAC / virtual — with a speed and VLAN tags.
- The Hierarchy tab gives a tiered, printable view derived from your connections (mark your gateway as Level 1 in a host's Edit dialog).
Connect a container/VM to the host it runs on, using the virtual link — not to the switch.
So: NUC → switch (wired cable), and container → NUC (virtual link).
Why: a container has no cable of its own — it egresses through its host's NIC (and on bridge networking it sits behind the host's NAT). Drawing it to its host reflects reality, shows the real failure domain (host down → its containers down, which lines up with the host↔service correlation in Services and Monitoring), and keeps the graph tidy.
Rule of thumb: physical boxes connect to what they're cabled to; virtual things connect to the machine they run on, via the virtual link.
Define VLANs once (tag + name + color), then assign them to connections. The graph colors links by VLAN, so you can see at a glance which segments carry which VLANs. A connection can carry multiple VLANs (e.g. a trunk).
The Services tab also has a Topology view — a graph of services and their dependencies, if you've defined any (e.g. "app depends on database").