Firewall troubleshooting: follow the packet, prove the drop
▶ Start the interactive lesson
Ticket: "Warehouse scanners can't reach the stock server since last night's change." Everyone blames the firewall. Maya says the firewall is also the best witness. "Logs first. Then simulate the packet. Then capture the real one. By the end we'll know if it's even reaching us."
Key points
- Know the packet flow: arrive on an interface → existing session? → routing lookup → NAT → policy → inspection → out. Each stage has its own reason to drop.
- Tool 1: logs (traffic and deny logs, filtered by source/destination). Tool 2: the session table (is there a session? which policy? is NAT applied?). Tool 3: simulate a packet through the policy engine to see which rule, route and NAT it would hit.
- Tool 4: packet capture on ingress and egress interfaces proves whether the packet arrives and leaves. Tool 5: debug / trace walks a real packet through each internal stage and names the reason it was dropped. Always filter debugs and switch them off afterwards.
- Tool 6: drop counters show global reasons (spoofing, no route, bad TCP state). Also check resources (CPU, memory, session limits), licences and recent changes.
- Method: define the exact flow (source, destination, port, time), test, change one thing, retest, write it up.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →