peer manager limit number of peers

RE: peer manager limit number of peers

Kevin — Wed, 02 Aug 2017 16:27:55 GMT

Thanks for the tip about pm_peer_count(), but I'm wondering where to place it? Ideally I reject any connection after pm_peer_count() = 1, but I understand pairing and connecting are two different things. So where in BLE events should I place this check in order to reject unwanted centrals as early as possible?

RE: peer manager limit number of peers

Definitely Confused — Wed, 23 Nov 2016 11:38:55 GMT

I want to limit the number of peers that can be bonded to this device at any one time, but I want to allow pairing of more devices. Whitelisting was a way of disallowing the bonding, but I think I can just reinitialize the security params to disallow bonding after I reach my peer limit.

RE: peer manager limit number of peers

Petter Myhre — Wed, 23 Nov 2016 08:51:15 GMT

It is not a variable that you configure, you can decrease the number of flash pages dedicated to FDS (see this) But I don't recommend doing that. I would rather use pm_peer_count() and for example not allow pairing after a certain count. But what is that you want to achieve? What does whitelisting have to do with this?