Start here10 min
Device onboarding
Choose the correct client, create a unique identity and validate the first handshake.
Outcome
A uniquely identified endpoint with a stable name, overlay address and verified connection.
Before you start
- Permission to create devices
- A supported endpoint
- A site-and-role naming convention
Choose an onboarding mode
- Create: Wantastic creates the identity and provides its configuration.
- Claim: attach a pre-provisioned device with its valid WireGuard public key.
- MikroTik: apply a RouterOS 7 script; no router package is installed.
- OpenWrt/Linux: use wantasticd or a standard WireGuard profile.
Operational note: A WireGuard public key is 32 bytes and normally appears as a 44-character Base64 value.
Model the endpoint for operations
- 1Use a site plus role name, not a model-only name.
- 2Assign the correct tenant or operational group.
- 3Record whether it is a gateway, managed router, workstation or client.
- 4Enable optional services only after base connectivity works.
Apply the generated configuration
- RouterOS: paste the complete script once and read the first terminal error, if any.
- OpenWrt/Linux: use the fresh token on the intended endpoint and remove it from shell history.
- WireGuard client: import the file or scan the QR code on one device only.
Operational note: Regenerate credentials if a configuration or token was posted in chat, a ticket or a public recording.
Verify the result
The identity is unique.
Online and last-seen state update.
The assigned address matches the device row.
Disconnecting this endpoint changes only its own state.
Common issues
A claim key is rejected.
Likely cause
The key is malformed, already claimed or changed by URL/form decoding.
Fix
Copy the original Base64 key, confirm it decodes to 32 bytes and retry without spaces.
Two devices alternate online/offline.
Likely cause
They share one WireGuard identity.
Fix
Create a separate device and install a unique configuration on each endpoint.
Continue with
Getting startedCreate a workspace, connect the first device and prove that the remote path works.Install and operate wantasticdConnect Linux and OpenWrt endpoints with the open-source userspace agent.Remote MikroTik setupConnect RouterOS 7 behind CGNAT and prove remote management without exposing Winbox.