Routing on a firewall: tables, priorities and policy routes
▶ Start the interactive lesson
Burrow gets a second internet line. Traffic still all goes out the first one, and one branch's replies vanish entirely. Maya pulls up the routing table: "Firewalls route just like routers. They also check that a reply would come back the same way it left, and that's what's biting us."
Key points
- Route choice: the most specific prefix wins first; then lower administrative distance; then vendor tie-breakers like priority/metric. Equal routes can share load with ECMP.
- Route monitoring / tracking pings a target through a link and withdraws the route if it fails, so a "link up but internet dead" line stops attracting traffic.
- Policy-based routing sends traffic by source, app or port rather than destination, e.g. guest Wi-Fi out the cheap line. SD-WAN is the smarter, health-aware version.
- Anti-spoofing / reverse path checks drop packets arriving on an interface the firewall wouldn't use to reach their source. Great against spoofing, but surprising with asymmetric routing.
- Firewalls also speak OSPF and BGP, can redistribute between them, and can hold several separate routing tables (one per customer or segment).
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →