How to use public-addr and non-resolvable-addr on nrf connect SDK

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Mon, 27 Feb 2023 22:53:50 GMT

OK.Thanks.

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Mon, 27 Feb 2023 19:05:16 GMT

No, you can use a public address for advertising. And that works with some APIs in nRF Connect SDK 2.2.0, so for instance if you just call bt_ctlr_set_public_addr() before bt_enable() in the beacon sample, it works out of the box. However you cannot create a public ID with br_id_create(), which is what I was referring to in my previous post.

I was wrong about public address in extended advertising, though. That should work, but does not due to a bug. This is fixed in this PR.

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Sun, 26 Feb 2023 04:47:21 GMT

Really?

So I can't use public addr for advertising?

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Wed, 22 Feb 2023 08:51:35 GMT

Hi,

It is not allowed to use a public identity address here, only a static random one. That is enforced by the stack. You can see an example of making a static random identity and using that here (which is your sample slightly modified):

/* main.c - Application main entry point */

/*
 * Copyright (c) 2015-2016 Intel Corporation
 *
 * SPDX-License-Identifier: Apache-2.0
 */

#include <zephyr/types.h>
#include <stddef.h>
#include <zephyr/sys/printk.h>
#include <zephyr/sys/util.h>

#include <zephyr/bluetooth/bluetooth.h>
#include <zephyr/bluetooth/hci.h>
#include <sdc_hci_vs.h> 
#include <mpsl_timeslot.h>
#include <mpsl.h>
#include <hal/nrf_timer.h>

static void adv_sent(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_sent_info *info);


static struct bt_le_adv_param adv_param = {
	.options	= BT_LE_ADV_OPT_USE_IDENTITY,
	.interval_min	= 0x00a0,
	.interval_max	= 0x00a0,
};

static const struct bt_le_ext_adv_cb adv_cb = {
	.sent			= adv_sent,
};

static const uint8_t ManufData[] = { 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, 0x99, 0xAA, 0xBB, 0xCC, 0xDD, 0xEE, 0xFF};
static const struct bt_data bdata[1] = {
	BT_DATA(0xFF, ManufData, sizeof(ManufData))
};

static struct bt_le_ext_adv* ext_adv0;
static struct bt_le_ext_adv_start_param adv_start_param = { 0, 0 };

static void adv_sent(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_sent_info *info)
{
}

static int set_addr(void)
{
	int id;

	static bt_addr_le_t addr = {
		.type		= BT_ADDR_LE_RANDOM,
		.a.val		= {0xba, 0xde, 0xba, 0x11, 0xca, 0xfe},
	};

	id = bt_id_create(&addr, NULL);
	if (id < 0) {
		printk("Creating new ID failed (%d)\n", id);
	}
	else
	{
		printk("Id created: %i\n", id);
	}

	return id;
}

void main(void)
{
	int err;
	int id;

	printk("Starting Scanner/Advertiser Demo\n");

	/* Initialize the Bluetooth Subsystem */
	err = bt_enable(NULL);
	if (err) {
		printk("Bluetooth init failed (err %d)\n", err);
		return;
	}

	printk("Bluetooth initialized\n");

	id = set_addr();

	adv_param.id = id;

	err = bt_le_ext_adv_create(&adv_param, &adv_cb, &ext_adv0);
	if (err) {
		printk("adv create failed (err %d)\n", err);
		return;
	}

	err = bt_le_ext_adv_set_data(ext_adv0, bdata, 1, NULL, 0);
	if (err) {
		printk("adv set data failed (err %d)\n", err);
		return;
	}

	err = bt_le_ext_adv_start(ext_adv0, &adv_start_param);
	if (err) {
		printk("Advertising failed to start (err %d)\n", err);
		return;
	}


	do {
		k_sleep(K_MSEC(400));

	} while (1);
}

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Sun, 19 Feb 2023 06:27:02 GMT

Sorry.
Projects cannot be provided.
Instead, it only provides main.c/proj.conf.

main.c

/* main.c - Application main entry point */

/*
 * Copyright (c) 2015-2016 Intel Corporation
 *
 * SPDX-License-Identifier: Apache-2.0
 */

#include <zephyr/types.h>
#include <stddef.h>
#include <zephyr/sys/printk.h>
#include <zephyr/sys/util.h>

#include <zephyr/bluetooth/bluetooth.h>
#include <zephyr/bluetooth/hci.h>
#include <sdc_hci_vs.h> 
#include <mpsl_timeslot.h>
#include <mpsl.h>
#include <hal/nrf_timer.h>

static void adv_sent(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_sent_info *info);


