JNCIA-Junos lab 11 of 15
Firewall filters and unicast RPF
Protect HQ's routing engine with a loopback filter, rate-limit ICMP with a policer, block selected transit traffic between the depot and the warehouse, and switch on unicast reverse-path forwarding, first strict, then loose when asymmetric routing makes strict mode drop good traffic.
Run this lab
It needs Standard: its 3 nodes are set to 12 vCPU and 15,360 MB in total.
In your workspace: Shared, then JNCIA-Junos JN0-106 guided labs, then 11 - Firewall filters and unicast RPF
- Level
- Intermediate
- Time
- About 65 minutes
- Nodes need
- 12 vCPU, 15,360 MB
- Smallest plan
- Standard
The scenario
An audit of HQ found that anyone who can reach the router can try to log in, and that nothing limits how hard the routing engine can be flooded with pings. Operations also want two transit rules: the depot LAN may not ping the warehouse LAN, and traceroute through HQ should not reveal the warehouse. Finally, HQ must drop packets with forged source addresses.
OSPF runs everywhere (see the canvas). The WH-DEPOT radio link has metric 100 on both ends, so traffic between DEPOT and WH normally goes through HQ.
| Rule | Detail |
|---|---|
| Management | SSH to HQ only from the HQ LAN 10.1.0.0/24 |
| Routing | OSPF must keep working |
| ICMP to HQ | Allowed, policed to 1 Mbps |
| Traceroute to HQ | Allowed |
| Anything else to HQ | Dropped, counted and logged |
| Depot LAN to warehouse LAN | No ping (reject, so the sender knows) |
| Traceroute through HQ to WH | Dropped silently |
What you’ll practise
- Tell transit traffic from exception (host-bound) traffic and say where each is filtered
- Write stateless firewall filters with ordered terms, match conditions, actions and action modifiers
- Protect the routing engine with an input filter on lo0 without breaking OSPF
- Police ICMP to the routing engine and read the counters
- Compare reject and discard, and TCP, UDP and ICMP matches, on transit traffic
- Configure unicast RPF and explain strict and loose mode with asymmetric routing
The tasks
- Transit and exception traffic
- Protect the routing engine
- See the policer work
- Filter transit traffic
- Unicast reverse-path forwarding
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.
Every link, as text
- HQ
ge-0/0/0to DEPOTge-0/0/0 - HQ
ge-0/0/1to WHge-0/0/0 - WH
ge-0/0/1to DEPOTge-0/0/1 - HQ
ge-0/0/2to HQ-LAN (network) - WH
ge-0/0/2to WH-LAN (network) - DEPOT
ge-0/0/2to DEPOT-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| WH | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| DEPOT | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIA-Junos JN0-106 guided labs.Open
11 - Firewall filters and unicast RPFand 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-Junos labs
Related labs in other courses
CloudLabBox is independent of Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.