A frame lost because the spanning tree blocked the only other port is reported as a VLAN problem #1437
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1437
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?
A frame lost because the spanning tree blocked the only other port is reported as a VLAN problem — on the same box that already says the tree is dropping it.
Measured on a triangle
a -- s1 -- s2 -- s3 -- s1(s3 a dead end, its port back to s2 blocked), one ping fromatob:Two surfaces, one frame, two different stories.
Fa0/1is in VLAN 1; the tree is why it cannot carry._forwardL2()builds its flood candidates and filters them — blocked by the tree, outside the VLAN, far member of the ingress port-channel — and when nothing was left it emitted one sentence whatever the refusal had been:no egress ports in VLAN <vid>.The counter is the one an operator acts on, so the VLAN gets re-checked and the VLAN was never the problem. The sentence is also what
_lastDiscard()hands a failedping, so the wrong words reach the report as well as the counter.What should be true
show spanning-treeprints as blocking;drops.byReason) uses the same sentence as the console;_lastDiscard()does not move — naming the tree does not make it a different kind of cause, and a block on a redundant path is not the reason a ping failed.Evidence:
test/flood-refusal-reason.test.js, 24 checks; revertingengine/simulator.jsfails 11/24.