Study guide

6.2 Stateless Firewall Filters

JNCIA-Junos Juniper Networks Certified Associate

Track your progress as you read

Finished sections get a check mark.

1 Introduction & JNCIA-Junos Exam Overview

1.1 JNCIA-Junos Exam Facts 1.2 Juniper Certification Track 1.3 Exam Blueprint & Study Strategy

2 Networking & Junos OS Fundamentals

2.1 Networking Fundamentals 2.2 Junos OS Architecture 2.3 Transit Traffic & Packet Flow

3 User Interfaces & Configuration Basics

3.1 Junos CLI & J-Web 3.2 Configuration Model 3.3 Initial Configuration & Interfaces

4 Operational Monitoring & Maintenance

4.1 Monitoring with Operational Commands 4.2 Logging & Traceoptions 4.3 Device Maintenance

5 Routing Fundamentals

5.1 Routing & Forwarding Tables 5.2 Static & Default Routing 5.3 Route Preference & Dynamic Routing Overview

6 Routing Policy, Firewall Filters & Final Review

6.1 Routing Policy 6.2 Stateless Firewall Filters 6.3 High-Yield Review & Test Strategy

6.2 Stateless Firewall Filters

Key Takeaways Explain This Topic AI

Stateless firewall filters inspect packets in the forwarding plane and do not track connection state; each packet is evaluated independently against ordered terms.

Each filter term has an optional from (match conditions such as source/destination address, protocol, port, DSCP) and a then (actions such as accept, discard, reject, plus action-modifiers like count, log, syslog, policer, or forwarding-class).

There is an implicit deny-all at the end of every firewall filter: any packet that matches no term is silently discarded, so an explicit accept term is almost always required.

Filters are applied per interface and per direction using family inet (or inet6) with filter input or filter output; an input filter sees inbound packets and an output filter sees outbound packets.

Applying a filter to the device's loopback interface (lo0) protects the routing engine itself, and policers can rate-limit traffic by enforcing a bandwidth limit and burst size.

Last updated: May 2026

Why Stateless Firewall Filters Matter

Stateless firewall filters are the Junos OS tool for matching and acting on individual packets in the forwarding plane . They are called stateless because each packet is evaluated independently — the filter does not track sessions, connection state, or return traffic. This is different from a stateful firewall on an SRX security device, and the JNCIA-Junos exam expects you to know that core distinction.

Firewall filters are used to:

Permit or deny traffic transiting the device.

Protect the Routing Engine (RE) from unwanted or excessive control-plane traffic.

Classify, count, log, or rate-limit traffic.

Reinforce the control-plane vs forwarding-plane split from section 6.1: routing policy = routes; firewall filters = packets.

Filter Structure: Terms, From, Then

Firewall filters are configured under [edit firewall family inet filter <name>] and, like routing policy, are built from ordered terms :

from — match conditions. With no from , the term matches every packet.

  • then — the action and any action-modifiers. firewall {
  • family inet {
  • filter protect-mgmt {
  • term allow-ssh {
  • from {
  • source-address {
  • 192.168.10.0/24;
  • }
  • protocol tcp;
  • destination-port ssh;
  • }
  • then accept;
  • }
  • term log-and-drop {
  • then {
  • count dropped-pkts;
  • log;
  • discard;
  • }
  • }
  • }
  • }
  • }
  • The Implicit Discard

Every firewall filter has an implicit, terminating discard at the end. Any packet that matches no term is silently dropped. Because of this, a filter that only contains "deny" terms will drop all traffic — you almost always need at least one explicit accept term for legitimate traffic. This implicit-discard behavior is one of the most heavily tested JNCIA-Junos firewall facts.

Terms are evaluated top to bottom , and unlike routing policy, a basic accept / discard / reject action is terminating — the packet's fate is decided and no further terms are checked.

  • Match Conditions, Actions, and Action-Modifiers
  • Common from Match Conditions
  • Match condition Matches on
  • source-address / destination-address Packet source/destination IP or prefix
  • protocol IP protocol (tcp, udp, icmp, ospf...)
  • source-port / destination-port TCP/UDP port number or name
  • dscp / precedence QoS/CoS marking
  • tcp-flags TCP control flags (e.g., established, syn)
  • packet-length / fragment-offset Size or fragmentation
  • Actions vs Action-Modifiers

Terminating actions decide the packet and stop term evaluation:

accept — let the packet through.

discard — drop the packet silently (no notification to the sender).

reject — drop the packet and send an ICMP/protocol-unreachable message back (you can specify the reject type).

Action-modifiers can be combined with an action and do not stop evaluation by themselves:

count <name> — increment a named counter.

log / syslog — record the match (log is a local kernel cache; syslog goes to the system log).

policer <name> — apply a rate limiter.

forwarding-class / loss-priority — set CoS handling.

next term — explicitly continue to the next term (without it, an action is terminating).

Know the discard vs reject difference cold: discard is silent; reject notifies the sender. Exam questions phrase this as "which action drops the packet without informing the source?"

Applying Filters to Interfaces and Protecting the RE

A filter does nothing until it is applied to an interface, under a specific address family and direction : interfaces {

  • ge-0/0/0 {
  • unit 0 {
  • family inet {
  • filter {
  • input protect-mgmt;
  • output egress-acl;
  • }
  • address 10.1.1.1/24;
  • }
  • }
  • }
  • }
  • Term Meaning
  • filter input Evaluates packets arriving on the interface
  • filter output Evaluates packets leaving the interface
  • family inet / inet6 IPv4 / IPv6 filter family
  • Routing Engine (RE) Protection

Applying an input filter to the loopback interface lo0 filters traffic destined to the device's own Routing Engine — SSH, SNMP, BGP, OSPF, ping to the device, etc. This is the standard Junos technique for RE protection / control-plane protection : permit only required management and routing protocols from trusted sources, then discard the rest. A lo0 filter does not affect transit traffic forwarded through the device; transit traffic is filtered on the data interfaces it actually traverses.

Policer Basics

A policer enforces a traffic rate. It is defined with two key parameters:

Bandwidth limit — the sustained rate (bits per second).

Burst-size limit — how much traffic can briefly exceed the rate (bytes).

Traffic that conforms is forwarded normally; traffic that exceeds the policer is handled by the configured action (commonly discard or marking a higher loss priority). Policers are referenced from a filter term as the policer action-modifier, which is the typical way to rate-limit a specific class of traffic such as ICMP toward the RE.

Loading diagram... Stateless Firewall Filter Packet Flow