Linux bluetooth development
 help / color / mirror / Atom feed
From: Ron Harding <ron@prudentl.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez LE: Unable to get readings from LE devices
Date: Mon, 07 Mar 2016 14:05:45 -0500	[thread overview]
Message-ID: <56DDD109.5040701@prudentl.com> (raw)
In-Reply-To: CABBYNZJ=smBb3mjvidmx+0FNqx6OLHpt-jzOcCKuO91hxdg-VQ@mail.gmail.com

> 'No bonding' is used when the device is performing a
> Secure Simple Pairing procedure, but does not intend to retain the link key
> after the physical link is disconnected.
>
> I would keep the policy of not redoing the pairing automatically in
> case of missing link key error but perhaps the agent shall be called
> in such case and then depending on the response start a new pairing,
> so we keep this policy in the agent. Nevertheless it is still a good
> idea to set the "No bonding' value in case you want to avoid this
> extra steps while reconnecting.

Your explanation of how the "PIN or Key Missing" status could arise matches what I thought might be happening.

But I'm having trouble figuring out how to implement your suggested fix.  I know "No Bonding" is one of the values
that can be specified in the AuthReq field of a pairing request.  But I don't see how I, as a user of BlueZ, can
tell it to do so.  There doesn't seem to be anything in either org.bluez.Device1 or org.bluez.Agent1 for it.

I think maybe you're suggesting that the LE device it should be specifying "No Bonding".  If it's not going to
store the Link Key, then indeed it probably should.  But unfortunately we can't change that: we don't make the device.

- Ron


             reply	other threads:[~2016-03-07 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 19:05 Ron Harding [this message]
2016-03-08 12:58 ` Bluez LE: Unable to get readings from LE devices Luiz Augusto von Dentz
     [not found] <56C5F299.5080909@prudentl.com>
2016-02-18 16:51 ` ram
2016-02-19 11:19   ` Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56DDD109.5040701@prudentl.com \
    --to=ron@prudentl.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox