nimble/host: Enable address resolution if IRK is the same #2043
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
Address resolution should be enabled in case of setting same IRK. It should not be assumed it is still enabled from last IRK set as controller might have beed HCI reseted (for example with host stop/start). Otherwise a central peer with RPA will fail to connect.
guy-m
force-pushed
the
guym/addr_res_enable_same_irk
branch
from
188024f to
57f2976
Compare
|
Hi, Please check if #2068 fix this issue for you. After HCi reset, resolving list is cleared anyway and we should have setup all from start, while that didn't happen was due to missing cleanup on host stop (fixed in 2068) |
|
Hi, |
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.
Address resolution should be enabled in case of setting same IRK.
It should not be assumed it is still enabled from last IRK set as host can disable it with command or send HCI reset to controller (for example with host stop/start) which disabled it.
Otherwise a central peer with RPA will fail to connect.