fix support for link-local IPv6 addresses #32
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
Signed-off-by: Thomas Stilwell <[email protected]>
sloanyyc
approved these changes
Aug 23, 2023
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.
This PR addresses link-local IPv6 handling in the broker by adding the interface ID (
scope_id) as part of the address string for link-local clients.This fixes the case where the broker receives a packet from a link-local IPv6 address and the reply is dropped due to not specifying which interface to send on.
See https://github.com/RIOT-OS/RIOT/tree/master/examples/emcute_mqttsn#i-see-incoming-messages-in-rsmb-but-no-outgoing-message-seems-to-arrive