This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Connection establishment only for specific device

Hello,

I'm trying to setup an automated pairing for two devices. My peripheral device is advertising and should only allow connection requests from a specific central device. I've read that using directed advertising will not show my peripheral device on unauthorized devices if they are complaint to the specification. However, a malicious device which doesn't ignore those advertising packets would still be able establish a connection if I'm not mistaken and I would need a whitelist instead. Is it possible to add a specific device (I know the device address, it's randomly generated but doesn't change) without the IRK such that only this specific central device is able to establish a connection and perform the automated pairing?

Best regards

Tobias

Parents
  • Hi,

    I guess there are a few ways this can be done.

    For instance you can start advertising with a whitelist enabled (allow scan requests, but disallow connection requests). The peripheral can then check the RSSI value of the peers executing scan requests, and if the RSSI level is very good (e.g. peer placed in very close proximity), then you can add this peer to the whitelist to allow it to connect and bond.

    In addition you can also pre-configure all your devices with an hard coded OOB key or passkey, such that any peer that connect will only be able to successfully bond if they have the correct key. If they are not able to bond within a reasonable time-out (let's say 1-2 seconds), then the peripheral can disconnect the link and start advertisement again until the next peer connection (hopefully with the correct key).

    Best regards,
    Kenneth

Reply
  • Hi,

    I guess there are a few ways this can be done.

    For instance you can start advertising with a whitelist enabled (allow scan requests, but disallow connection requests). The peripheral can then check the RSSI value of the peers executing scan requests, and if the RSSI level is very good (e.g. peer placed in very close proximity), then you can add this peer to the whitelist to allow it to connect and bond.

    In addition you can also pre-configure all your devices with an hard coded OOB key or passkey, such that any peer that connect will only be able to successfully bond if they have the correct key. If they are not able to bond within a reasonable time-out (let's say 1-2 seconds), then the peripheral can disconnect the link and start advertisement again until the next peer connection (hopefully with the correct key).

    Best regards,
    Kenneth

Children
Related