mirror of
https://github.com/logicog/RTLPlayground.git
synced 2026-09-02 15:02:51 +08:00
d00f
0160b430f4
The note said a blocked port drops frames the CPU injects into it and so cannot send BPDUs of its own. Hardware says otherwise, and it matters, because that sentence is the reason one would go looking for a way to let control frames out of a blocked port when there is nothing to fix there. Held a two port group in blocking and watched from the neighbour. Our BPDUs kept leaving it, 27 of them with a largest gap of 2.00 s, which is the hello interval with nothing missed. Pings across the same port stopped dead for 11.63 s in one unbroken gap, so data really is held. In the same window the neighbour sent 74 frames with a largest gap of 1.04 s while our receive counter for them moved by 2, and the port stayed in its trunk throughout, so nothing in the aggregation code was discarding them.