static struct bt_le_adv_param adv_param = {
	.id				= BT_ID_DEFAULT,
	.options		= BT_LE_ADV_OPT_USE_IDENTITY,
	.interval_min	= 0x00a0,
	.interval_max	= 0x00a0,
};

static const struct bt_le_ext_adv_cb adv_cb = {
	.sent			= adv_sent,
};

static const uint8_t ManufData[] = { 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, 0x99, 0xAA, 0xBB, 0xCC, 0xDD, 0xEE, 0xFF};
static const struct bt_data bdata[1] = {
	BT_DATA(0xFF, ManufData, sizeof(ManufData))
};

static struct bt_le_ext_adv* ext_adv0;
static struct bt_le_ext_adv_start_param adv_start_param = { 0, 0 };

static bt_addr_le_t bdaddr0 = {
	.type = BT_ADDR_LE_RANDOM,
	.a = {
		.val = {0xC1, 0x11, 0x11, 0x11, 0x11, 0xC1},
	}
};

static bt_addr_le_t bdaddr1 = {
	.type = BT_ADDR_LE_RANDOM,
	.a = {
		.val = {0xC2, 0x22, 0x22, 0x22, 0x22, 0xC2},
	}
};

static void set_public_addr(void)
{
	uint8_t pub_addr[BT_ADDR_SIZE] = {0xba, 0xde, 0xba, 0x11, 0xca, 0xfe};
	bt_ctlr_set_public_addr(pub_addr);
}

static void adv_sent(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_sent_info *info)
{
}

void main(void)
{
	int err;

	printk("Starting Scanner/Advertiser Demo\n");

	set_public_addr();

	/* Initialize the Bluetooth Subsystem */
	err = bt_enable(NULL);
	if (err) {
		printk("Bluetooth init failed (err %d)\n", err);
		return;
	}

	printk("Bluetooth initialized\n");

	err = bt_le_ext_adv_create(&adv_param, &adv_cb, &ext_adv0);
	if (err) {
		printk("adv create failed (err %d)\n", err);
		return;
	}

	err = bt_le_ext_adv_set_data(ext_adv0, bdata, 1, NULL, 0);
	if (err) {
		printk("adv set data failed (err %d)\n", err);
		return;
	}

	err = bt_le_ext_adv_start(ext_adv0, &adv_start_param);
	if (err) {
		printk("Advertising failed to start (err %d)\n", err);
		return;
	}


	do {
		k_sleep(K_MSEC(400));

	} while (1);
}

proj.conf

CONFIG_FPU=y
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_BROADCASTER=y
CONFIG_BT_OBSERVER=y
CONFIG_BT_EXT_ADV=y
CONFIG_BT_EXT_ADV_MAX_ADV_SET=4
CONFIG_BT_PER_ADV=y
CONFIG_BT_PER_ADV_SYNC=y
CONFIG_BT_PER_ADV_SYNC_MAX=64
CONFIG_BT_ASSERT=n
CONFIG_BT_ASSERT_VERBOSE=n
CONFIG_BT_DEVICE_NAME="EXBeacon"
CONFIG_BT_ID_MAX=5
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
CONFIG_BT_CTLR_PHY_2M=y
CONFIG_BT_CTLR_PHY_CODED=y
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_CTLR_ADV_SET=4
CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=191
CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX=200
CONFIG_MPSL_TIMESLOT_SESSION_COUNT=1
CONFIG_NRFX_GPIOTE_NUM_OF_EVT_HANDLERS=2
CONFIG_THREAD_CUSTOM_DATA=y
CONFIG_BT_DEBUG_NONE=y
CONFIG_BT_RECV_WORKQ_SYS=y
CONFIG_BOOT_BANNER=n
CONFIG_ASSERT_VERBOSE=n
CONFIG_CONSOLE=n
CONFIG_USE_SEGGER_RTT=n
CONFIG_SERIAL=n
CONFIG_UART_CONSOLE=n
CONFIG_CPLUSPLUS=y
CONFIG_STD_CPP17=y
CONFIG_EVENTS=y
CONFIG_NRFX_WDT0=y
CONFIG_NRFX_GPIOTE_NUM_OF_EVT_HANDLERS=4

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Wed, 15 Feb 2023 11:37:42 GMT

Hi,

Can you share a minimal but complete example that does this so that I can test your exact code on my end?

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Mon, 13 Feb 2023 16:01:04 GMT

My Code (simply)

static void set_public_addr(void)
{
	uint8_t pub_addr[BT_ADDR_SIZE] = {0xba, 0xde, 0xba, 0x11, 0xca, 0xfe};
	bt_ctlr_set_public_addr(pub_addr);
}

