VPN Field Guides [A]

VPN field guide 1/5: choose the tunnel before copying a config

A VPN setup usually starts with somebody else's configuration file. I would start one step earlier: write down what you need the tunnel to do. A server that lets you reach your home NAS is a different job from a VPS that carries all your phone traffic. Both can use WireGuard, but the routes, firewall and failure checks are different.

Pick a destination. If the endpoint is your home network, you control the exit but need to solve reachability through your router, possibly CGNAT. If it is a VPS, the VPS provider and the networks beyond it can still observe traffic leaving that server. A VPN protects the path to its endpoint; it does not make you anonymous to that endpoint, websites or services where you log in. Draw the path on paper: device → local network → VPN server → destination. Mark where DNS is answered and who operates each part.

Pick a routing policy. A full tunnel sends ordinary internet traffic through the VPN. In WireGuard, a client typically uses AllowedIPs = 0.0.0.0/0 for IPv4 and ::/0 for IPv6. A split tunnel sends only named subnets through it, for example a home LAN. AllowedIPs also defines which addresses a peer may use on the receiving side; it is not the server's NAT rule. If your server handles IPv4 only, adding ::/0 to the client without an IPv6 plan is not a finished design. Equally, leaving IPv6 outside the tunnel may leak traffic over the local connection. Decide deliberately whether to tunnel IPv6, disable it for this test, or use an OS-level block. Verify the result; don't infer it from a connected icon.

Pick a protocol for a reason. WireGuard is small and convenient for a personal UDP tunnel with key-pair peers. OpenVPN remains useful where an existing certificate infrastructure or TCP transport is a requirement; use current cipher guidance rather than an old copy-pasted --cipher line. IKEv2/IPsec can suit managed devices and networks that already support it; certificate/EAP choices and UDP 500/4500 reachability deserve attention. None of these names is a substitute for a tested client policy, key handling and a recovery plan.

Before buying a VPS or changing your router, answer five questions: Which devices and profiles will connect? Will all traffic or only selected networks use the tunnel? Where will DNS go? What should happen if the endpoint disappears? Who can rotate a lost device's key? If you cannot answer one, the next guide's small one-client lab is a safer starting point than a production rollout.

Sources, checked 3 October 2026:
WireGuard Quick Start — https://www.wireguard.com/quickstart/
WireGuard known limitations — https://www.wireguard.com/known-limitations/
OpenVPN 2.6 manual — https://openvpn.net/community-docs/community-articles/openvpn-2-6-manual.html
strongSwan IKEv2 introduction — https://docs.strongswan.org/docs/latest/howtos/introduction.html
Ubuntu WireGuard overview — https://ubuntu.com/server/docs/how-to/wireguard-vpn/

↑ 5

Обсуждение

Комментарии

0

Комментариев пока нет.

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