* [Bluez-devel] Problem connecting Bluetooth device
@ 2006-06-12 13:07 Harald Niederländer
2006-06-17 10:42 ` Marcel Holtmann
0 siblings, 1 reply; 4+ messages in thread
From: Harald Niederländer @ 2006-06-12 13:07 UTC (permalink / raw)
To: bluez-devel
Hello all,
I try to connect (unsuccessful) a Bluetooth Device (blood pressure unit)
to read the data .
(The connection with other devices was easy,
Inquirys by the manufacturer are ineffective)
I doe the following steps:
doro:/home/harald # hcitool scan
Scanning ...
00:11:B1:A2:01:C9 TaiDoc-BTM
then "hcitool info" (after sending the PIN):
doro:/home/harald # hcitool info 00:11:B1:A2:01:C9
Requesting information ...
BD Address: 00:11:B1:A2:01:C9
Device Name: TaiDoc-BTM
LMP Version: 1.1 (0x1) LMP Subversion: 0x2c2
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging
scheme>
<power control> <transparent SCO>
then:
doro:/home/harald # rfcomm bind 0 00:11:B1:A2:01:C9 1
and change the rigths:
doro:/home/harald # chmod 777 rfcomm0
If i try to connect the device:
doro:/home/harald # rfcomm connect 0 00:11:B1:A2:01:C9 1
Can't connect RFCOMM socket: Permission denied
and in a message box I get :
....Authentication Error!
hcidump give the following infoarmations (during the steps above), but
I'm not able to interpret the output becouse I have
no documentations how to interpret the output:
HCI sniffer - Bluetooth packet analyzer ver 1.30
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Complete (0x01) plen 1
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: PIN Code Request (0x16) plen 6
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Link Key Notification (0x18) plen 23
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Remote Name Req Complete (0x07) plen 255
< HCI Command: Read Remote Version Information (0x01|0x001d) plen 2
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Read Remote Ver Info Complete (0x0c) plen 8
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
< HCI Command: Create Connection (0x01|0x0005) plen 13
> 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: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: PIN Code Request (0x16) plen 6
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Link Key Notification (0x18) plen 23
> HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Command Complete (0x0e) plen 6
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
< ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 6 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 17
> ACL data: handle 6 flags 0x01 dlen 1
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 320 max_retrans 0 credits 0
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 6 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 5
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
< HCI Command: Inquiry (0x01|0x0001) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Complete (0x01) plen 1
< HCI Command: Create Connection (0x01|0x0005) plen 13
> 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: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
Any help?
Thanks
Harald
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [Bluez-devel] Problem connecting Bluetooth device
2006-06-12 13:07 [Bluez-devel] Problem connecting Bluetooth device Harald Niederländer
@ 2006-06-17 10:42 ` Marcel Holtmann
2006-06-19 12:05 ` Harald Niederländer
0 siblings, 1 reply; 4+ messages in thread
From: Marcel Holtmann @ 2006-06-17 10:42 UTC (permalink / raw)
To: BlueZ development
Hi Harald,
> I try to connect (unsuccessful) a Bluetooth Device (blood pressure unit)
> to read the data .
> (The connection with other devices was easy,
> Inquirys by the manufacturer are ineffective)
>
> I doe the following steps:
>
> doro:/home/harald # hcitool scan
> Scanning ...
> 00:11:B1:A2:01:C9 TaiDoc-BTM
>
> then "hcitool info" (after sending the PIN):
> doro:/home/harald # hcitool info 00:11:B1:A2:01:C9
> Requesting information ...
> BD Address: 00:11:B1:A2:01:C9
> Device Name: TaiDoc-BTM
> LMP Version: 1.1 (0x1) LMP Subversion: 0x2c2
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2
> packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
> scheme>
> <power control> <transparent SCO>
>
> then:
> doro:/home/harald # rfcomm bind 0 00:11:B1:A2:01:C9 1
>
> and change the rigths:
> doro:/home/harald # chmod 777 rfcomm0
>
> If i try to connect the device:
> doro:/home/harald # rfcomm connect 0 00:11:B1:A2:01:C9 1
> Can't connect RFCOMM socket: Permission denied
>
> and in a message box I get :
> ....Authentication Error!
>
> hcidump give the following infoarmations (during the steps above), but
> I'm not able to interpret the output becouse I have
> no documentations how to interpret the output:
run it with "hcidump -X -V" as root.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-devel] Problem connecting Bluetooth device
2006-06-17 10:42 ` Marcel Holtmann
@ 2006-06-19 12:05 ` Harald Niederländer
2006-06-20 9:41 ` Marcel Holtmann
0 siblings, 1 reply; 4+ messages in thread
From: Harald Niederländer @ 2006-06-19 12:05 UTC (permalink / raw)
To: BlueZ development
Marcel Holtmann schrieb:
> Hi Harald,
>
>
> run it with "hcidump -X -V" as root.
>
> Regards
>
> Marcel
>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
Hi Marcel,
here are 2 different outputs of "hcidump -X -V" (i apologize for the length)
1. Trying to connect the device for the first time:
doro: # rfcomm connect /dev/rfcomm0 0:11:B1:A2:01:C9
Can't create RFCOMM TTY: Address already in use
doro: #
The device ask for the PIN
doro: # hcidump -X -V -i hci0
HCI sniffer - Bluetooth packet analyzer ver 1.30
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:11:B1:A2:01:C9 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: PIN Code Request (0x16) plen 6
bdaddr 00:11:B1:A2:01:C9
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
bdaddr 00:11:B1:A2:01:C9 len 6 pin '111111'
> HCI Event: Command Complete (0x0e) plen 10
PIN Code Request Reply (0x01|0x000d) ncmd 1
status 0x00 bdaddr 00:11:B1:A2:01:C9
> HCI Event: Link Key Notification (0x18) plen 23
bdaddr 00:11:B1:A2:01:C9 key 060E5E846F8206C5AECD5306622526E6 type 0
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 6 bdaddr 00:11:B1:A2:01:C9 type ACL encrypt 0x01
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 6 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Command Complete (0x0e) plen 6
Write Link Policy Settings (0x02|0x000d) ncmd 1
status 0x00 handle 6
> HCI Event: Max Slots Change (0x1b) plen 3
handle 6 slots 5
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 1
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 1
> ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
< ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 2
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 6 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 1
> ACL data: handle 6 flags 0x02 dlen 17
> ACL data: handle 6 flags 0x01 dlen 1
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 320 max_retrans 0 credits 0
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 1
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 3
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 6 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> ACL data: handle 6 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 5
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 1
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 6 packets 2
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> ACL data: handle 6 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 6 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 6 reason 0x16
Reason: Connection Terminated by Local Host
< HCI Command: Inquiry (0x01|0x0001) plen 5
lap 0x9e8b33 len 6 num 0
> HCI Event: Command Status (0x0f) plen 4
Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x48af class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x48af class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x48af class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x48af class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x48af class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x48af class 0x001f00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
2. Trying to connect the device for the second time (without resetting
the device):
doro: # rfcomm connect /dev/rfcomm0 0:11:B1:A2:01:C9
Can't connect RFCOMM socket: Permission denied
doro: #
The device don't ask for the PIN!!
doro: # hcidump -X -V -i hci0
HCI sniffer - Bluetooth packet analyzer ver 1.30
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:11:B1:A2:01:C9 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: Link Key Request (0x17) plen 6
bdaddr 00:11:B1:A2:01:C9
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:11:B1:A2:01:C9 key 6F032F60640CF647B6F07173A5A773CD
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:11:B1:A2:01:C9
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 6 bdaddr 00:11:B1:A2:01:C9 type ACL encrypt 0x00
Error: Authentication Failure
< HCI Command: Inquiry (0x01|0x0001) plen 5
lap 0x9e8b33 len 6 num 0
> HCI Event: Command Status (0x0f) plen 4
Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c0 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c0 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c0 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c0 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c1 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:11:B1:A2:01:C9 mode 1 clkoffset 0x19c0 class 0x001f00
> HCI Event: Inquiry Result (0x02) plen 15
bdaddr 00:A0:96:0B:98:B8 mode 1 clkoffset 0x7f1e class 0x000510
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
Regards
Harald
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [Bluez-devel] Problem connecting Bluetooth device
2006-06-19 12:05 ` Harald Niederländer
@ 2006-06-20 9:41 ` Marcel Holtmann
0 siblings, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2006-06-20 9:41 UTC (permalink / raw)
To: BlueZ development
Hi Harald,
> here are 2 different outputs of "hcidump -X -V" (i apologize for the length)
is the device a security mode 3 device or did you enabled auth and
encrypt in hcid.conf?
So the PIN code of this device is "111111". What does the manual state
about Bluetooth pairing etc.
The link key you get from the pairing is different from the link key you
actually use for authentication in the second try. Please check what has
been stored in /var/lib/bluetooth/<bdaddr>/linkkeys.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-06-20 9:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-12 13:07 [Bluez-devel] Problem connecting Bluetooth device Harald Niederländer
2006-06-17 10:42 ` Marcel Holtmann
2006-06-19 12:05 ` Harald Niederländer
2006-06-20 9:41 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).