-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[zephyr 1.14] Host does not change the RPA #18150
Labels
Comments
joerchan
added a commit
to joerchan/zephyr
that referenced
this issue
Aug 14, 2019
The RPA timer should always be running, even with privacy supported by the controller. In order to select an IRK to generate the private the controller is instructed by provided an identity address. If we want to advertise privately without providing an identity address the host has to set the private address. Fixes: zephyrproject-rtos#18150 Signed-off-by: Joakim Andersson <[email protected]>
carlescufi
pushed a commit
that referenced
this issue
Aug 15, 2019
The RPA timer should always be running, even with privacy supported by the controller. In order to select an IRK to generate the private the controller is instructed by provided an identity address. If we want to advertise privately without providing an identity address the host has to set the private address. Fixes: #18150 Signed-off-by: Joakim Andersson <[email protected]>
joerchan
added a commit
to joerchan/zephyr
that referenced
this issue
Aug 15, 2019
The RPA timer should always be running, even with privacy supported by the controller. In order to select an IRK to generate the private the controller is instructed by provided an identity address. If we want to advertise privately without providing an identity address the host has to set the private address. Fixes: zephyrproject-rtos#18150 Signed-off-by: Joakim Andersson <[email protected]>
nashif
pushed a commit
that referenced
this issue
Aug 15, 2019
The RPA timer should always be running, even with privacy supported by the controller. In order to select an IRK to generate the private the controller is instructed by provided an identity address. If we want to advertise privately without providing an identity address the host has to set the private address. Fixes: #18150 Signed-off-by: Joakim Andersson <[email protected]>
LeiW000
pushed a commit
to LeiW000/zephyr
that referenced
this issue
Sep 2, 2019
The RPA timer should always be running, even with privacy supported by the controller. In order to select an IRK to generate the private the controller is instructed by provided an identity address. If we want to advertise privately without providing an identity address the host has to set the private address. Fixes: zephyrproject-rtos#18150 Signed-off-by: Joakim Andersson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
It happens (about 30%) that Zephyr host does not change the RPA.
To Reproduce
Steps to reproduce the behavior:
To speed up RPA address rotation, set RPA timeout to 30 seconds
CONFIG_BT_RPA_TIMEOUT=30
0. Test using Zephyr bluetooth/shell app for both devices. peripheral (a) - (b) central
1a. bt init
1b. bt init
2a. bt clear all
2b. bt clear all
3a. bt advertise on
3b. bt connect REMOTE_RPA_ADDR (random)
4b. bt security 2
5b. bt disconnect
6. Observe Zephyr peripheral (a) does not change the RPA address
Expected behavior
Zephyr changes it's RPA every CONFIG_BT_RPA_TIMEOUT
Screenshots or console output
Observe RPA rotation that in frames #263 - #289
After the connection, pairing, disconnection
Note the timestamps between LE Set Advertise Enable and LE Enhanced Connection Complete
it's almost 10 minutes and Zephyr does not changed it's RPA address
gap_priv_conn_bi_01_c.btsnoop.log
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: