CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 5 of 16

Routing instances and filter-based forwarding

Send voice traffic out of a second internet line with filter-based forwarding, and keep guests in their own virtual router, joined to the main table by a next-table route and a rib-group.

Run this lab

It needs Lite: its 5 nodes are set to 6 vCPU and 7,168 MB in total. That fits the free demo too.

In your workspace: Shared, then JNCIA-SEC and JNCIS-SEC SRX security guided labs, then 05 - Routing instances and filter-based forwarding

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 70 minutes
Nodes need
6 vCPU, 7,168 MB
Smallest plan
Lite

The scenario

Hartwell's yard at Falmouth has two internet lines. ISP-A is big and cheap, ISP-B is small with very steady latency. The boss wants the phones on ISP-B and everything else on ISP-A. A guest network has to reach the internet without touching the office routing table.

DeviceInterfaceAddressNotes
SRXge-0/0/0198.51.100.2/30Zone untrust, to ISP-A (198.51.100.1)
SRXge-0/0/1198.51.100.6/30Zone untrust, to ISP-B (198.51.100.5)
SRXge-0/0/210.10.10.1/24Zone trust, office LAN
SRXge-0/0/310.10.90.1/24Zone guest, guest Wi-Fi (you add it)
LAN-PCeth010.10.10.10/24, 10.10.10.70/24Desktop, and the voice gateway's address
GUESTeth010.10.90.10/24Gateway 10.10.90.1
ISP-A, ISP-BLoopback0192.0.2.200/32The same test address behind both providers

Each ISP router answers on 192.0.2.200, and each one already has routes back to the 10.10.x.0/24 networks. So the second hop of a traceroute tells you which line your traffic took. No NAT is used here.

What you’ll practise

  • Explain forwarding and virtual-router instances
  • Share interface routes with a rib-group
  • Steer traffic with a firewall filter and routing-instance action
  • Join tables with a next-table route and a rib-group
  • Keep zones and policy working across instances

The tasks

  1. Default routing
  2. A forwarding instance for ISP-B
  3. The filter
  4. A virtual router for the guests

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 Routing instances and filter-based forwarding5 nodes, 4 links. Every link is listed as text below the diagram.SRXISP-AISP-BLAN-PCGUESTge-0/0/2eth0ge-0/0/0Gi0/0ge-0/0/1Gi0/0ge-0/0/3eth0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • SRX ge-0/0/0 to ISP-A Gi0/0
  • SRX ge-0/0/1 to ISP-B Gi0/0
  • SRX ge-0/0/2 to LAN-PC eth0
  • SRX ge-0/0/3 to GUEST eth0
Nodes in Routing instances and filter-based forwarding, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
SRXJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
ISP-ACisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
ISP-BCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
LAN-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
GUESTEVE-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 05 - Routing instances and filter-based forwarding 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.