Know what’s inside
your tunnel.
One connection. Several separate questions.
A protocol, a routing rule, and a traffic-blocking control do not do the same job. Keeping them separate makes it easier to evaluate a product, understand its settings, and describe an unexpected result. Begin with your actual device and a concrete task rather than a list of features.
The guides below introduce each concept, connect it to ordinary use, and explain why platform-specific documentation matters. Use them as a vocabulary for better questions. When it is time to configure a product, follow its maintained instructions and keep a record of changes you make.
The encrypted tunnel
A VPN creates a protected route to an endpoint for the traffic configured to use it. Understand that boundary before assuming the website, the account, or every other app is covered.
The protocol
WireGuard and OpenVPN offer different engineering choices. Evaluate the supported implementation, compatibility, and performance of your actual setup.
The failure behavior
A kill switch is about where traffic may go when a required connection is unavailable. Product names and platform behavior need a closer look.
The deliberate exception
Split tunneling directs selected traffic through different routes. Know the default policy and the reason behind every included or excluded application.
The name lookup
DNS behavior deserves its own question. A public-IP result does not establish the route of every name lookup on a device.