Mac address in whitelist

RE: Mac address in whitelist

Kazi Afroza Sultana — Tue, 08 Feb 2022 09:00:09 GMT

You are welcome. Yes, Let us know your result. 🙂

Best Regards,

Kazi Afroza Sultana

RE: Mac address in whitelist

Daniela_A — Mon, 07 Feb 2022 21:36:11 GMT

Hello,

Thank you for your suggestion. I will test it and see what happens

RE: Mac address in whitelist

Kazi Afroza Sultana — Wed, 02 Feb 2022 08:05:54 GMT

Hello Daniela,

I talked to our team. Peer count is an input parameter to the pm_whitelst_set() function, not an output. You can use pm_peer_count() to get the number of bonds on the device. Then you can check if the count gets incremented after adding the new peer device.

Best Regards,

Kazi Afroza Sultana

RE: Mac address in whitelist

Daniela_A — Mon, 31 Jan 2022 21:29:15 GMT

Hello Kazi,

I was able to add the MAC addresses using sd_ble_gap_whitelist_set() successfully. The peers are recognized and the central proceeds to establish a connection.

However, I would like the addresses to be written in the flash with the others using the peer manager. I am using parts of the code someone else wrote here in this forum. I successfully add the address using pm_peer_new(); however, when I want to set the whitelist using pm_whitelist_set(), it is not working because it says that the peer count = 0.

PS: I am using the code shown in the answer that contains the solution

RE: Mac address in whitelist

Daniela_A — Fri, 28 Jan 2022 15:53:47 GMT

Hello Kazi,

Thanks for your support. I will try implementing that and if I have any issues, I will let you know.

Good day

RE: Mac address in whitelist

Kazi Afroza Sultana — Fri, 28 Jan 2022 14:34:48 GMT

Hello Daniela,

It is possible as long as the peripheral uses a static address type. You can populate the whitelist in the application. However, there are no examples for it. The SDK examples populates the whitelist via the peer manager which gets the information from the bond table.

The softdevice calls for updating the whitelist and it is done by sd_ble_gap_whitelist_set() function (https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v3.0.0/group___b_l_e___g_a_p___f_u_n_c_t_i_o_n_s.html?cp=4_7_3_9_2_1_2_34#gacdd2dd570000368dd5c29d799c198779 )

pp_wl_addrs: Pointer to a whitelist of peer addresses, if NULL the whitelist will be cleared.

len: Length of the whitelist, maximum length is defined by BLE_GAP_WHITELIST_ADDR_MAX_COUNT

This function sets the active whitelist in the SoftDevice. The things to be noted;- Only one whitelist can be used at a time and the whitelist is shared between the BLE roles. The whitelist can not be set if a BLE role is using the whitelist. If an address is resolved using the information in the device identity list, then the whitelist filter policy applies to the peer identity address and not the resolvable address sent on air.

You can look at the id_manager.c::im_whitelist_set() function to see how the function is used by the peer manager.

Fell free to ask if you have further queries.

Have a nice weekend.

Best regards,

Kazi Afroza Sultana