Use topology before numbers
An IP plan should know which devices are reachable from the router. HLBuilder calculates from saved nodes and edges, so the visual topology matters before any address list is trusted.
That makes orphan devices obvious. If a server is not connected to a router path, it should not quietly receive a normal service address.
Keep role ranges predictable
HLBuilder maps node types to role ranges inside a subnet. Routers, switches, access points, NAS units, servers, mini PCs, and SBCs can each sit in a predictable part of the plan.
Predictable ranges make the generated plan easier to read. The user can look at an address and understand whether it belongs to infrastructure, storage, or compute.
Save before calculating
The frontend should save the current build before asking the backend to calculate network data. That order matters because calculation reads the saved nodes and edges.
For the user, this means the canvas and address list stay tied together. A changed cable should be saved before the address plan is reviewed.
Builder checks
Check
Router node exists and has a gateway role.
Check
All addressable devices are connected through the topology.
Check
Device roles match the address ranges expected by the plan.
Check
The build is saved before network calculation runs.
Common questions
Why plan IP addresses from a diagram?
A diagram shows reachability and role. That prevents disconnected devices from looking valid in an address list.
What does HLBuilder do for IP planning?
HLBuilder reads saved topology data and assigns addresses by router reachability and node type.