What Is IPsec VPN? How IKEv2 Sets Up Protected Traffic
A device might call the VPN type “IKEv2,” while your IT instructions call it “IPsec VPN.” These labels describe different jobs in one connection. IKEv2 negotiates and authenticates. IPsec protects packets under the resulting agreements. That distinction helps when the client can connect but the resource you need still won’t open.
About 3 min read
Follow the connection from setup to data
- 01 · NegotiateThe device and gateway establish IKE parameters
- 02 · AuthenticateThe peers usually set up the first Child SA
- 03 · Protect dataESP handles the IP packets covered by policy
A common connection begins with IKE_SA_INIT. The device and gateway agree on how to protect their negotiation and exchange the material needed to derive keys. IKE_AUTH then authenticates the parties and normally establishes the first Child SA for traffic. SA stands for security association. It includes the parameters and state the peers use for a protected exchange.
ESP is commonly used at the data stage. It protects IP packets that match the relevant security association. The deployed policies and routes determine which traffic is in scope. A connection icon can tell you that the client reached a particular stage, while the route for a particular app needs its own check.
Test the right resource for your deployment
In remote access, an employee device commonly connects to a company gateway. Test the internal page IT gave you and note whether ordinary browsing still works. If the organization routes only internal addresses over the tunnel, your public IP can remain the same.
Site-to-site setups often connect two gateways. Devices use their usual local network to reach the approved remote resources. The teams managing both networks should agree on which networks and directions are in scope. If the goal is to reach one file service from a branch, test that service rather than assuming that any reachable page proves the whole deployment is working.
Identify the first stage that fails
| Symptom | What to record and verify |
|---|---|
| The connection times out before any authentication prompt | Network access, whether ordinary browsing works, gateway name, and the time |
| Authentication starts and then fails | The exact error, account type, and device time. Ask IT to check certificates, identity, and permissions |
| The client connects but the approved resource won’t open | Compare with a second approved resource and ask IT to check routes, name resolution, and access policy |
| It drops only after changing Wi-Fi networks | Record the old and new network types and whether it reconnects. Ask whether your setup supports address changes |
Keep the issued profile and change one test condition at a time. Redact internal hostnames, certificate contents, and account details before sharing screenshots. If a certificate warning appears, stop and ask the issuer to verify it.
Describe the difference between connected and usable
An actionable ticket might say, “The client showed Connected, the approved ticketing page timed out, and the test intranet page still loaded.” The administrator can now distinguish the tunnel from the route or service. Include the time zone so support can correlate gateway logs.
Frequently asked questions
Does IKEv2 encrypt the web page I’m reading?
IKEv2 negotiates and authenticates. ESP normally protects in-scope IP packets, while HTTPS protects the browser’s connection to the site independently.
Why can I reach the intranet while my public IP stays the same?
Your organization may route only internal networks through the VPN. Use the approved internal test resource to confirm access.