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
Do you intend to support parsing BGP traffic with some level of encapsulation?
I saw right now the parser assumes that the IP payload is directly encapsulated by the Ethernet frame. In case of a network with VLAN there might be an additional 802.1Q VLAN header before the IP payload.
Supporting this might open deployment options. In our case, we mirrored a port with BGP traffic on an Extreme Network Switch. This mirroring necessarily introduces a 802.1Q encapsulation.
The text was updated successfully, but these errors were encountered:
thank you for message. I will flag your issue as feature request and will head back to it as soon as I'm back from vacation. I guess it won't be a problem to support 802.1Q encapsulation in a future version. As soon as this feature is implemented I will get back to you.
Hi Tobias.
Do you intend to support parsing BGP traffic with some level of encapsulation?
I saw right now the parser assumes that the IP payload is directly encapsulated by the Ethernet frame. In case of a network with VLAN there might be an additional 802.1Q VLAN header before the IP payload.
Supporting this might open deployment options. In our case, we mirrored a port with BGP traffic on an Extreme Network Switch. This mirroring necessarily introduces a 802.1Q encapsulation.
The text was updated successfully, but these errors were encountered: