dc4d63e97b
The address could have changed. The issue linked (and bsim test in previous commit) shows a scenario where that could happen: - we start scanning, host will use NRPA - we start advertising, host will use identity address - a device connects (as a central) -> advertising resume fails for some unrelated reason - another device connects (as a peripheral) - the central device disconnects, we resume scanning - the peripheral disconnects, the stack resumes advertising -> but it mistakenly advertises using the NRPA set by the scanner Fixes #52059 . Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| audio | ||
| common | ||
| controller | ||
| crypto | ||
| host | ||
| mesh | ||
| services | ||
| shell | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.adv | ||
| Kconfig.iso | ||