Firewall Policies
First match wins, in order. A policy is only “applied” after the agent deploys and verifies it.
| # | Name | From → To | Source | Destination | Service | Action | Hits | Status |
|---|---|---|---|---|---|---|---|---|
| 10 | LAN to Internet | lan → wan | lan-net | any | any | accept | 184,213 | applied |
| 20 | LAN DNS to firewall | lan → wan | lan-net | any | dns | accept | 29,811 | applied |
| 30 | Block Telnet egressLOG | lan → wan | lan-net | any | telnet | drop | 42 | applied |
| 40 | IoT cannot reach LANLOG | lan → lan | iot-net | lan-trusted | any | reject | 377 | applied |
| 50 | Guest web only | lan → wan | guest-net | any | web | accept | 0 | pending |
Editing, reordering, and deploy/rollback are available in the local build against the backend API — disabled in this read-only demo.