A trunk's allowed-VLAN list blinds both ends of the cable #1457

Closed
opened 2026-11-12 01:59:31 +00:00 by jaylouisw · 0 comments
Owner

Two switches joined by a trunk. Somebody trims it to the VLAN it is meant to carry:

s1(config-if)# switchport trunk allowed vlan 10
s1# show lldp neighbors
  (none - no LLDP has been heard on any port)

s1# show interfaces Fa0/1
  peer: s2/Fa0/1
  switchport: trunk · native 1 · allowed 10
  1 drop (VLAN 1 not allowed on egress)

The cable is up, show interfaces still names its peer, STP still elects a root — and both ends have gone blind to each other. The only trace is a drop counter on a perfectly healthy port, blaming a VLAN nobody mentioned.

Cause

The announcement goes through the egress VLAN filter in _emitFrame: the LLDPDU is classified into the port's native VLAN (1), the allowed list does not contain it, and the frame is refused.

LLDP is a link protocol, not customer traffic. It is sent untagged to the nearest-bridge multicast group (01:80:c2:00:00:0e) and terminated by the nearest bridge; the allowed-VLAN list decides which switched frames the link carries, not whether its two ends may describe themselves to each other. Trimming a trunk's allowed list is routine, and it should not cost the neighbour table.

What should be true

  1. a trunk whose allowed list excludes its native VLAN still exchanges announcements, in both directions;
  2. the frame leaves untagged, with no VLAN tag on the wire;
  3. the far end records it on the port it arrived on, naming the sender;
  4. the exemption is LLDP only — a customer frame in an excluded VLAN out the same port is still refused with the same VLAN N not allowed on egress, and never reaches the wire;
  5. the announcement is counted as throughput, not as a drop: 1 packets output, no drop line;
  6. a shut port still announces nothing, an already-known neighbour is annotated down: peer shut down rather than forgotten, access ports in any VLAN still advertise, and a default trunk is unchanged.

test/lldp-across-trunk.test.js, 32 checks. Reverting engine/simulator.js fails 16. Neighbours green: lldp 27, show-lldp 23, vlan 59, switchport-mismatch 26, counters-agreement 32, flood-refusal-reason 24, flood-port-state 19, link-state 69, stp-port-state 31.

Two switches joined by a trunk. Somebody trims it to the VLAN it is meant to carry: ``` s1(config-if)# switchport trunk allowed vlan 10 s1# show lldp neighbors (none - no LLDP has been heard on any port) s1# show interfaces Fa0/1 peer: s2/Fa0/1 switchport: trunk · native 1 · allowed 10 1 drop (VLAN 1 not allowed on egress) ``` The cable is up, `show interfaces` still names its peer, STP still elects a root — and both ends have gone blind to each other. The only trace is a drop counter on a perfectly healthy port, blaming a VLAN nobody mentioned. ### Cause The announcement goes through the egress VLAN filter in `_emitFrame`: the LLDPDU is classified into the port's native VLAN (1), the allowed list does not contain it, and the frame is refused. LLDP is a link protocol, not customer traffic. It is sent untagged to the nearest-bridge multicast group (`01:80:c2:00:00:0e`) and terminated by the nearest bridge; the allowed-VLAN list decides which switched frames the link carries, not whether its two ends may describe themselves to each other. Trimming a trunk's allowed list is routine, and it should not cost the neighbour table. ### What should be true 1. a trunk whose allowed list excludes its native VLAN still exchanges announcements, in both directions; 2. the frame leaves **untagged**, with no VLAN tag on the wire; 3. the far end records it on the port it arrived on, naming the sender; 4. the exemption is **LLDP only** — a customer frame in an excluded VLAN out the same port is still refused with the same `VLAN N not allowed on egress`, and never reaches the wire; 5. the announcement is counted as throughput, not as a drop: `1 packets output`, no drop line; 6. a shut port still announces nothing, an already-known neighbour is annotated `down: peer shut down` rather than forgotten, access ports in any VLAN still advertise, and a default trunk is unchanged. `test/lldp-across-trunk.test.js`, 32 checks. Reverting `engine/simulator.js` fails 16. Neighbours green: `lldp` 27, `show-lldp` 23, `vlan` 59, `switchport-mismatch` 26, `counters-agreement` 32, `flood-refusal-reason` 24, `flood-port-state` 19, `link-state` 69, `stp-port-state` 31.
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#1457
No description provided.