Before you link devices
Device Link lets authorized devices communicate using their virtual addresses over their VPN connections. In the consumer and website workflow, both devices need active subscription connections, supported direct routes and the same specific exit server. Choosing the same country is not enough. Pay as you go connections are not eligible.
Request and approve a link
Keep both devices connected while you complete these steps.
- Open Featured, then Device links in the client. Share your device public key with the intended peer; never share its private key.
- On the website, open Devices & connections, then Device Link. Choose your source device and either your other device or its 64-character public key.
- Request the link, review pending requests in the clients and approve where asked. Wait for an active link.
- Right-click the peer in Device links to copy its available virtual IPv4, IPv6 or public key. Use the virtual address in your application.
Example: reach a service on another computer
For a game or file service, connect to the peer's virtual address and service port. The service must be running, listening on a suitable interface and allowed by that computer's firewall. Device Link does not publish its port on the public internet.
Keep consent and availability in view
Ask for approval is the default. Open accepts incoming requests automatically; Closed declines them and prevents new outgoing links. Remove revokes a saved link authorization. A saved authorization does not keep an offline device reachable.
Other accounts are supported through an explicitly shared public key, not a public device directory. Automatic discovery is limited; not every LAN application discovers peers. Ordinary-client configurations can expose different server-managed options; these steps describe the consumer workflow.