Whitelist issue - IRK & Addr added

[Markus]

Hi,

we are developing a custom board based on an NRF51822 and for security reasons are using whitelisting.

So far this worked well with different iOS and Android devices but today I tested with a ZTE Android device (running Android 5.1). When bonding this Android device my whitelist addr_count and irk_count are both 0x01 (no previously bonded devices). And when advertising with whitelisting is supposed to start the device reboots. If I disable whitelisting everything works as expected.

Is there any way to solve this issue without disabling whitelisting? I don't quite understand why both the addres and irk are added to the whitelist? When bonding other devices only addr or irk are added.

I'm using device manager, SDK 11 and softdevice S130.

Thanks for your help

[Markus]

Thanks for your reply.

The ZTE devices uses a private non resolvable address (0x03). And my whitelist shows pp_addrs 0x2002A90, addr_count 0x01, pp_irks 0x2002AB0, irk_count 0x01.

You are correct, that the error handler reboots the device. It seems like the error occurs at the sd_ble_gap_adv_start(&adv_params) call.

Is there anything wrong with the irk or device address?

[FormerMember]

Private non-resolvable addresses are not meant to be used for a longterm form of identification, because they are not resolvable and they will change at a given time interval. It is therefore not really possible to "re-identify" a device using that address type when it has changed its address.

[Markus]

Ok, so is there any other soultion than disabling the whitelist as soon as a device with a private non resolvalbe address was bonded?

[FormerMember]

I have updated my answer with a suggestion.