Packet Runner.
Route packets through a tiny network before the queue backs up. Read the policy, choose the right egress, and keep one very impatient user from closing the tab. Built on the shared cb-lab-02 Cloud Bridge profile — an isolated lab with no WAN uplink.
One router. One queue. One very impatient user.
Every packet wants an egress. You have four choices: LAN 1, DMZ, SERVICES, or DROP. The policy panel is the truth. Kalin's marked packets have a five-second timer, and the queue only holds eight.
Router
Loading the shared Bridge profile…
Policy
Router profile source: ASCS Cloud Bridge cb-lab-02 · interface and rule names follow the Bridge config schema. The lab's wan1 interface is down; transit1 is a simulated internet segment used only for NAT practice.
Lab policy
Queue backed up.
Same shared cb-lab-02 profile for every operator. No customer traffic, no WAN, no real firewall changes.