CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 7 of 16

Policy-based VPN and traffic selectors

Build a policy-based VPN with pair policies and a NAT exemption alongside a route-based VPN with a traffic selector, compare how each picks its traffic, and read about dial-up.

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 07 - Policy-based VPN and traffic selectors

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 70 minutes
Nodes need
7 vCPU, 10,752 MB
Smallest plan
Standard

The scenario

Falmouth's accounts system must only ever talk to Poole's accounts LAN, and the auditors like to see that in the security policy itself. Meanwhile the engineering subnets also need a link, and your colleague wants to try traffic selectors. You'll build one of each between the same two firewalls, and see how they differ.

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
Second subnets (already on the LAN ports and the PCs)PooleFalmouth
Accounts: policy-based VPN10.10.10.0/24 (HQ-PC .10)10.20.10.0/24 (BR-PC .10)
Engineering: traffic selector10.10.30.0/24 (HQ-PC .10)10.20.30.0/24 (BR-PC .10)

The algorithms match lab 6: DH group 20, SHA-256, AES-256-CBC, ESP with HMAC-SHA-256-128, PFS group 20, key Hartwell-VPN-2027. The proposals, policies and gateway GW-PEER are already configured on both SRXs, along with system-services ike on untrust. So only the VPNs themselves are left. There's one change from lab 6: the gateway here is IKEv1, in main mode. Task 1 explains why.

What you’ll practise

  • Build a policy-based VPN with tunnel actions and pair policies
  • Exempt VPN traffic from source NAT
  • Read proxy IDs in SA detail
  • Narrow a route-based VPN with traffic selectors and auto route insertion
  • Explain the differences, and where dial-up and Secure Connect fit

The tasks

  1. A policy-based VPN
  2. Keep NAT out of it
  3. Traffic selectors on a route-based VPN
  4. Compare them
  5. Dial-up, as a concept

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 Policy-based VPN and traffic selectors5 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 Policy-based VPN and traffic selectors, 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 07 - Policy-based VPN and traffic selectors 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.