Digitelektro opened a new issue, #1852:
URL: https://github.com/apache/mynewt-nimble/issues/1852
Hi,
I am facing an issue that might not be a nimble bug, but I haven't found a
solution yet. I am using the NimBLE stack on Linux to create a BLE peripheral.
I can successfully connect and pair my phone. However, when I try to reconnect
my phone later, it prompts me to pair again.
After investigating, I suspect the problem is that my Bluetooth adapter
doesn't support the Resolving List feature. As a result, when my phone
reconnects using a resolvable random address, NimBLE cannot identify it as an
already bonded device.
I use key distribution flags: BLE_SM_PAIR_KEY_DIST_ENC |
BLE_SM_PAIR_KEY_DIST_ID
Logs when I start my program:
btmon log (I removed the sensitive informations):
```
HCI Command: LE Add Device To Resolving List (0x08|0x0027) plen 39
[hci1] 8.517265
Address type: Public (0x00)
Address: XX:XX:XX:XX:XX:XX
Peer identity resolving key: ...
Local identity resolving key: ...
HCI Event: Command Complete (0x0e) plen 4
8.519054
LE Add Device To Resolving List (0x08|0x0027) ncmd 2
Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
```
Nimble log output:
`failed to configure restored IRK`
Out of three BT adapter, two has this issue.
Is there a way to solve this problem?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
