From: "Caleb Reinhold" <creinhold@lampreynetworks.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: BLE Delayed encryption change using
Date: Fri, 5 Sep 2014 17:32:41 -0400 [thread overview]
Message-ID: <001301cfc950$ecd06240$c67126c0$@lampreynetworks.com> (raw)
Hello all,
Summary:
I am attempting to reconnect to a BLE glucometer with gatttool after pairing
with bluetoothctl. A quick connection update seems to cause a large delay
(around a minute) in the transmission of the LL_ENC_REQ.
Description:
Attempting to connect to an agent which after connecting immediately sends
an L2CAP update connection parameters request with minimum connection
interval set to 20 ms, and maximum connection interval set to 40 ms.
Increasing both values by 100 ms causes the problem to stop being generated.
The problem happens only if the dongle using the Broadcom BCM20702 chipset
is used, using a CSR8510 A10 dongle I cannot generate this issue. I am using
BlueZ 5.22, using Linux kernel 3.10.17. The hardware platform is a Utilite.
Caleb Reinhold
next reply other threads:[~2014-09-05 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 21:32 Caleb Reinhold [this message]
2014-09-06 16:52 ` BLE Delayed encryption change using Marcel Holtmann
2014-09-09 22:29 ` Caleb Reinhold
2014-09-09 22:44 ` Marcel Holtmann
2014-09-10 14:16 ` Tom Harada
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='001301cfc950$ecd06240$c67126c0$@lampreynetworks.com' \
--to=creinhold@lampreynetworks.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