Central Connection Establishment with Private Peer (Resolvable Random Private Address)

RE: Central Connection Establishment with Private Peer (Resolvable Random Private Address)

Adrian B. — Wed, 22 Mar 2023 07:19:00 GMT

Hi Susheel,

Thanks for your answer and I am sorry for my late response.

I the above code snippet I tried to add in the trusted list the IRK of the peripheral without making any bonding (pairing procedure) prior. In the meantime, I understood that this is not the right way for making a connection. As you mention this information are stored in persistent memory when bonding is done. This could be handled automatically by the peer_manager library if it is used.

I think we can close this case.

Thank you very much.

Adrian

RE: Central Connection Establishment with Private Peer (Resolvable Random Private Address)

Susheel Nuguru — Mon, 20 Mar 2023 13:15:45 GMT

It is a bit difficult to understand why this error is thrown without understanding the context of when you are trying to do this and the peer info. Normally the information is got from the persistent memory which is saved when bonding is done. Since you are manually building this struct for ble_gap_id_key_t, I cannot validate what is correct and wrong data.

Can you print this data when the device bonding is done so that we can match that data with what you are trying to set?

RE: Central Connection Establishment with Private Peer (Resolvable Random Private Address)

Susheel Nuguru — Fri, 17 Mar 2023 10:43:28 GMT

I am sorry, I was not able to look into this today, I will look into your code snippet on Monday and come back to you with my inputs.