Private resolvable addresses and unbonded devices

RE: Private resolvable addresses and unbonded devices

Petter Myhre — Thu, 29 Sep 2016 13:17:02 GMT

Np :) If everything is clear, maybe you could accept my answer by clicking the check mark next to it? Thanks.

RE: Private resolvable addresses and unbonded devices

lee.W — Thu, 29 Sep 2016 12:56:18 GMT

Ok, After a bit of research I believe I've got it: There are only really 2 types of address from a connection request point of view: public - this is a fix address which has to be issued by the SIG. random - The random address can be a static type which is randomly generated at power up and changes every time or a private type which still appears random but to a device that has its IRK this address can be resolved to a known device. This makes good sense thank you!

RE: Private resolvable addresses and unbonded devices

Petter Myhre — Thu, 29 Sep 2016 10:54:01 GMT

The address type of the peripheral is irrelevant in regards to if a central can connect to a it or not. What matters is if the peripheral uses a whitelist or not. If it is using a whitelist only connection requests from centrals in it will be accepted. The whitelist can contain static addresses and/or IRKs.

The main point of using a resolvable private address is to achieve privacy. This means that friendly (bonded) device can identify the device, while unfriendly (not bonded) devices cannot.