How does a peripheral refuse a connection from a central?

RE: How does a peripheral refuse a connection from a central?

Eliot Stock — Mon, 10 Aug 2015 15:36:17 GMT

OK, great. Thanks.

RE: How does a peripheral refuse a connection from a central?

Petter Myhre — Mon, 10 Aug 2015 15:29:18 GMT

The Advertising Module was introduced in SDK 8.0.0. You don't need one :) It just a suggested way to handle advertising. If you don't use it, you can ignore the last sentence :)

RE: How does a peripheral refuse a connection from a central?

Eliot Stock — Mon, 10 Aug 2015 14:58:03 GMT

Thanks. I'm using a whitelist already and have added details above. I'm confused about the answer you linked to. I don't currently have any on_adv_evt() handler in my code. Is this a new thing in recent SDKs? Do I need one? I'm already calling dm_whitelist_create() before advertising, but at no point am I calling ble_advertising_whitelist_reply() currently.

RE: How does a peripheral refuse a connection from a central?

Petter Myhre — Mon, 10 Aug 2015 12:32:14 GMT

"The Link Layer may perform device filtering based on the device address of the peer device. Link Layer Device Filtering is used by the Link Layer to minimize the number of devices to which it responds." See Vol. 6, Part B, Section 4.3 in the Bluetooth Core specification 4.2.

"The set of devices that the Link Layer uses for device filtering is called the White List." See Vol. 6, Part B, Section 4.3.1 in the Bluetooth Core specification 4.2.

Whitelist is exactly what you describe, you still send out advertising packets, but you only respond to connection requests from devices in the whitelist. The whitelist is usually created by using the addresses and IRKs of the current bonded devices.

There are many questions regarding whitelist on Devzone, so a search should give you some information on how to set it up, but please ask if you get into trouble, preferably in a new question.

If you are using the Advertising Module in SDK 8.1.0, please be aware of this.