Firewall building blocks: modes, interfaces and zones
▶ Start the interactive lesson
Burrow's new head office firewall arrives in a box. Before a single rule exists, Maya asks three questions: "Will it route between networks or sit invisibly in a cable? Which ports become which zones? And is it there to block or only to watch?" Get these wrong and every later policy is built on…
Key points
- Routed (Layer 3) mode is the default: each interface has an IP, the firewall is the gateway between subnets, and it can do NAT, routing and VPNs. Transparent (Layer 2) mode or a virtual wire drops the firewall into an existing link with no IP changes; it inspects but is not a routing hop.
- Inline vs passive. Inline means traffic flows through the firewall, so it can block. Passive / tap means it gets a copy (SPAN or tap port), so it can only detect and alert. Passive is a safe way to trial IPS before going inline.
- Interfaces you'll meet: physical ports, VLAN sub-interfaces (one cable, many networks), aggregates (several links bundled with LACP for bandwidth and redundancy), tunnel interfaces for VPNs, loopbacks, and a dedicated management port kept off the data path.
- A zone groups interfaces that share a trust level (inside, outside, DMZ, guest). Policies are written zone-to-zone, so adding a new LAN port to "inside" doesn't mean rewriting rules.
- Under the hood a firewall has a management plane (GUI, CLI, logs, updates) and a data plane (forwarding and inspection). A busy GUI shouldn't slow traffic, and a traffic flood shouldn't lock you out of management.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →