From: Alan Au <alan.au@netcommwireless.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: Unable to make subsequent BLE connections
Date: Thu, 11 Dec 2014 10:29:32 +1100 [thread overview]
Message-ID: <5488D75C.2010700@netcommwireless.com> (raw)
Hi,
I'm connecting to a BLE oximeter device. The first couple of connects
succeed. But after that the connection always fails. I have tried with
both gatttool and with my own code. hcidump shows that the "LE Start
Encryption" command fails with "PIN or Key Missing". If I delete the
pairing (that was created by the earlier successful connection) then
subsequent connects will succeed for a few times again.
I analysed the hcidumps of successful and failed connects. In the failed
case, it looks to me like bluez is not sending out an SMP PairingRequest
in response to an SMP SecurityRequest from the slave. I can see in the
kernel code that smp_cmd_security_req() does not send out the
PairingRequest if it finds an LTK. But is that correct? Should it not
try to pair anyway because the remote device is requesting it and may
have deleted the earlier bonding.
I can provide the detailed hcidumps if anyone needs that.
Thanks.
Alan
______________________________________________________________________
This communication contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this communication in error, please notify me by telephone immediately.
______________________________________________________________________
next reply other threads:[~2014-12-10 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 23:29 Alan Au [this message]
2014-12-11 7:36 ` Unable to make subsequent BLE connections Johan Hedberg
2014-12-11 23:37 ` Alan Au
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=5488D75C.2010700@netcommwireless.com \
--to=alan.au@netcommwireless.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;
as well as URLs for NNTP newsgroup(s).