Skip to content

Device lifecycle

Choose an unused address inside hub.client_cidr, a tunnel ID (or direct), and a protected output location. The private key goes directly into the profile and is not retained by the hub.

Terminal window
hubctl device add laptop \
--address 10.80.0.2/32 \
--egress corp-egress \
--output ./laptop.conf
hubctl validate
hubctl deploy --confirm-within 5m
hubctl confirm

This changes only the selected device’s default egress; private routes stay governed by tunnel routes and zones.

Terminal window
hubctl device set-egress laptop direct
hubctl deploy --confirm-within 5m
hubctl confirm

Revoke a lost profile first. Reissue with a fresh profile rather than copying a private key. Reverse only an accidental revocation.

Terminal window
hubctl device revoke laptop
hubctl device unrevoke laptop
hubctl device list

Use hubctl routes to explain active destination paths. If the revision is unhealthy before confirmation, run hubctl rollback.