CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 6 of 16

Route-based IKEv2 VPN with st0

Join Poole and Falmouth with a route-based IKEv2 VPN: proposals, policies, gateway, st0 in its own zone, routes and policies, then dead peer detection.

Run this lab

It needs Standard: its 5 nodes are set to 7 vCPU and 10,752 MB in total.

In your workspace: Shared, then JNCIA-SEC and JNCIS-SEC SRX security guided labs, then 06 - Route-based IKEv2 VPN with st0

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 7 vCPU and 10,752 MB together. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 75 minutes
Nodes need
7 vCPU, 10,752 MB
Smallest plan
Standard

The scenario

Hartwell's two sites, Poole (head office) and Falmouth (the yard), both have an SRX and internet access with source NAT. Staff at Falmouth need the Poole file server, and the Poole office needs the Falmouth stock server. You'll join them with a route-based IKEv2 VPN: the tunnel appears as an interface, st0.0, and ordinary routing decides what goes down it.

DeviceInterfaceAddressNotes
ISPGi0/0 / Gi0/1198.51.100.1/30 / 203.0.113.1/30The internet between the sites
SRX-HQge-0/0/0198.51.100.2/30Zone untrust, default route to the ISP
SRX-HQge-0/0/110.10.10.1/24Zone trust, Poole LAN
HQ-PCeth010.10.10.10/24Gateway 10.10.10.1
SRX-BRge-0/0/0203.0.113.2/30Zone untrust, default route to the ISP
SRX-BRge-0/0/110.20.10.1/24Zone trust, Falmouth LAN
BR-PCeth010.20.10.10/24Gateway 10.20.10.1
SettingValue
IKE proposalPre-shared keys, DH group 20, SHA-256, AES-256-CBC, 28,800 s
Pre-shared keyHartwell-VPN-2027
IPsec proposalESP, HMAC-SHA-256-128, AES-256-CBC, 3,600 s, PFS group 20
Tunnel addressesst0.0: SRX-HQ 172.16.12.1/30, SRX-BR 172.16.12.2/30, zone vpn

What you’ll practise

  • Build IKE and IPsec configuration in layers
  • Bind a VPN to st0 and place it in a zone
  • Allow IKE with host-inbound traffic
  • Route traffic through the tunnel and write policies for it
  • Verify SAs, counters and real traffic
  • Add dead peer detection

The tasks

  1. Check the underlay
  2. IKE, phase 1
  3. IPsec, phase 2
  4. st0, zones, host-inbound and routes
  5. Policies
  6. Verify, and see the traffic
  7. Notice a dead peer

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Route-based IKEv2 VPN with st05 nodes, 4 links. Every link is listed as text below the diagram.ISPSRX-HQSRX-BRHQ-PCBR-PCge-0/0/1eth0ge-0/0/1eth0ge-0/0/0Gi0/0ge-0/0/0Gi0/1
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • SRX-HQ ge-0/0/0 to ISP Gi0/0
  • SRX-BR ge-0/0/0 to ISP Gi0/1
  • SRX-HQ ge-0/0/1 to HQ-PC eth0
  • SRX-BR ge-0/0/1 to BR-PC eth0
Nodes in Route-based IKEv2 VPN with st0, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
ISPCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SRX-HQJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
SRX-BRJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
HQ-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
BR-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder JNCIA-SEC and JNCIS-SEC SRX security guided labs.

  3. Open 06 - Route-based IKEv2 VPN with st0 and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More JNCIA-SEC and JNCIS-SEC labs

All JNCIA-SEC and JNCIS-SEC labs

Related labs in other courses

CloudLabBox is independent of Cisco and Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.