Devices and connections
The device page stores paired targets and connection information. One device can have multiple routes. Display labels, default selection and route policy are separate settings.
Add and identify devices
Use the pairing entry, then set a recognizable label in the device menu, such as “Home workstation.” A label helps identification but does not replace checking device identity.
Distinguish editing, routes, disconnecting and removing.
Capture instructions · app-devices
Show demo device actions and network details including the actual path.
Device menu
| Action | Purpose |
|---|---|
| Edit and save display name | Identify the device in lists |
| Set default | Select the default target |
| Network connections | Inspect routes, latency and policy |
| Authorize device | Follow the re-pairing flow for access |
| Disconnect | Close the current shared connection |
| Remove device | Remove this App’s saved routes and credentials |
Removing a device locally does not revoke its host-issued grant. For a lost phone or permanent removal, revoke access on the target.
Inspect multiple routes
Open network connections and inspect the actual current route, then candidate status and latency. Reconnect after saving a policy and verify the resulting path. A route label alone does not prove Direct, P2P or Relay was used.
Connection failures
Check target wakefulness and daemon status, then phone network, addressing and grants. A LAN address may stop working after switching to cellular. See route diagnosis.