Add support for Client Link-Layer Address Option #373
Merged
Conversation
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
RFC6939 specifies a client option to relay the link-layer address of the original client in the relayed message. This commit adjusts the OOB plugin to first try and read the address from that option and falls back to the old EUI64 parsing when that fails. It should be noted that the EUI64 parsing does not work if the client has IPv6 privacy extensions enabled as the server can not distinguish between EUI64 and and a random IPv6 host address. See: https://www.rfc-editor.org/rfc/rfc6939
Member
|
Nice! |
damyan
approved these changes
Nov 13, 2025
hardikdr
added
the
area/metal-automation
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.
RFC6939 specifies a client option to relay the link-layer address of the original client in the relayed message. This commit adjusts the OOB plugin to first try and read the address from that option and falls back to the old EUI64 parsing when that fails.
It should be noted that the EUI64 parsing does not work if the client has IPv6 privacy extensions enabled as the server can not distinguish between EUI64 and and a random IPv6 host address.
See: https://www.rfc-editor.org/rfc/rfc6939
Fixes #374