Fixed issue in bluetooth-meshd which causes HCI
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | Fixed issue in bluetooth-meshd which causes HCI error 0x12 when LE scanning is enabled because no random address was set. This is fixed by using the default HCI own device address option.mesh/ | +2 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH BlueZ 0/1] Fixed issue in bluetooth-meshd which causes HCI
I had compiled bluez for OpenWRT and was running the bluetooth-meshd daemon with a Fanstel BT680T module which implement the Bluetooth 5.0 core specification.
The daemon did not properly start and failed with error:
LE Scan enable failed (0x12)
This error is described on page 2496 of the Bluetooth Core Specification Version 5.2 and is caused by the fact that no random address was initialized. The issue is resolved by falling back to using the default HCI advertisement settings which use the public device address in it's advertisements.
This is the first time that I contribute to Bluez so please forgive me if I made any styling mistake in the patch format. I also did not include my details in the 'AUTHORS' file just yet as I first wanted to wait for your reaction. In case the patch is accepted my name can be added to the 'AUTHORS' file as:
Daan Pape <[email protected]>
Please do not hesitate to ask any further questions if neccesary.
Kind regards,
Daan Pape
Daan Pape (1):
Fixed issue in bluetooth-meshd which causes HCI error 0x12 when LE
scanning is enabled because no random address was set. This is fixed by using the default HCI own device address option.
mesh/mesh-io-generic.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.20.1