public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: John Gruenenfelder <johng@as.arizona.edu>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem with link keys
Date: Fri, 5 Aug 2005 22:01:45 -0700	[thread overview]
Message-ID: <20050806050145.GA11152@as.arizona.edu> (raw)
In-Reply-To: <1123301455.26693.4.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]

On Sat, Aug 06, 2005 at 06:10:55AM +0200, Marcel Holtmann wrote:
>> 
>> I do not see any "reply negative" messages in any of the hcidump output yet it
>> doesn't work until I make a new key.
>
>use "hcidump -X -V".

The -V helps a lot.  I have attached a short hcidump listing from when I power
on the headset and it attempts to make a connection and fails.

>> Am I doing something wrong or in the wrong order?  This is with the current
>> bluez packages from Debian unstable (amd64 port).
>
>Is the link key valid if you don't power cycle your headset, but
>disconnect and then reconnect? If yes, then your headset is maybe
>broken.

Yes.  I was able to do the following:

hcitool cc bdaddr
hcitool dc bdaddr
hcitool cc bdaddr
hcitool info bdaddr

And it is working just fine.  It only seems to misbehave when I power it off.
Are any other people on this list using a Plantronics M2500 headset and, if
so, are you experiencing anything similar?


-- 
--John Gruenenfelder    Research Assistant, Steward Observatory, U of Arizona
                        johng@as.arizona.edu
Try Weasel Reader for PalmOS  --  http://gutenpalm.sf.net
"This is the most fun I've had without being drenched in the blood
of my enemies!"
        --Sam of Sam & Max

[-- Attachment #2: connect_attempt.log --]
[-- Type: text/plain, Size: 3752 bytes --]

HCI sniffer - Bluetooth packet analyzer ver 1.23
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:03:89:6E:C9:11 class 0x20040c type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:03:89:6E:C9:11
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
    bdaddr 00:03:89:6E:C9:11 key EB66D91F1F03B1531043A4E00E5F0199
> HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Reply (0x01|0x000b) ncmd 1
    status 0x00 bdaddr 00:03:89:6E:C9:11
> HCI Event: Connect Complete (0x03) plen 11
    status 0x05 handle 41 bdaddr 00:03:89:6E:C9:11 type ACL encrypt 0x00
    Error: Authentication Failure
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:03:89:6E:C9:11 class 0x20040c type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:03:89:6E:C9:11
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
    bdaddr 00:03:89:6E:C9:11 key EB66D91F1F03B1531043A4E00E5F0199
> HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Reply (0x01|0x000b) ncmd 1
    status 0x00 bdaddr 00:03:89:6E:C9:11
> HCI Event: Connect Complete (0x03) plen 11
    status 0x05 handle 42 bdaddr 00:03:89:6E:C9:11 type ACL encrypt 0x00
    Error: Authentication Failure
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:03:89:6E:C9:11 class 0x20040c type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:03:89:6E:C9:11
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
    bdaddr 00:03:89:6E:C9:11 key EB66D91F1F03B1531043A4E00E5F0199
> HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Reply (0x01|0x000b) ncmd 1
    status 0x00 bdaddr 00:03:89:6E:C9:11
> HCI Event: Connect Complete (0x03) plen 11
    status 0x05 handle 43 bdaddr 00:03:89:6E:C9:11 type ACL encrypt 0x00
    Error: Authentication Failure
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:03:89:6E:C9:11 class 0x20040c type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:03:89:6E:C9:11
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
    bdaddr 00:03:89:6E:C9:11 key EB66D91F1F03B1531043A4E00E5F0199
> HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:03:89:6E:C9:11 role 0x00
    Role: Master
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Reply (0x01|0x000b) ncmd 1
    status 0x00 bdaddr 00:03:89:6E:C9:11
> HCI Event: Connect Complete (0x03) plen 11
    status 0x05 handle 44 bdaddr 00:03:89:6E:C9:11 type ACL encrypt 0x00
    Error: Authentication Failure

  reply	other threads:[~2005-08-06  5:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06  3:01 [Bluez-devel] Problem with link keys John Gruenenfelder
2005-08-06  4:10 ` Marcel Holtmann
2005-08-06  5:01   ` John Gruenenfelder [this message]
2005-08-06  5:07     ` Marcel Holtmann
2005-08-06  9:07       ` John Gruenenfelder
2005-08-10 14:14         ` Alexandros Vellis

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=20050806050145.GA11152@as.arizona.edu \
    --to=johng@as.arizona.edu \
    --cc=bluez-devel@lists.sourceforge.net \
    /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