From: Marcel Holtmann <marcel@holtmann.org>
To: sushil <skdeka@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: HID control channel req issue
Date: Tue, 20 Jan 2009 10:28:57 +0100 [thread overview]
Message-ID: <1232443737.4655.0.camel@californication> (raw)
In-Reply-To: <92aeef200901192230r33a7afa9pb3db7a816a915d0e@mail.gmail.com>
Hi,
> In HID Host initiated connection to HID device, Host is sending L2CAP
> control channel request message twice to the device. The hcidump logs
> are as follows
>
>
> < ACL data: handle 47 flags 0x02 dlen 12
>
> L2CAP(s): Connect req: psm 17 scid 0x0040
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
>
> handle 47 packets 1
>
> > ACL data: handle 47 flags 0x02 dlen 16
>
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
>
> Connection pending - No futher information available
>
>
>
> > HCI Event: Link Key Request (0x17) plen 6
>
> bdaddr 00:02:5B:02:97:6E
>
> < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
>
> bdaddr 00:02:5B:02:97:6E
>
> > HCI Event: Command Complete (0x0e) plen 10
>
> Link Key Request Negative Reply (0x01|0x000c) ncmd 1
>
> status 0x00 bdaddr 00:02:5B:02:97:6E
>
>
> > HCI Event: PIN Code Request (0x16) plen 6
>
> bdaddr 00:02:5B:02:97:6E
>
> < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
>
> bdaddr 00:02:5B:02:97:6E len 4 pin '0000'
>
> > HCI Event: Command Complete (0x0e) plen 10
>
> PIN Code Request Reply (0x01|0x000d) ncmd 1
>
> status 0x00 bdaddr 00:02:5B:02:97:6E
>
> > HCI Event: Link Key Notification (0x18) plen 23
>
> bdaddr 00:02:5B:02:97:6E key B00AC8478BC923A0E1B269C5BB510584 type 0
>
> Type: Combination Key
>
> > HCI Event: Encrypt Change (0x08) plen 4
>
> status 0x00 handle 47 encrypt 0x01
>
>
> < ACL data: handle 47 flags 0x02 dlen 12
>
> L2CAP(s): Connect req: psm 17 scid 0x0040
>
> > ACL data: handle 47 flags 0x02 dlen 16
>
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
>
> Connection successful
>
> < ACL data: handle 47 flags 0x02 dlen 12
>
> L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
>
> handle 47 packets 1
>
>
> After looking into the code, in l2cap.c function l2cap_encrypt_cfm()
>
> If state is BT_CONNECT and status is 0, host again sends the second
> L2cap_conn_req for control channel.
>
>
> I am not sure even if encrypt== 0x01, bluez needs to send the second
> L2cap_connect_req for control channel.
no it does not. And I have never seen this behaviour. What kernel
version is this? Can you try my bluetooth-testing.git tree which is
against 2.6.29-rc2. It includes changes in that area.
Regards
Marcel
prev parent reply other threads:[~2009-01-20 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 6:30 HID control channel req issue sushil
2009-01-20 9:28 ` Marcel Holtmann [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=1232443737.4655.0.camel@californication \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=skdeka@gmail.com \
/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