You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring an access-interface with QinQ enabled, I would expect the rx-bps-l2 bandwidth in session statistics to include the S-VLAN as well as the FCS, but it's not included (maybe because it's stripped by the network card?)
I configured a packet-length of 128b with PPPoverL2TP, so that the l2-size on access-interface would be: Ethernet (14) + QinQ (8) + PPP (8) + Payload (128) + FCS (4) = 162b. However, BNG Blaster reports only 154b. The same value as in the capture file.
The stats are based on the length of the packet as received from driver, which might be without offloaded most outer VLAN and FCS. But I could provide a configuration option to adjust the packet stats by N byte per packet if this helps?
Describe the bug
When configuring an access-interface with QinQ enabled, I would expect the
rx-bps-l2
bandwidth in session statistics to include the S-VLAN as well as the FCS, but it's not included (maybe because it's stripped by the network card?)I configured a packet-length of 128b with PPPoverL2TP, so that the l2-size on access-interface would be:
Ethernet (14) + QinQ (8) + PPP (8) + Payload (128) + FCS (4) = 162b
. However, BNG Blaster reports only 154b. The same value as in the capture file.I know that it's a matter of faith, whether FCS is part of a L2-bandwidth, however other testing solutions sees the FCS as part of the L2 bandwidth: https://support.spirent.com/SC_KnowledgeView?id=FAQ20004
To Reproduce
Version (
bngblaster -v
):JSON configuration:
Screenshots
The text was updated successfully, but these errors were encountered: