adapt to ipv4 fragmentation changes, use ipaddr 3.0 #88
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
|
this PR includes ipaddr 3 support as well /cc @avsm (I suspect some upper bounds for previous charrua releases are needed) |
hannesm
changed the title
… instead depend on concrete devices
hannesm
added a commit
to hannesm/charrua
that referenced
this pull request
Nov 25, 2020
As observed in mirage#88, the client identifier type was set to 0 (and thus not respecting the client which sent the identifier). This violates RFC6842, which states that the client identifier must be replied with unmodified.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
since mirage/mirage-tcpip#375 was merged, required API changes to dhcp_wire.ml