[BlueZ,0/1] Fixed issue in bluetooth-meshd which causes HCI

Message

Daan Pape Aug. 18, 2020, 4:36 p.m. UTC

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 <[e-mail]>

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(-)