This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
Don't inspect the DF flag earlier than we need to #1016
Merged
Conversation
This file contains 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
So that LogFrame can include information about the decoded frame beyond the ethernet layer.
|
I've managed to eliminate the DF passing API strangeness. This should perhaps be squashed with dpw@64ac774. Am happy with the rest. |
|
Fine. |
rade
added a commit
that referenced
this pull request
Jun 26, 2015
Don't inspect the DF flag earlier than we need to
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The router extracts the DF flag from a received frame early on and passes it around. But it doesn't use it in any significant way until it reaches the UDP forwarder code. These commits defer extracting it until it is really needed.