From: Marcel Holtmann <marcel@holtmann.org>
To: wim delvaux <wim.delvaux@adaptiveplanet.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] link_key_request problems
Date: Wed, 03 Mar 2004 15:46:06 +0100 [thread overview]
Message-ID: <1078325166.2787.108.camel@pegasus> (raw)
In-Reply-To: <200403031516.12967.wim.delvaux@adaptiveplanet.com>
Hi Wim,
write a binary version do disk (with -w) and post it or use -x.
Regards
Marcel
> hcidump attached :
>
> > 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
> . . . . . . . B . . 3 . . . . i . c . .
> . b
> > HCI Event: Role Change(0x12) plen 8
> . . . . . . . .
> > HCI Event: Command Complete(0x0e) plen 10
> . . . . . . . . . .
> > HCI Event: Connect Complete(0x03) plen 11
> . ( . . . . . . . . .
>
> or RAW
>
> > 04 04 0A 96 85 0D C7 02 00 12 01 12 01
> < 01 09 04 07 96 85 0D C7 02 00 00
> > 04 0F 04 00 01 09 04
> > 04 17 06 96 85 0D C7 02 00
> < 01 0B 04 16 96 85 0D C7 02 00 F5 42 F5 95 33 1E 18 AF B9 69
> 87 63 F4 EA DA 62
> > 04 12 08 00 96 85 0D C7 02 00 00
> > 04 0E 0A 01 0B 04 00 96 85 0D C7 02 00
> > 04 03 0B 05 28 00 96 85 0D C7 02 00 01 00
>
> In the syslog I see ...
>
> Mar 3 15:09:05 localhost hcid[10515]: link_key_request
> (sba=00:60:57:02:71:A2, dba=00:02:C7:0D:85:96)
>
> On the Ipaq (3800) I see similar messages but the ascii content of the message
> is different
>
> Raw output there is ...
>
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> > 04 12 08 00 A2 71 02 57 60 00 01
> > 04 17 06 A2 71 02 57 60 00
> < 01 0B 04 16 A2 71 02 57 60 00 16 66 2E EB B9 33 32 1B EE A8
> 15 F7 11 CA B1 CF
> > 04 0E 0A 01 0B 04 00 A2 71 02 57 60 00
> > 04 03 0B 05 28 00 A2 71 02 57 60 00 01 00
>
> The only solution is still to remove the link_key file
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-03 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 0:54 [Bluez-users] link_key_request problems wim delvaux
2004-02-25 1:27 ` Marcel Holtmann
2004-02-25 2:51 ` wim delvaux
2004-02-25 13:28 ` Marcel Holtmann
2004-03-03 14:16 ` wim delvaux
2004-03-03 14:46 ` 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=1078325166.2787.108.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=wim.delvaux@adaptiveplanet.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