From: Johan Hedberg <johan.hedberg@gmail.com>
To: bubba junk <junkbubba2@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Question For Devs: Is Headset Connection Automatic?
Date: Tue, 3 Jul 2012 10:45:27 +0300 [thread overview]
Message-ID: <20120703074527.GA23089@x220> (raw)
In-Reply-To: <CAMk70DD3+26Q885KPbnim1Rj04=y9APOUOQM7teUNq95q7EPCw@mail.gmail.com>
Hi,
First of all, please don't top-post on this list.
On Mon, Jul 02, 2012, bubba junk wrote:
> I was wondering if you've had a chance to review the output of the
> hcidump and list-devices that you requested me to provide. I noticed
> the text "Connection refused - security block" in the output. Prior to
> the following patch, I was not able to connect my headset using the
> panel applet: [PATCH] Bluetooth: Fix l2cap connfailures for ssp
> devices. Since that patch, I am now able to connect the headset using
> the panel applet, but the headset does not connect automatically.
> Based on the output, is this another bug related to SSP?
I'll copy-paste it below:
> >> ACL data: handle 11 flags 0x02 dlen 12
> > L2CAP(s): Connect req: psm 3 scid 0x0041
> > < ACL data: handle 11 flags 0x00 dlen 16
> > L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0
> > Connection refused - security block
> >> HCI Event: Encrypt Change (0x08) plen 4
> > status 0x00 handle 11 encrypt 0x01
This looks like a well known hardware bug where the controller doesn't
send HCI events and ACL data packets in the right order. If you had an
air sniffer you'd probably see that the link is encrypted *before* the
L2CAP Connect request is sent (as opposed to after it as the log above
indicates). For connect requests to non-SDP PSMs coming before an
encrypted link a security block response is the correct behavior for
BlueZ.
Johan
prev parent reply other threads:[~2012-07-03 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 21:31 Question For Devs: Is Headset Connection Automatic? bubba junk
2012-06-15 3:24 ` Gustavo Padovan
2012-06-16 20:32 ` bubba junk
2012-06-16 20:39 ` bubba junk
2012-06-16 20:56 ` bubba junk
2012-07-02 19:23 ` bubba junk
2012-07-03 7:45 ` Johan Hedberg [this message]
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=20120703074527.GA23089@x220 \
--to=johan.hedberg@gmail.com \
--cc=junkbubba2@gmail.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).