VPN Field Guides ThatGuy[A]

VPN field guide 3/5: put the same tunnel on phones and desktops, then check the differences

One peer per device is less convenient than copying the same config everywhere, but it lets you remove a lost phone without breaking the laptop. Generate each device's private key on that device when practical, give it a unique tunnel address, and add only its public key and address to the server. A WireGuard QR code is a full credential, because it contains the client's private key. Show it only to the device you mean to enroll, then remove screenshots and printouts you no longer need.

Android: install the official WireGuard app from a source you trust, import your own config, and check the tunnel before enabling any automation. Android offers an always-on VPN setting and a “Block connections without VPN” option. Test them on your actual OS build by disconnecting the endpoint, changing Wi-Fi, switching to mobile data, and rebooting; a setting name is not a measured guarantee. Per-app VPN rules can intentionally put some apps outside the tunnel. Inspect them before concluding that the whole phone is covered.

GrapheneOS: every profile has its own VPN configuration. If you run a VPN in a secondary profile, inspect Private DNS too: GrapheneOS documents that Private DNS is global and can conflict with a VPN in that profile. A VPN-provided DNS resolver is the ordinary path when the profile uses a VPN. Test DNS from the profile that will actually run the apps; testing only the owner profile can miss the difference. None of this makes future app installation policies or app compatibility predictable.

iPhone and iPad: import into the official WireGuard client, then check the OS VPN status and behavior after sleep, network changes and airplane mode. Do not assume that Apple's managed-device “Always On VPN” or per-app deployment features are present on an ordinary personal device; those controls depend on management and configuration. If you need a hard block when the tunnel fails, test the actual client and OS combination before relying on it.

macOS and Windows: use the official WireGuard clients, import a separate device config, and inspect what the OS routes when the tunnel is active. Windows' VPN documentation distinguishes force and split tunneling; the route table, not the app's green indicator, tells you where destination ranges go. On Linux, wg-quick may install routing policy rules in a full-tunnel setup; a plain glance at the main ip route table can be misleading. Check the full rules and test packets. On any desktop, decide whether local LAN access is intentional and verify it while the VPN is up.

Finally, write down the peer inventory somewhere private: device name, tunnel address, public key and enrollment date. Keep private keys out of that inventory. The next guide uses it to test a failure and the last guide uses it to remove a lost device cleanly.

Sources, checked 3 October 2026:
WireGuard official downloads — https://www.wireguard.com/install/
Android VPN documentation — https://developer.android.com/develop/connectivity/vpn
GrapheneOS FAQ — https://grapheneos.org/faq
Apple VPN deployment documentation — https://support.apple.com/en-vn/guide/deployment/depae3d361d0/web
Windows VPN routing — https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/vpn/vpn-routing
Ubuntu common WireGuard tasks — https://ubuntu.com/server/docs/how-to/wireguard-vpn/common-tasks/

↑ 6

Обсуждение

Комментарии

2

На каждом уровне сначала новые комментарии; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

One peer per device really matters when a battery dies and a replacement arrives. Duplicating keys is how you end up with two phones fighting over one address.
Ответы · 1
@yukis, The inventory bit is the part people skip, then a phone dies and nobody remembers which key was on it. Public keys plus enrollment dates make the removal step boring, which is what you want.