Misunderstanding about adertising mode "Whitelist"

RE: Misunderstanding about adertising mode "Whitelist"

Shafy — Fri, 25 Jul 2014 09:19:04 GMT

Hi, Is this issue fixed in SD V6.0 and SDK 5.2 also ? I understand that device_manager_peripheral.c which has the fix is a file for SDk 6.0 and it cant be used in SDk5.2. i have bonded with one android phone, but still another phone is able to connect with the device.

Thanks Shafy

RE: Misunderstanding about adertising mode "Whitelist"

Matt — Thu, 24 Jul 2014 01:56:05 GMT

Patch in SDK6.0, use SD7.0: The issue 1 and 2 are fixed.

RE: Misunderstanding about adertising mode "Whitelist"

Sébastien Despont — Tue, 22 Jul 2014 10:51:41 GMT

Hi Matt, check the reported bugs list for SDK 6.0 : devzone.nordicsemi.com/.../ and let us know if the point 1 or 2 fix the issue.

RE: Misunderstanding about adertising mode "Whitelist"

Matt — Tue, 22 Jul 2014 09:55:48 GMT

Use SDK6.0 and SD7.0, still have this issue.

void advertising_start(void) { uint32_t err_code;

// Initialize advertising parameters (used when starting advertising).
memset(&m_adv_params, 0, sizeof(m_adv_params));

m_adv_params.type        = BLE_GAP_ADV_TYPE_ADV_IND;
m_adv_params.p_peer_addr = NULL;    // Undirected advertisement.
m_adv_params.interval    = APP_ADV_INTERVAL;
m_adv_params.timeout     = APP_ADV_TIMEOUT_IN_SECONDS;
  

ble_gap_whitelist_t  whitelist;
ble_gap_addr_t       * p_whitelist_addr[BLE_GAP_WHITELIST_ADDR_MAX_COUNT];
ble_gap_irk_t        * p_whitelist_irk[BLE_GAP_WHITELIST_IRK_MAX_COUNT];
        
whitelist.addr_count = BLE_GAP_WHITELIST_ADDR_MAX_COUNT;
whitelist.irk_count  = BLE_GAP_WHITELIST_IRK_MAX_COUNT;
whitelist.pp_addrs   = p_whitelist_addr;
whitelist.pp_irks    = p_whitelist_irk;
        
err_code = dm_whitelist_create(&m_app_handle, &whitelist);
APP_ERROR_CHECK(err_code);
        
if ((whitelist.addr_count != 0) || (whitelist.irk_count != 0))
{
    m_adv_params.fp          = BLE_GAP_ADV_FP_FILTER_BOTH;
    m_adv_params.p_whitelist = &whitelist;
    advertising_init(BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED);    
}
else
{
    m_adv_params.fp          = BLE_GAP_ADV_FP_ANY;
    m_adv_params.p_whitelist = NULL;
    advertising_init(BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE);
}


err_code = sd_ble_gap_adv_start(&m_adv_params);
APP_ERROR_CHECK(err_code);

}

RE: Misunderstanding about adertising mode "Whitelist"

Ole Morten — Mon, 28 Apr 2014 11:32:48 GMT

If you have bonded with one of your Android devices, and the device is added to the whitelist, there shouldn't be any such problems. However, if you have problems with this, can you please either post a question or a support case separately, making sure to include your complete code?

RE: Misunderstanding about adertising mode "Whitelist"

julian — Thu, 24 Apr 2014 18:28:07 GMT

for same issue, I set #define BLE_BONDMNGR_MAX_BONDED_CENTRALS 1 and follow same


APP_ERROR_CHECK(ble_bondmngr_whitelist_get(&whitelist));
            if ((whitelist.addr_count != 0) || (whitelist.irk_count != 0)) {
                adv_params.fp          = BLE_GAP_ADV_FP_FILTER_CONNREQ;
                adv_params.p_whitelist = &whitelist;                
                advertising_init(BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED);
advertising_init(BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED);

but two of my android phone are able to connect to the nrf51822, and I am using sdk 5.2 and SD 6.0 release.

anything I am missing here?

RE: Misunderstanding about adertising mode "Whitelist"

Sébastien Despont — Mon, 09 Dec 2013 08:38:47 GMT

Hi Ole,

I have tested with SDK5 and softdevice 6 and there is no longer problem.

Best regards

RE: Misunderstanding about adertising mode "Whitelist"

Ole Morten — Fri, 06 Dec 2013 13:51:02 GMT

Just in case you've missed it, a new release is now out, that includes the fix for this issue.

I'd also be happy if you could accept my answer above, since it seems to answer the original question here. :-)

RE: Misunderstanding about adertising mode "Whitelist"

Sébastien Despont — Thu, 21 Nov 2013 13:09:38 GMT

Hi Ole,

I confirm that if I pair the dongle-"Matser control panel" first, the iPhone cannot be connected due to whitelist restriction. But, of course, the opposite doesn't work because of IRK whitelist problem you mentionned.

RE: Misunderstanding about adertising mode "Whitelist"

Sébastien Despont — Thu, 21 Nov 2013 09:47:03 GMT

I am glad to read your comment. So I really looking forward to testing the next Softdevice version.

I have just tested to pair the dongle-"Master emulator" first, but I still have similar problem. I can also connect and pair the second iPhone (it means a third master) and pair it.

RE: Misunderstanding about adertising mode "Whitelist"

Ole Morten — Thu, 21 Nov 2013 09:25:09 GMT

The problem is also there in the alpha, which is why I recommended you to test with the final when it is available, which have fixed this issue. With 5.2.1 and 6.0.0-alpha I can see similar problems to the ones you report, so I'm hopeful that the final 6.0.0 release will fix the problem for you as well.

If you have a Master Emulator dongle, you should be able to bond your device with the Master Control Panel, and then see that your iPhone is not able to connect.

RE: Misunderstanding about adertising mode "Whitelist"

Sébastien Despont — Thu, 21 Nov 2013 09:16:37 GMT

Dear Ole Morten,

Thanks for your reply. I have just tested to upgrade the Softdevice to version 6.0.0-1 alpha but the problem persists. :(

After pairing the first iPhone, I am still able to connect to the nRF51822 with the second one and perform a pairing. It seems that the whitelist has no effect with IOS. But unfortunately, I can't test with other kind of central.

By the way, I am using the very last version of the SDK 4.4.2.

Can you confirm that you don't have this kind of problem on your side?

I know that it is another problem and I don't want to interfere with the main purpose of this question, but after pairing the second iPhone, the first one is no longer able to read secure characteristics (no problem with non-secure ones) of the nRF51822. I will open a second question on this topic when the whitelist problem will be fixed.

Best regards

RE: Misunderstanding about adertising mode "Whitelist"

Ole Morten — Wed, 20 Nov 2013 13:54:55 GMT

Your code looks very reasonable, and I suspect that what you see is a known issue with S110 version 5.2.1. As you can see in its release notes, it says: "On a bonded device using IRK based whitelisting, the white list is not effective until after the first advertising event (NRFFOETT-515, DRGN-3141)"

There isn't any workaround you can do from your application for this, except to make sure to upgrade to the final 6.0.0 as soon as it's available (should be very soon).

Apart from this bug, you are correct that even when using whitelisting all Centrals will be able to see the device, the only effect of the whitelist is that the Peripheral will not accept the Connection request from other Centrals than the ones it has in its whitelist.