an ACL applied to an SVI is stored and never evaluated #1517

Closed
opened 2026-11-15 18:01:06 +00:00 by jaylouisw · 0 comments
Owner

Interface Vlan20: access list 101 applied in is accepted and recorded on the SVI, and then has no effect: a flow from that VLAN to another is identical with and without the ACL, and zero acl-deny events are produced. The same ACL bound to the physical port denies correctly with E_ACL_DENY.

Why it matters: this is the failure mode the project keeps finding - a mechanism that looks right from outside and tells the truth to nobody. Worse, it fails open: a lab testing VLAN isolation passes while the isolation does nothing.

Where: engine/simulator.js _aclCheck / the ingress ACL lookup, which resolves the port ACL but not the SVI binding; engine/acl.js stores the binding.

Suggested fix: resolve the binding on the ingress VLAN interface as well as the ingress port, and - if SVI ACLs are deliberately unsupported - refuse the command by name instead of accepting it. Do not leave it accepted-but-inert.

Found by the w7 intent-check study, probe11.js.

`Interface Vlan20: access list 101 applied in` is accepted and recorded on the SVI, and then has no effect: a flow from that VLAN to another is identical with and without the ACL, and zero acl-deny events are produced. The same ACL bound to the physical port denies correctly with `E_ACL_DENY`. **Why it matters:** this is the failure mode the project keeps finding - a mechanism that looks right from outside and tells the truth to nobody. Worse, it fails *open*: a lab testing VLAN isolation passes while the isolation does nothing. **Where:** `engine/simulator.js` `_aclCheck` / the ingress ACL lookup, which resolves the port ACL but not the SVI binding; `engine/acl.js` stores the binding. **Suggested fix:** resolve the binding on the ingress VLAN interface as well as the ingress port, and - if SVI ACLs are deliberately unsupported - refuse the command by name instead of accepting it. Do not leave it accepted-but-inert. Found by the w7 intent-check study, probe11.js.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#1517
No description provided.