Fix Dot1Q metadata extraction - #561
Open
Aritra-Das-c-source wants to merge 1 commit into
Open
Conversation
Aritra-Das-c-source
force-pushed
the
fix-dot1q-extract-metadata
branch
from
September 5, 2026 13:28
b9ed3ea to
915bb1d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix Dot1Q::extract_metadata() to determine the next PDU type from the
EtherType stored in the Dot1Q header.
Previously, Dot1Q::extract_metadata() always returned PDU::UNKNOWN as
the next PDU type, even when the EtherType identified a known protocol.
Added a regression test covering Dot1Q containing an IPv4 PDU.
Fixes #558
All 62 tests pass.