an ACL applied to an SVI is stored and never evaluated #1517
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1517
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Interface Vlan20: access list 101 applied inis 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 withE_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.jsstores 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.