8000 Address resolution issue for bonded devices · Issue #1183 · UltimateHackingKeyboard/firmware · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Address resolution issue for bonded devices #1183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
mondalaci opened this issue Mar 16, 2025 · 1 comment
Open

Address resolution issue for bonded devices #1183

mondalaci opened this issue Mar 16, 2025 · 1 comment
Assignees
@benedekkupper

Comments

@mondalaci
Copy link
Member

Zephyr should be able to resolve the identity address for bonded devices, but it doesn't seem to work for some reason.

@kareltucek Please elaborate and provide related code.
@kareltucek
Copy link
Collaborator
kareltucek commented Mar 28, 2025 •
edited
Loading

Well, my set of beliefs:

  • allow list in zephyr is for both scanning and advertising
  • it is a single list that is used for both scanning and advertising
  • am now using it as direct advertisement implementation. Compared to true direct advertisement, this advertisement is still visible to other bluetooth devices, as it restricts only the ability to connect.
  • we store identity addresses of ble hid devices, however these devices use a private address when trying to connect. When connecting this is seen as address of such connection changing after the connection is secured.
  • Paired devices should be able to use the keys to determine the identity address from the private address.

What I would like:

  • add ble hid identity addresses to the allow list, and have those devices succesfully connect.

What is happening:

  • the devices never connect. (My guess is that something is wrong with the resolution of the identity address, and so the connections are refused because the anonymous addresses are not in the allow list.)

State of affairs: I have put this aside for the moment as the priority isn't super high.

Ways to help:

  • check the above against your knowledge
  • figure out what is wrong with it

Relevant code:

  • bt_advertise.c
  • goal: use allow list for nus+hid advertisement the same way it is used for nus advertisement, just add ble address for host connections of ble hid type too

Additional issues:

  • dongle pairing doesn't work via allow list, which is unexpected because I believe our NUS devices use identity addresses publicly. I may be wrong on this, in which case it is not surprising.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benedekkupper benedekkupper

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mondalaci @kareltucek @benedekkupper
0