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
An 802.1ad (EthernetPacketType.ProviderBridging) VLAN tag is just an 802.1Q (EthernetPacketType.VLanTaggedFrame) VLAN tag with a TPID value of 0x88a8 rather than 0x8100.
When EthernetPacket.ParseNextSegment() is parsing the Ethernet payload data to set the PayloadPacket property, it creates an Ieee8021QPacket object for an 802.1Q tag, but not for an 802.1ad tag, thus the PayloadPacket ends up being set to null.
I suggest setting the PayloadPacket to an Ieee8021QPacket for an 802.1ad tag. Maybe even create a new Ieee8021ADPacket class that derives from Ieee8021QPacket.
The text was updated successfully, but these errors were encountered:
HI @rlebeau. Thank you for reporting the issue. I'm not sure anyone will pick up fixing this, however we do wish it were fixed. If you do end up fixing the issue in Packet.Net could you open a pull request with a test that fails and the code fix that corrects it?
An 802.1ad (
EthernetPacketType.ProviderBridging
) VLAN tag is just an 802.1Q (EthernetPacketType.VLanTaggedFrame
) VLAN tag with aTPID
value of 0x88a8 rather than 0x8100.When
EthernetPacket.ParseNextSegment()
is parsing the Ethernet payload data to set thePayloadPacket
property, it creates anIeee8021QPacket
object for an 802.1Q tag, but not for an 802.1ad tag, thus thePayloadPacket
ends up being set tonull
.I suggest setting the
PayloadPacket
to anIeee8021QPacket
for an 802.1ad tag. Maybe even create a newIeee8021ADPacket
class that derives fromIeee8021QPacket
.The text was updated successfully, but these errors were encountered: