Fix for non-confirmable responses #763
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
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.
Previously all non-confirmable messages sent out by the device are considered requests, but they can be responses. This, combined with enabling the replay protection, caused ETS download to fail.
e.g. When ETS sends a NON request using a new unsynchronised access token, the device should send a non-confirmable RESPONSE with 4.01 + echo; But before the fix, it's sending a non-confirmable REQUEST with 4.01 + echo, which ETS cannot handle
Also a fix so that IPV6 multicast destination addresses are created using the recipient GRPID instead of publisher