A frame lost because the spanning tree blocked the only other port is reported as a VLAN problem #1437

Closed
opened 2026-11-11 23:21:33 +00:00 by jaylouisw · 0 comments
Owner

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 from a to b:

s3> show spanning-tree                         s3> show interfaces
Fa0/1   alternate  blocking (traffic dropped)  Fa0/2 ... 1 drop (no egress ports in VLAN 1)

Two surfaces, one frame, two different stories. Fa0/1 is 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 failed ping, so the wrong words reach the report as well as the counter.

What should be true

  1. A refusal by the spanning tree says so, and names the port — the same port show spanning-tree prints as blocking;
  2. a refusal by the port-channel says so (a hairpin is not a VLAN fact either);
  3. the VLAN wording stays where it was always true — a port genuinely outside the VLAN;
  4. the frame is still counted once, not once per blocked candidate;
  5. the payload (drops.byReason) uses the same sentence as the console;
  6. where the reason sits in _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; reverting engine/simulator.js fails 11/24.

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 from `a` to `b`: ``` s3> show spanning-tree s3> show interfaces Fa0/1 alternate blocking (traffic dropped) Fa0/2 ... 1 drop (no egress ports in VLAN 1) ``` Two surfaces, one frame, two different stories. `Fa0/1` **is** 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 failed `ping`, so the wrong words reach the report as well as the counter. ### What should be true 1. A refusal by the spanning tree says so, and names the port — the same port `show spanning-tree` prints as blocking; 2. a refusal by the port-channel says so (a hairpin is not a VLAN fact either); 3. the VLAN wording stays where it was always true — a port genuinely outside the VLAN; 4. the frame is still counted once, not once per blocked candidate; 5. the payload (`drops.byReason`) uses the same sentence as the console; 6. where the reason sits in `_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; reverting `engine/simulator.js` fails 11/24.
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#1437
No description provided.