Fail to pair more than one device

RE: Fail to pair more than one device

kchuva — Thu, 26 Dec 2013 09:03:17 GMT

Hi,

I have the same problem. When I try bonding from second device nRF51822 return "NRF_ERROR_FORBIDDEN" from on_auth_status method ble_bondmngr.c. I think that's happend because the Encryption Diversifier param from m_master equal with masters from database.


if (INVALID_MASTER_HANDLE == m_master.bond.master_handle)
{
    uint32_t err_code = master_find_in_db(m_master.bond.master_id_info.div);

    if (err_code == NRF_SUCCESS)
    {
        // Possible DIV Collision indicate error to application,
        // not storing the new LTK
        err_code = NRF_ERROR_FORBIDDEN;
    }
}

Why "div" param sended to mastter_find_in_db method from m_master? I think it must sended from new master info which stored in p_auth_status. Otherwise, we always find in db with old "div" param because it isn't updating.

RE: Fail to pair more than one device

Ole Morten — Fri, 22 Nov 2013 11:46:14 GMT

Unfortunately, I can't quite remember what I thought when I wrote that... :-P

However, my best guess is that my point was that if you always are open to receive connections from all Central devices, you may be connected to by a Central you don't actually want to be connected to. So depending on how you intend your device to be used, you should put some thought into these problems, and make sure that things work as you want to.

RE: Fail to pair more than one device

Jamie — Fri, 22 Nov 2013 01:06:19 GMT

Hi Ole,

Can you elaborate more on what you mean above by, "If you always want to be connectable with new devices, you should not use whitelisting, but this might not always give desirable behavior." What undesirable behavior might arise?

Thanks, Jamie

RE: Fail to pair more than one device

Ole Morten — Fri, 15 Nov 2013 12:22:18 GMT

Whitelisting based on address will not work with iOS, since it uses resolvable addresses, but whitelisting based on Identity Resolving Key works, even with resolvable addresses.

Unfortunately, I'm still not able to replicate the original problem reported here, no matter if I use 4.4.1 or 4.4.2. On which file and line do you get this error?

RE: Fail to pair more than one device

Sébastien Despont — Thu, 14 Nov 2013 21:15:35 GMT

Hi, I read somewhere that the whitelisting mode is not working with IOS because the address change randomly. So, after some times, the IOS app will not be able to be connected to your device anymore. Just check before having troubles with your product. Perhaps some good guy from Nordic could add useful comment on this comment?

RE: Fail to pair more than one device

Henry Wong — Thu, 14 Nov 2013 08:39:47 GMT

The error appear when I disconnect currently connected iPhone and wait for 30s, then pair another new iPhone. After I press "accept pairing", nRF51822 will reset due to "NRF_ERROR_FORBIDDEN".

I have this problem when I using SDK v.4.4.1. Fortunately, this error no longer appear after upgrading to v.4.4.2.

RE: Fail to pair more than one device

Ole Morten — Tue, 12 Nov 2013 17:51:36 GMT

From which method exactly do you get the FORBIDDEN error?

RE: Fail to pair more than one device

Henry Wong — Tue, 05 Nov 2013 05:27:14 GMT

Thanks for your reply, but the problem still cannot be solved. I have wait for whitelist advertising timeout to pair a new iPhone. However, it always give out the error "NRF_ERROR_FORBIDDEN". I need to power reset the nRF51822 in order to get successfully pairing for the new iPhone.

RE: Fail to pair more than one device

Ole Morten — Mon, 04 Nov 2013 13:56:57 GMT

When the keyboard application has been bonded with something, it will advertise with whitelist first, with a 30 s timeout. As long as it uses the whitelist, it will not be connectable for other devices, giving the behavior you describe. However, after this 30 s timeout, new devices should be able to connect.

If you always want to be connectable with new devices, you should not use whitelisting, but this might not always give desirable behavior. You should therefore take some care to make sure you cover the use cases you want.