public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem with link keys
Date: Sat, 06 Aug 2005 06:10:55 +0200	[thread overview]
Message-ID: <1123301455.26693.4.camel@pegasus> (raw)
In-Reply-To: <20050806030119.GA10008@as.arizona.edu>

Hi John,

> My previous problems getting my headset to work were due to stale link keys.
> After deleting the old one, I could make a new pairing.  The problem is that
> the *new* link key becomes useless as soon as I turn off the headset.
> 
> The procedure is something like this:
> 1) Turn on headset
> 2) Pair with PC
> 3) Enter PIN when asked
> 4) headset works fine
> 5) shut off headset
> 6) turn headset back on
> 7) hcitool commands targeted at the headset all fail with "input/output error"
>    now.
> 8) Delete existing link key
> 9) Go back to step 2
> 
> Why does the link key go bad as soon as I power cycle the headset?  The
> hcidump output from step 6 is:
> 
> > HCI Event: Connect Request (0x04) plen 10
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> > HCI Event: Command Status (0x0f) plen 4
> > HCI Event: Link Key Request (0x17) plen 6
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> > HCI Event: Role Change (0x12) plen 8
> > HCI Event: Command Complete (0x0e) plen 10
> > HCI Event: Connect Complete (0x03) plen 11
> > HCI Event: Connect Request (0x04) plen 10
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> > HCI Event: Command Status (0x0f) plen 4
> > HCI Event: Link Key Request (0x17) plen 6
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> > HCI Event: Role Change (0x12) plen 8
> > HCI Event: Command Complete (0x0e) plen 10
> > HCI Event: Connect Complete (0x03) plen 11
> 
> 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".

> 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.

Regards

Marcel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-08-06  4:10 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 [this message]
2005-08-06  5:01   ` John Gruenenfelder
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=1123301455.26693.4.camel@pegasus \
    --to=marcel@holtmann.org \
    --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