Synthetic Devices
A synthetic device stands in for connectivity Forward can't collect directly: the public internet, a leased L3 VPN, a carrier WAN circuit, an encrypted tunnel. You define it, and Forward models paths through it so traffic continues across the uncollected segment instead of dead-ending at the edge of your collected network.
Synthetic devices model user-defined connectivity. They are not a substitute for collection. If a physical device is reachable and you have credentials, collect it — a synthetic device is for the segment you genuinely can't reach.
In This Section
| Page | What it covers |
|---|---|
| Overview | What synthetic devices model, how they fit the collected network, where they sit. |
| Choosing a Device | Which type to use for a given situation, and how the types differ. |
| Configuring Connections | Uplink vs. gateway, VLAN, site, subnet auto-discovery, backdoor ports. |
| Automated Setup with NQE | Generating connections in bulk from an NQE query, with the schema and gotchas. |
| Reference | Per-type fields, constraints, locations, BGP collection, and API pointers. |
| Missing Peer | The placeholder Forward auto-creates for unmodeled uplink traffic. |
| Troubleshooting & FAQ | Symptom-keyed fixes for common synthetic-device problems. |
Suggested Reading Order
- New to synthetic devices: read Overview, then Choosing a Device, then Configuring Connections.
- Setting one up: Choosing a Device to pick the type, Configuring Connections for the field choices, and Automated Setup with NQE if you have many connections to add.
- Looking up a field, constraint, or API path: go straight to Reference.
Where to Find Them
To add or edit a synthetic device, open the Sources page and select the Synthetic nodes category.
Changes to a synthetic device — creating one, editing it, adding or removing a connection — take effect on the next processed snapshot, not the current one.