static struct bt_le_adv_param adv_param = {
	.id				= BT_ID_DEFAULT,
	.options		= BT_LE_PER_ADV_OPT_NONE,
	.interval_min	= 0x00a0,
	.interval_max	= 0x00a0,
};

main()
...
	set_public_addr();
	bt_enable(NULL);
	bt_le_ext_adv_create(&adv_param, &adv_cb, &ext_adv0);
	bt_le_ext_adv_set_data(ext_adv0, bdata, 1, NULL, 0);
	bt_le_ext_adv_start(adv, &adv_start_param);
...

If adv_param.options = BT_LE_PER_ADV_OPT_NONE
Result
001845.151 37 ___ 15:0B:7D:17:CF:B9 -45 10FF112233445566778899AABBCCDDEEFF
(non resolvable private address)

If adv_param.options = BT_LE_ADV_OPT_USE_IDENTITY
Result
001962.104 37 ___ xx:xx:xx:xx:xx:xx -40 10FF112233445566778899AABBCCDDEEFF
(xx is FICR.DEVICEADDR (Random Static Address))

what i want
BA:DE:BA:11:CA:FE 10FF112233445566778899AABBCCDDEEFF
(public address)

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Thu, 09 Feb 2023 17:19:21 GMT

I am still confused. What is the expected result? And what is the actual result? Please elaborate.

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Thu, 09 Feb 2023 14:54:21 GMT

I try,

bt_le_adv_param.id=0 / bt_le_adv_param.options=BT_LE_PER_ADV_OPT_NONE
BDADDR=non-resolvable-private address

bt_le_adv_param.id=0 / bt_le_adv_param.options=BT_LE_ADV_OPT_USE_IDENTITY
BDADDR=random static address (FICR.DEVICEADDR)

call bt_ctlr_set_public_addr() before bt_enable()
bt_le_adv_param.id=0 / bt_le_adv_param.options=BT_LE_PER_ADV_OPT_NONE
BDADDR=non-resolvable-private address

call bt_ctlr_set_public_addr() before bt_enable()
bt_le_adv_param.id=0 / bt_le_adv_param.options=BT_LE_ADV_OPT_USE_IDENTITY
BDADDR=random static address (FICR.DEVICEADDR)

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Thu, 09 Feb 2023 13:57:48 GMT

Good to hear you got NRPA working. Regarding public address I am not sure I understand the issue now. Can you elaborate a bit? Exactly what to do you do, and exactly how does it fail?

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Thu, 09 Feb 2023 13:12:55 GMT

OK.

About NRPA solved. Simply not specifying BT_LE_ADV_OPT_USE_IDENTITY made it a non-resolvable-addr.

But, As for the public address setting, it doesn't work.
Calling bt_ctlr_set_public_addr still NRPA.

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Thu, 09 Feb 2023 10:22:23 GMT

Hi,

Which device are you using? As you referred to nRF5 SDK in some other post I assumed you were using a nRF52 series device, but perhaps that is not the case? If you are, the function from my previous post is enough to set the public address, and you can test this by copy-pasting it to the beacon sample and calling it before bt_enable().

In what way does it fail in your case?

Regarding the non-resolvable random address you cannot use a non-static identity address, so it is expected that the call to bt_id_create() fails. That does not cause problems with security though, as long as you never advertise with that address. To advertise with a random address, adjust the advertising flags accordingly (for instance pick BT_LE_EXT_ADV_NCONN). Along that line it also looks strange that you added the BT_LE_ADV_OPT_USE_IDENTITY option, as I assume that is not what you want?

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

loquat — Wed, 08 Feb 2023 22:55:09 GMT

I tried using bt_ctlr_set_public_addr but it didn't work. (see code above)
Called before bt_enable().
what am i doing wrong?

I implement encrypted advertising transmission.
I want to use NRPA to make it harder to track. (like bluetooth mesh does)

RE: How to use public-addr and non-resolvable-addr on nrf connect SDK

Einar Thorsrud — Wed, 08 Feb 2023 14:35:32 GMT

Hi,

Different address types must be configured in different ways. To set a public address, the simplest is to do as illustrated here:

static void set_public_addr(void)
{
	uint8_t pub_addr[BT_ADDR_SIZE] = {0xba, 0xde, 0xba, 0x11, 0xca, 0xfe};
	bt_ctlr_set_public_addr(pub_addr);
}

Note that this must be done before you call bt_enable().

I need to look a bit more into non resolvable private addresses though, as I did not get that to work. That is a very uncommon address type, though. May I ask why you want to use it?