Connect Systems & Ports
Create links by clicking/dragging between endpoints.
Wire the topology
Mission Planner links are created between specific endpoints and ports. Start the connection from one object, choose the matching source and destination interfaces, then save the link.
Verify port selection before committing the connection, especially on systems and switches with multiple interfaces.
Procedure
Connect Switch To External Network
Start a link between the switch and the external network using the connect action or direct canvas gesture shown in Mission Planner.
Select Switch Network Ports
Choose the switch interface that should carry the link, then save the connection. Network objects such as Management (Cloud0) do not expose numbered destination ports the way switches and VMs do, so there is no destination-port selection on the network-object side of that link.
Connect VM To Switch
Create a link between the VM and the switch after both objects are present on the canvas.
Select VM Switch Ports
Select the VM interface and switch port that should be connected, then save the link and verify it appears on the canvas.
Multiple connections between the same systems
Mission Planner can keep multiple independent links between the same pair of systems. Each wire retains its own source interface and destination interface, so a firewall, router, switch or appliance can use several explicit port-to-port relationships without collapsing them into one generic connection.
In the example below, pfSense and VyOS are connected by two separate links. The canvas labels preserve the interface pairings so an operator can see which ports participate in each path. The same model works for inside/outside interfaces, transit networks, management paths, redundant physical designs and lab topologies that deliberately use several interfaces between the same devices.
When parallel links are grouped for canvas interaction, right-click the connection group to inspect the member links and select the specific wire that needs attention. Each member remains an independent topology object with its own port mapping and state. If the connected systems require LACP, bonding or teaming, configure that behavior inside those systems while STRATUM continues to represent the underlying links individually.
Retaining the individual relationships matters for operations and AI. STRATUM can reason about a particular interface pair, distinguish a failed member from the rest of the connection group, and keep the topology aligned with the network that actually exists rather than reducing several cables to one ambiguous line.
Cloud/Management connections can select pnet0–pnet7. See Multi-Homed Workers to choose the bridge and understand where traffic exits when a VM connects through a remote STRATUM Switch.
The outcome you should see
The canvas shows the completed links and each endpoint is attached to the intended port.