Packet Filtering Firewalls
What you'll learn: How basic stateless firewalls make security decisions by examining individual packet headers.
The Checkpoint Analogy
Imagine a security guard at a building entrance who checks each person's ID against a simple list: "Allow anyone from Company A, block anyone from Company B, allow deliveries to Floor 3 only." The guard doesn't remember who passed through earlier—they just check each person independently against the rules.
That's exactly how packet filtering firewalls work. They're the simplest type of firewall, examining each network packet individually and deciding whether to allow or drop it based on basic header information.
What Packet Filters Inspect
A stateless packet filtering firewall looks at the network layer (IP) and transport layer (TCP/UDP) headers, checking:
- Source IP address – Where is this packet coming from?
- Destination IP address – Where is it going?
- Protocol – Is it TCP, UDP, ICMP, or something else?
- Source port – Which port sent this?
- Destination port – Which service is it trying to reach (e.g., port 80 for HTTP, 443 for HTTPS)?
How Rules Work
You create an ordered list of rules. For example:
- Allow TCP from
192.168.1.0/24to any destination on port 443 - Block all UDP from
10.0.0.50to any destination - Allow ICMP echo requests from anywhere
- Default: Block all other traffic
The firewall checks each packet against these rules top-to-bottom and applies the first match.
The "Stateless" Limitation
These firewalls have no memory. They don't track whether a packet is part of an established connection or a reply to something you sent earlier—each packet is judged in isolation. This makes them fast but limited.
Key Takeaway: Packet filtering firewalls provide basic security by examining IP addresses, ports, and protocols in packet headers without tracking connection state.