Devices
A device is a machine you have registered so it can reach your labs over the private tunnel (an encrypted WireGuard connection). This page covers how to manage your devices after you have added them.
Follow Connect your device — it walks through installing WireGuard, registering, and testing the tunnel.
Go to Connectivity → My Devices.
Reading a device card
| Field | Meaning |
|---|---|
| Status | Online (green) — the tunnel is up. Unreachable (amber) or Offline (red) — the device has not been heard from recently; activate the tunnel on that machine. No Connection — the tunnel has never connected. |
| Interface chip | Which network the device is on. The shared network is the default. |
| Device IP | The device's address inside the private network |
| Origin IP | Where the tunnel last connected from |
| Sent / Received | Traffic through the tunnel |
| Reserved | This address is kept for the device (below) |
What the status means
The status comes from the last time the device completed a handshake with the private network. Hover the status badge to see when that was. The page updates the status and traffic counters every few seconds while it is open.
| Status | Last handshake |
|---|---|
| Online | Less than 2 minutes ago |
| Unreachable | Between 2 and 10 minutes ago |
| Offline | More than 10 minutes ago |
| No Connection | Never |
A tunnel only handshakes when there is traffic or a keep-alive, so a device whose tunnel is switched off in the WireGuard app drifts from Online to Offline on its own. That is normal.
Add a device: every field
Add Device opens a dialog. The step-by-step setup is in Connect your device; this table explains every field you may see.
| Field | What it does |
|---|---|
| Device Name | A name you recognize, up to 25 characters. Also used as the name of the downloaded tunnel file. |
| Device Type | Mobile, Laptop, Desktop, Tablet, Server, IoT or Embedded. A label shown on the card. |
| Network | Shown only when you can use more than the public network. Choose which private network the device joins. See Private networks. |
| Reallocate IP | Shown only when you have reserved addresses that no device is using. Pick one to give this device that address, or leave Auto-allocate for a new one. |
| Wireguard Public Key | Paste your own WireGuard public key — 44 characters ending in = — or check Auto Generate Keypair and leave the field empty. |
| Auto Generate Keypair | The platform creates the key pair and keeps the private key, so it can give you a ready-to-use tunnel file and QR code. |
| Primary Device, Trusted Device | Labels for your own reference. They do not change what the device can reach. |
| Reserve IP when Allocated | Reserves the address the device gets, as if you chose Reserve IP afterwards. |
What a tunnel file contains
The tunnel file sends only traffic for the private network through the tunnel. Your normal internet traffic does not go through it. The file also keeps the tunnel alive while it is idle, so labs can reach the device too.
Keep the same address: reserve it
Without a reservation, a device can be given a different address later. If you have scripts, firewall rules or bookmarks that point at a device's address, reserve it.
- Reserve IP in the device's menu keeps the current address.
- Unreserve IP gives it up. The address goes back to the pool and the device may get a different one next time.
You can also select Reserve IP when Allocated when you add a device. Reserved addresses are listed under My Network → IP Addresses — see Private networks.