From: kjonca@o2.pl (Kamil Jońca)
To: linux-bluetooth@vger.kernel.org
Subject: Re: How to pair device from CLI?
Date: Fri, 28 Dec 2012 14:30:57 +0100 [thread overview]
Message-ID: <87wqw2s3qm.fsf@alfa.kjonca> (raw)
In-Reply-To: <20121228080842.GA28814@x220.P-661HNU-F1> (Johan Hedberg's message of "Fri, 28 Dec 2012 10:08:42 +0200")
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
writes:
> Hi Kamil,
>
> On Fri, Dec 28, 2012, Kamil Jońca wrote:
[....]
>
> It's quite odd that you should get RequestPasskey. That's something that
> should only happen if you're pretending to be a keyboard in which case
> you should enter the passkey displayed on the remote device (your phone
> in this case).
Nothing shows on my phone.
>
>> What do I should check? (s)trace?
>>
>> Distribution is pretty fresh debian sid.
>
> The most useful too would be hcidump (bluez-hcidump package). The output
> of hcidump -X for the full pairing process would be interesting.
Two tries in attachment.
[-- Attachment #2: Log --]
[-- Type: text/plain, Size: 6851 bytes --]
Sorry, try again.
HCI sniffer - Bluetooth packet analyzer ver 2.4
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr D4:E8:B2:AA:15:FA ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
status 0x00 bdaddr D4:E8:B2:AA:15:FA role 0x01
Role: Slave
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 12 bdaddr D4:E8:B2:AA:15:FA type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 12
> HCI Event: Max Slots Change (0x1b) plen 3
handle 12 slots 5
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 12
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x83
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
handle 12 page 1
> HCI Event: Command Status (0x0f) plen 4
Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
> HCI Event: Read Remote Extended Features (0x23) plen 13
status 0x00 handle 12 page 1 max 1
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
bdaddr D4:E8:B2:AA:15:FA mode 2 clkoffset 0x0000
> HCI Event: Command Status (0x0f) plen 4
Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Link Supervision Timeout Change (0x38) plen 4
handle 12 timeout 8000
> HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr D4:E8:B2:AA:15:FA name 'theta'
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
handle 12
> HCI Event: Command Status (0x0f) plen 4
Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr D4:E8:B2:AA:15:FA
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
bdaddr D4:E8:B2:AA:15:FA
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
status 0x00 bdaddr D4:E8:B2:AA:15:FA
> HCI Event: IO Capability Request (0x31) plen 6
bdaddr D4:E8:B2:AA:15:FA
< HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
bdaddr D4:E8:B2:AA:15:FA capability 0x04 oob 0x00 auth 0x03
Capability: Reserved (OOB data not present)
Authentication: Dedicated Bonding (MITM Protection)
> HCI Event: Command Complete (0x0e) plen 10
IO Capability Request Reply (0x01|0x002b) ncmd 1
status 0x00 bdaddr D4:E8:B2:AA:15:FA
> HCI Event: IO Capability Response (0x32) plen 9
bdaddr D4:E8:B2:AA:15:FA capability 0x01 oob 0x00 auth 0x03
Capability: DisplayYesNo (OOB data not present)
Authentication: Dedicated Bonding (MITM Protection)
> HCI Event: User Passkey Request (0x34) plen 6
bdaddr D4:E8:B2:AA:15:FA
< HCI Command: User Passkey Request Reply (0x01|0x002e) plen 10
bdaddr D4:E8:B2:AA:15:FA passkey 0
> HCI Event: Command Complete (0x0e) plen 10
User Passkey Request Reply (0x01|0x002e) ncmd 1
status 0x00 bdaddr D4:E8:B2:AA:15:FA
> HCI Event: Simple Pairing Complete (0x36) plen 7
status 0x05 bdaddr D4:E8:B2:AA:15:FA
Error: Authentication Failure
> HCI Event: Auth Complete (0x06) plen 3
status 0x05 handle 12
Error: Authentication Failure
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 12 reason 0x05
Reason: Authentication Failure
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr D4:E8:B2:AA:15:FA ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 12 bdaddr D4:E8:B2:AA:15:FA type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 12
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 12
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x83
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
handle 12 page 1
> HCI Event: Command Status (0x0f) plen 4
Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
> HCI Event: Max Slots Change (0x1b) plen 3
handle 12 slots 5
> HCI Event: Read Remote Extended Features (0x23) plen 13
status 0x00 handle 12 page 1 max 1
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
bdaddr D4:E8:B2:AA:15:FA mode 2 clkoffset 0x0000
> HCI Event: Command Status (0x0f) plen 4
Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr D4:E8:B2:AA:15:FA name 'theta'
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
handle 12
> HCI Event: Command Status (0x0f) plen 4
Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr D4:E8:B2:AA:15:FA
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
bdaddr D4:E8:B2:AA:15:FA
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
status 0x00 bdaddr D4:E8:B2:AA:15:FA
> HCI Event: IO Capability Request (0x31) plen 6
bdaddr D4:E8:B2:AA:15:FA
< HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
bdaddr D4:E8:B2:AA:15:FA capability 0x04 oob 0x00 auth 0x03
Capability: Reserved (OOB data not present)
Authentication: Dedicated Bonding (MITM Protection)
> HCI Event: Command Complete (0x0e) plen 10
IO Capability Request Reply (0x01|0x002b) ncmd 1
status 0x00 bdaddr D4:E8:B2:AA:15:FA
> HCI Event: IO Capability Response (0x32) plen 9
bdaddr D4:E8:B2:AA:15:FA capability 0x01 oob 0x00 auth 0x03
Capability: DisplayYesNo (OOB data not present)
Authentication: Dedicated Bonding (MITM Protection)
> HCI Event: User Passkey Request (0x34) plen 6
bdaddr D4:E8:B2:AA:15:FA
< HCI Command: User Passkey Request Reply (0x01|0x002e) plen 10
bdaddr D4:E8:B2:AA:15:FA passkey 0
> HCI Event: Command Complete (0x0e) plen 10
User Passkey Request Reply (0x01|0x002e) ncmd 1
status 0x00 bdaddr D4:E8:B2:AA:15:FA
> HCI Event: Simple Pairing Complete (0x36) plen 7
status 0x05 bdaddr D4:E8:B2:AA:15:FA
Error: Authentication Failure
> HCI Event: Auth Complete (0x06) plen 3
status 0x05 handle 12
Error: Authentication Failure
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 12 reason 0x05
Reason: Authentication Failure
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
--
http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/
I want to reach your mind -- where is it currently located?
next prev parent reply other threads:[~2012-12-28 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 0:23 How to pair device from CLI? Kamil Jońca
2012-12-28 8:08 ` Johan Hedberg
2012-12-28 13:30 ` Kamil Jońca [this message]
2012-12-28 13:54 ` Johan Hedberg
2012-12-28 15:25 ` Kamil Jońca
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=87wqw2s3qm.fsf@alfa.kjonca \
--to=kjonca@o2.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.