Re: bluez: Disable GATT client at non-initiator side?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Yauhen,

On Tue, Mar 19, 2019 at 5:07 PM Yauhen Kharuzhy <jekhor@xxxxxxxxx> wrote:
>
> Hello,
>
> I am trying to implement GATT services with bluez API.
>
> If external device initiated LE connection to device with bluez
> running, bluez start to discover services at initiator and, if one of
> characteristics required pairing, request pairing. This is not
> intended behaviour for some reason in my case, so I need to disable
> GATT client if bluez is not initiator side of the connection, similar
> to ReverseServiceDiscovery config option for non-LE.
>
> Is it possible by any way? As i see code, device_attach_att() function
> in src/device.c initializes GATT client unconditionally in both cases.
> For debug, I disabled client initializing and this seems works for
> external-initiated connections.

We could perhaps reuse the same logic to disable the GATT service
discovery, though the should not cause any pairing request since the
discovery don't actually read any value, apart from characteristic
declaration which shall not require authentication.


-- 
Luiz Augusto von Dentz



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux