Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CAB+bgRb6vh4Pv9nZjYGoNXimTGoW1jYjxHk8ouvf6cBb8PcOXQ@mail.gmail.com>
In-Reply-To: <CAB+bgRb6vh4Pv9nZjYGoNXimTGoW1jYjxHk8ouvf6cBb8PcOXQ@mail.gmail.com>
From:   Ordit Gross <ordit.gross@orcam.com>
Date:   Mon, 28 Dec 2020 14:24:01 +0200
Message-ID: <CAB+bgRZrJn3m0_q5LRxEi9AYHNmiqozO61wYfX5pSwqXrho+vw@mail.gmail.com>
Subject: Re: getting address type from scan result
To:     linux-bluetooth@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

just to clarify, the needed information is:
> HCI Event: LE Meta Event (0x3e) plen 37                                                                                                                       #324 [hci0] 1064.855314
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Random (0x01)
        Address: 5B:6C:86:BE:2C:40 (Resolvable)

the only way I could think of is by opening an hci socket.. is there
any other way?
thanks for your help!


On Fri, Dec 25, 2020 at 6:28 AM Ordit Gross <ordit.gross@orcam.com> wrote:
>
> hi,
>
> Up till now the peripheral device we worked against was configured
> with public address,
> now it might also be random (both BDADDR_LE_RANDOM, BDADDR_LE_PUBLIC).
> The type of address is needed to connect correctly to the device
> (using l2cap_connect).
>
> How can I get the address type from the scan report?
> I'm currently using bluetoothctl, which seems not to expose this
> information in Device1 interface.
> thanks in advance! and happy holidays
>
> --


--