* Can't connect Bluetooth Devices
@ 2012-04-24 11:35 Steffen Becker
2012-04-24 20:57 ` Steffen Becker
2012-05-02 22:54 ` Steffen Becker
0 siblings, 2 replies; 11+ messages in thread
From: Steffen Becker @ 2012-04-24 11:35 UTC (permalink / raw)
To: linux-bluetooth
Hello,
I still have a problem to connect my bluetooth devices via pand command.
I've been searching the internet and asked in forums, but i didn't get
an answer.
I have 2 gentoo-PCs with a Bluetooth-3.0 Dongle at each PC.
Circa 2 weeks ago, everything worked. BlueZ-4.96 was installed and I had
no problems to connect my devices via pand and via rfcomm command.
But then I asked you for an SSP debug mode patch, because I wanted to
sniff my rfcomm connection. At the same time BlueZ-4.99 was released and
so I installed the new BlueZ-version and the patch.
I also deleted the stored linkkey and I was happy that I was able to
sniff my rfcomm-connection.
But thenceforth I can't connect my devices via pand command.
Then I tried to install the BlueZ-4.99 *without* the patch, but I still
couldn't connect via pand.
I also tried to install BlueZ-4.96, but the problem was still the same.
So I think it's no problem of the patch or the newer BlueZ-version, but
I really have no idea what's wrong.
If you need any of my configuration-files, just tell me and I will send it.
In the end, I show the hcidump message when I try to connect via pand
command.
Hope anyone can help me.
Regards,
Steffen
# hcidump -i hci0
HCI sniffer - Bluetooth packet analyzer ver 2.3
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> HCI Event: Connect Request (0x04) plen 10
bdaddr 00:02:72:AE:58:73 class 0x420100 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:02:72:AE:58:73 role 0x00
Role: Master
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
status 0x00 bdaddr 00:02:72:AE:58:73 role 0x00
Role: Master
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 11 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 11
> HCI Event: Max Slots Change (0x1b) plen 3
handle 11 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 11
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
handle 11 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 11 page 1 max 1
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth1-0'
> HCI Event: IO Capability Response (0x32) plen 9
bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
Capability: NoInputNoOutput (OOB data not present)
Authentication: No Bonding (No MITM Protection)
> HCI Event: IO Capability Request (0x31) plen 6
bdaddr 00:02:72:AE:58:73
< HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
Capability: NoInputNoOutput (OOB data not present)
Authentication: No Bonding (No MITM Protection)
> HCI Event: Command Complete (0x0e) plen 10
IO Capability Request Reply (0x01|0x002b) ncmd 1
status 0x00 bdaddr 00:02:72:AE:58:73
> HCI Event: User Confirmation Request (0x33) plen 10
bdaddr 00:02:72:AE:58:73 passkey 800553
< HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6
bdaddr 00:02:72:AE:58:73
> HCI Event: Command Complete (0x0e) plen 10
User Confirmation Request Reply (0x01|0x002c) ncmd 1
status 0x00 bdaddr 00:02:72:AE:58:73
> HCI Event: Simple Pairing Complete (0x36) plen 7
status 0x00 bdaddr 00:02:72:AE:58:73
> HCI Event: Link Key Notification (0x18) plen 23
bdaddr 00:02:72:AE:58:73 key E1C30FE5E1D620AC6DC78BB5A4AC299A type 4
Type: Unauthenticated Combination Key
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 11 encrypt 0x01
> ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< ACL data: handle 11 flags 0x00 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8
Enhanced Retransmission mode
Streaming mode
FCS Option
Fixed Channels
> ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 3
< ACL data: handle 11 flags 0x00 dlen 20
L2CAP(s): Info rsp: type 3 result 0
Fixed channel list 0x00000002
L2CAP Signalling Channel
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 11 packets 2
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 15 scid 0x0040
< ACL data: handle 11 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 11 flags 0x00 dlen 10
L2CAP(s): Info req: type 2
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 11 packets 2
> ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8
Enhanced Retransmission mode
Streaming mode
FCS Option
Fixed Channels
< ACL data: handle 11 flags 0x00 dlen 10
L2CAP(s): Info req: type 3
> ACL data: handle 11 flags 0x02 dlen 20
L2CAP(s): Info rsp: type 3 result 0
Fixed channel list 0x00000002
L2CAP Signalling Channel
< ACL data: handle 11 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
< ACL data: handle 11 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
Connection refused - security block
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 11 packets 2
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 11 packets 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 11 reason 0x13
Reason: Remote User Terminated Connection
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-04-24 11:35 Can't connect Bluetooth Devices Steffen Becker
@ 2012-04-24 20:57 ` Steffen Becker
2012-04-27 7:31 ` Steffen Becker
2012-05-02 22:54 ` Steffen Becker
1 sibling, 1 reply; 11+ messages in thread
From: Steffen Becker @ 2012-04-24 20:57 UTC (permalink / raw)
To: linux-bluetooth
Some additional information:
On both PCs I opened the file:
/var/lib/bluetooth/<local-bdaddr>/trusts
and wrote this line in it:
<remote-bdaddr> [all]
saved the file and tried again to connect via pand. Connection again
didn't worked but after that, the entered line in the trusts-file was
deleted!
Maybe this helps you to help me? :-)
Regards,
Steffen
Am 24.04.2012 13:35, schrieb Steffen Becker:
> Hello,
>
> I still have a problem to connect my bluetooth devices via pand
> command. I've been searching the internet and asked in forums, but i
> didn't get an answer.
>
> I have 2 gentoo-PCs with a Bluetooth-3.0 Dongle at each PC.
> Circa 2 weeks ago, everything worked. BlueZ-4.96 was installed and I
> had no problems to connect my devices via pand and via rfcomm command.
> But then I asked you for an SSP debug mode patch, because I wanted to
> sniff my rfcomm connection. At the same time BlueZ-4.99 was released
> and so I installed the new BlueZ-version and the patch.
> I also deleted the stored linkkey and I was happy that I was able to
> sniff my rfcomm-connection.
> But thenceforth I can't connect my devices via pand command.
>
> Then I tried to install the BlueZ-4.99 *without* the patch, but I
> still couldn't connect via pand.
> I also tried to install BlueZ-4.96, but the problem was still the
> same. So I think it's no problem of the patch or the newer
> BlueZ-version, but I really have no idea what's wrong.
>
> If you need any of my configuration-files, just tell me and I will
> send it.
>
> In the end, I show the hcidump message when I try to connect via pand
> command.
>
> Hope anyone can help me.
>
> Regards,
> Steffen
>
>
> # hcidump -i hci0
> HCI sniffer - Bluetooth packet analyzer ver 2.3
> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> > HCI Event: Connect Request (0x04) plen 10
> bdaddr 00:02:72:AE:58:73 class 0x420100 type ACL
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> bdaddr 00:02:72:AE:58:73 role 0x00
> Role: Master
> > HCI Event: Command Status (0x0f) plen 4
> Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> > HCI Event: Role Change (0x12) plen 8
> status 0x00 bdaddr 00:02:72:AE:58:73 role 0x00
> Role: Master
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x00 handle 11 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
> < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> handle 11
> > HCI Event: Max Slots Change (0x1b) plen 3
> handle 11 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 11
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
> < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
> handle 11 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 11 page 1 max 1
> Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
> bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth1-0'
> > HCI Event: IO Capability Response (0x32) plen 9
> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
> Capability: NoInputNoOutput (OOB data not present)
> Authentication: No Bonding (No MITM Protection)
> > HCI Event: IO Capability Request (0x31) plen 6
> bdaddr 00:02:72:AE:58:73
> < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
> Capability: NoInputNoOutput (OOB data not present)
> Authentication: No Bonding (No MITM Protection)
> > HCI Event: Command Complete (0x0e) plen 10
> IO Capability Request Reply (0x01|0x002b) ncmd 1
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: User Confirmation Request (0x33) plen 10
> bdaddr 00:02:72:AE:58:73 passkey 800553
> < HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6
> bdaddr 00:02:72:AE:58:73
> > HCI Event: Command Complete (0x0e) plen 10
> User Confirmation Request Reply (0x01|0x002c) ncmd 1
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: Simple Pairing Complete (0x36) plen 7
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: Link Key Notification (0x18) plen 23
> bdaddr 00:02:72:AE:58:73 key E1C30FE5E1D620AC6DC78BB5A4AC299A type 4
> Type: Unauthenticated Combination Key
> > HCI Event: Encrypt Change (0x08) plen 4
> status 0x00 handle 11 encrypt 0x01
> > ACL data: handle 11 flags 0x02 dlen 10
> L2CAP(s): Info req: type 2
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> > ACL data: handle 11 flags 0x02 dlen 10
> L2CAP(s): Info req: type 3
> < ACL data: handle 11 flags 0x00 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 2
> > ACL data: handle 11 flags 0x02 dlen 12
> L2CAP(s): Connect req: psm 15 scid 0x0040
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
> Connection pending - No futher information available
> < ACL data: handle 11 flags 0x00 dlen 10
> L2CAP(s): Info req: type 2
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 2
> > ACL data: handle 11 flags 0x02 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> < ACL data: handle 11 flags 0x00 dlen 10
> L2CAP(s): Info req: type 3
> > ACL data: handle 11 flags 0x02 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
> Connection pending - Authorization pending
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
> Connection refused - security block
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 2
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 1
> > HCI Event: Disconn Complete (0x05) plen 4
> status 0x00 handle 11 reason 0x13
> Reason: Remote User Terminated Connection
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-04-24 20:57 ` Steffen Becker
@ 2012-04-27 7:31 ` Steffen Becker
0 siblings, 0 replies; 11+ messages in thread
From: Steffen Becker @ 2012-04-27 7:31 UTC (permalink / raw)
To: linux-bluetooth
Hello,
isn't there anyone who can help me? It's really important for me.
It already would be helpful, if someone can tell me *how i can change my
security level*.
To the last mail (below here):
After overwriting with a sdp- and profiles-file from a backup, the line
in trusts don't get deleted anymore.
Regards & have a good weekend,
Steffen
Am 24.04.2012 22:57, schrieb Steffen Becker:
> Some additional information:
>
> On both PCs I opened the file:
> /var/lib/bluetooth/<local-bdaddr>/trusts
> and wrote this line in it:
> <remote-bdaddr> [all]
> saved the file and tried again to connect via pand. Connection again
> didn't worked but after that, the entered line in the trusts-file was
> deleted!
>
> Maybe this helps you to help me? :-)
>
> Regards,
> Steffen
>
> Am 24.04.2012 13:35, schrieb Steffen Becker:
>> Hello,
>>
>> I still have a problem to connect my bluetooth devices via pand
>> command. I've been searching the internet and asked in forums, but i
>> didn't get an answer.
>>
>> I have 2 gentoo-PCs with a Bluetooth-3.0 Dongle at each PC.
>> Circa 2 weeks ago, everything worked. BlueZ-4.96 was installed and I
>> had no problems to connect my devices via pand and via rfcomm command.
>> But then I asked you for an SSP debug mode patch, because I wanted to
>> sniff my rfcomm connection. At the same time BlueZ-4.99 was released
>> and so I installed the new BlueZ-version and the patch.
>> I also deleted the stored linkkey and I was happy that I was able to
>> sniff my rfcomm-connection.
>> But thenceforth I can't connect my devices via pand command.
>>
>> Then I tried to install the BlueZ-4.99 *without* the patch, but I
>> still couldn't connect via pand.
>> I also tried to install BlueZ-4.96, but the problem was still the
>> same. So I think it's no problem of the patch or the newer
>> BlueZ-version, but I really have no idea what's wrong.
>>
>> If you need any of my configuration-files, just tell me and I will
>> send it.
>>
>> In the end, I show the hcidump message when I try to connect via pand
>> command.
>>
>> Hope anyone can help me.
>>
>> Regards,
>> Steffen
>>
>>
>> # hcidump -i hci0
>> HCI sniffer - Bluetooth packet analyzer ver 2.3
>> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>> > HCI Event: Connect Request (0x04) plen 10
>> bdaddr 00:02:72:AE:58:73 class 0x420100 type ACL
>> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
>> bdaddr 00:02:72:AE:58:73 role 0x00
>> Role: Master
>> > HCI Event: Command Status (0x0f) plen 4
>> Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
>> > HCI Event: Role Change (0x12) plen 8
>> status 0x00 bdaddr 00:02:72:AE:58:73 role 0x00
>> Role: Master
>> > HCI Event: Connect Complete (0x03) plen 11
>> status 0x00 handle 11 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
>> < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
>> handle 11
>> > HCI Event: Max Slots Change (0x1b) plen 3
>> handle 11 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 11
>> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
>> < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
>> handle 11 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 11 page 1 max 1
>> Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
>> bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth1-0'
>> > HCI Event: IO Capability Response (0x32) plen 9
>> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
>> Capability: NoInputNoOutput (OOB data not present)
>> Authentication: No Bonding (No MITM Protection)
>> > HCI Event: IO Capability Request (0x31) plen 6
>> bdaddr 00:02:72:AE:58:73
>> < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
>> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
>> Capability: NoInputNoOutput (OOB data not present)
>> Authentication: No Bonding (No MITM Protection)
>> > HCI Event: Command Complete (0x0e) plen 10
>> IO Capability Request Reply (0x01|0x002b) ncmd 1
>> status 0x00 bdaddr 00:02:72:AE:58:73
>> > HCI Event: User Confirmation Request (0x33) plen 10
>> bdaddr 00:02:72:AE:58:73 passkey 800553
>> < HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6
>> bdaddr 00:02:72:AE:58:73
>> > HCI Event: Command Complete (0x0e) plen 10
>> User Confirmation Request Reply (0x01|0x002c) ncmd 1
>> status 0x00 bdaddr 00:02:72:AE:58:73
>> > HCI Event: Simple Pairing Complete (0x36) plen 7
>> status 0x00 bdaddr 00:02:72:AE:58:73
>> > HCI Event: Link Key Notification (0x18) plen 23
>> bdaddr 00:02:72:AE:58:73 key E1C30FE5E1D620AC6DC78BB5A4AC299A type 4
>> Type: Unauthenticated Combination Key
>> > HCI Event: Encrypt Change (0x08) plen 4
>> status 0x00 handle 11 encrypt 0x01
>> > ACL data: handle 11 flags 0x02 dlen 10
>> L2CAP(s): Info req: type 2
>> < ACL data: handle 11 flags 0x00 dlen 16
>> L2CAP(s): Info rsp: type 2 result 0
>> Extended feature mask 0x00b8
>> Enhanced Retransmission mode
>> Streaming mode
>> FCS Option
>> Fixed Channels
>> > ACL data: handle 11 flags 0x02 dlen 10
>> L2CAP(s): Info req: type 3
>> < ACL data: handle 11 flags 0x00 dlen 20
>> L2CAP(s): Info rsp: type 3 result 0
>> Fixed channel list 0x00000002
>> L2CAP Signalling Channel
>> > HCI Event: Number of Completed Packets (0x13) plen 5
>> handle 11 packets 2
>> > ACL data: handle 11 flags 0x02 dlen 12
>> L2CAP(s): Connect req: psm 15 scid 0x0040
>> < ACL data: handle 11 flags 0x00 dlen 16
>> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
>> Connection pending - No futher information available
>> < ACL data: handle 11 flags 0x00 dlen 10
>> L2CAP(s): Info req: type 2
>> > HCI Event: Number of Completed Packets (0x13) plen 5
>> handle 11 packets 2
>> > ACL data: handle 11 flags 0x02 dlen 16
>> L2CAP(s): Info rsp: type 2 result 0
>> Extended feature mask 0x00b8
>> Enhanced Retransmission mode
>> Streaming mode
>> FCS Option
>> Fixed Channels
>> < ACL data: handle 11 flags 0x00 dlen 10
>> L2CAP(s): Info req: type 3
>> > ACL data: handle 11 flags 0x02 dlen 20
>> L2CAP(s): Info rsp: type 3 result 0
>> Fixed channel list 0x00000002
>> L2CAP Signalling Channel
>> < ACL data: handle 11 flags 0x00 dlen 16
>> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
>> Connection pending - Authorization pending
>> < ACL data: handle 11 flags 0x00 dlen 16
>> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
>> Connection refused - security block
>> > HCI Event: Number of Completed Packets (0x13) plen 5
>> handle 11 packets 2
>> > HCI Event: Number of Completed Packets (0x13) plen 5
>> handle 11 packets 1
>> > HCI Event: Disconn Complete (0x05) plen 4
>> status 0x00 handle 11 reason 0x13
>> Reason: Remote User Terminated Connection
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-bluetooth" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-04-24 11:35 Can't connect Bluetooth Devices Steffen Becker
2012-04-24 20:57 ` Steffen Becker
@ 2012-05-02 22:54 ` Steffen Becker
2012-05-02 22:58 ` Gustavo Padovan
1 sibling, 1 reply; 11+ messages in thread
From: Steffen Becker @ 2012-05-02 22:54 UTC (permalink / raw)
To: linux-bluetooth
Hello everyone,
Am 24.04.2012 13:35, schrieb Steffen Becker:
> Hello,
>
> I still have a problem to connect my bluetooth devices via pand
> command. I've been searching the internet and asked in forums, but i
> didn't get an answer.
>
> I have 2 gentoo-PCs with a Bluetooth-3.0 Dongle at each PC.
> Circa 2 weeks ago, everything worked. BlueZ-4.96 was installed and I
> had no problems to connect my devices via pand and via rfcomm command.
> But then I asked you for an SSP debug mode patch, because I wanted to
> sniff my rfcomm connection. At the same time BlueZ-4.99 was released
> and so I installed the new BlueZ-version and the patch.
> I also deleted the stored linkkey and I was happy that I was able to
> sniff my rfcomm-connection.
> But thenceforth I can't connect my devices via pand command.
>
> Then I tried to install the BlueZ-4.99 *without* the patch, but I
> still couldn't connect via pand.
> I also tried to install BlueZ-4.96, but the problem was still the
> same. So I think it's no problem of the patch or the newer
> BlueZ-version, but I really have no idea what's wrong.
>
> If you need any of my configuration-files, just tell me and I will
> send it.
>
> In the end, I show the hcidump message when I try to connect via pand
> command.
>
> Hope anyone can help me.
>
> Regards,
> Steffen
>
>
> # hcidump -i hci0
> HCI sniffer - Bluetooth packet analyzer ver 2.3
> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> > HCI Event: Connect Request (0x04) plen 10
> bdaddr 00:02:72:AE:58:73 class 0x420100 type ACL
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> bdaddr 00:02:72:AE:58:73 role 0x00
> Role: Master
> > HCI Event: Command Status (0x0f) plen 4
> Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> > HCI Event: Role Change (0x12) plen 8
> status 0x00 bdaddr 00:02:72:AE:58:73 role 0x00
> Role: Master
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x00 handle 11 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
> < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> handle 11
> > HCI Event: Max Slots Change (0x1b) plen 3
> handle 11 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 11
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
> < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
> handle 11 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 11 page 1 max 1
> Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
> bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth1-0'
> > HCI Event: IO Capability Response (0x32) plen 9
> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
> Capability: NoInputNoOutput (OOB data not present)
> Authentication: No Bonding (No MITM Protection)
> > HCI Event: IO Capability Request (0x31) plen 6
> bdaddr 00:02:72:AE:58:73
> < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
> Capability: NoInputNoOutput (OOB data not present)
> Authentication: No Bonding (No MITM Protection)
> > HCI Event: Command Complete (0x0e) plen 10
> IO Capability Request Reply (0x01|0x002b) ncmd 1
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: User Confirmation Request (0x33) plen 10
> bdaddr 00:02:72:AE:58:73 passkey 800553
> < HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6
> bdaddr 00:02:72:AE:58:73
> > HCI Event: Command Complete (0x0e) plen 10
> User Confirmation Request Reply (0x01|0x002c) ncmd 1
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: Simple Pairing Complete (0x36) plen 7
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: Link Key Notification (0x18) plen 23
> bdaddr 00:02:72:AE:58:73 key E1C30FE5E1D620AC6DC78BB5A4AC299A type 4
> Type: Unauthenticated Combination Key
> > HCI Event: Encrypt Change (0x08) plen 4
> status 0x00 handle 11 encrypt 0x01
> > ACL data: handle 11 flags 0x02 dlen 10
> L2CAP(s): Info req: type 2
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> > ACL data: handle 11 flags 0x02 dlen 10
> L2CAP(s): Info req: type 3
> < ACL data: handle 11 flags 0x00 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 2
> > ACL data: handle 11 flags 0x02 dlen 12
> L2CAP(s): Connect req: psm 15 scid 0x0040
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
> Connection pending - No futher information available
> < ACL data: handle 11 flags 0x00 dlen 10
> L2CAP(s): Info req: type 2
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 2
> > ACL data: handle 11 flags 0x02 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> < ACL data: handle 11 flags 0x00 dlen 10
> L2CAP(s): Info req: type 3
> > ACL data: handle 11 flags 0x02 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
> Connection pending - Authorization pending
> < ACL data: handle 11 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
> Connection refused - security block
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 2
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 11 packets 1
> > HCI Event: Disconn Complete (0x05) plen 4
> status 0x00 handle 11 reason 0x13
> Reason: Remote User Terminated Connection
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
That's still my problem, but now I have a different question regarding
to that:
As I said, I deleted the stored linkkey to get my rfcomm-connection sniffed.
Now I think this (deleting the linkkey) is the problem why I can't
connect via pand. Am I right?
With "deleting" I mean: I just deleted the file "linkkeys" in
/var/lib/bluetooth/<local-bdaddr>/
So my question is: How can I create a new linkkey (so that hopefully my
pand-connection works) ?
I tried the command "hciconfig hci0 putkey" but nothing happened.
I also tried to copy a backup-file ("linkkeys"-file) into both of my
/var/lib/bluetooth-folders, but it looks like the devices don't use the
key from that backup-file.
Regards,
Steffen
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-02 22:54 ` Steffen Becker
@ 2012-05-02 22:58 ` Gustavo Padovan
2012-05-03 8:02 ` Steffen Becker
0 siblings, 1 reply; 11+ messages in thread
From: Gustavo Padovan @ 2012-05-02 22:58 UTC (permalink / raw)
To: Steffen Becker; +Cc: linux-bluetooth
[-- Attachment #1: Type: text/plain, Size: 8001 bytes --]
Hi Steffen,
* Steffen Becker <steffen.becker@tu-ilmenau.de> [2012-05-03 00:54:20 +0200]:
> Hello everyone,
>
> Am 24.04.2012 13:35, schrieb Steffen Becker:
> >Hello,
> >
> >I still have a problem to connect my bluetooth devices via pand
> >command. I've been searching the internet and asked in forums, but
> >i didn't get an answer.
> >
> >I have 2 gentoo-PCs with a Bluetooth-3.0 Dongle at each PC.
> >Circa 2 weeks ago, everything worked. BlueZ-4.96 was installed and
> >I had no problems to connect my devices via pand and via rfcomm
> >command.
> >But then I asked you for an SSP debug mode patch, because I wanted
> >to sniff my rfcomm connection. At the same time BlueZ-4.99 was
> >released and so I installed the new BlueZ-version and the patch.
> >I also deleted the stored linkkey and I was happy that I was able
> >to sniff my rfcomm-connection.
> >But thenceforth I can't connect my devices via pand command.
> >
> >Then I tried to install the BlueZ-4.99 *without* the patch, but I
> >still couldn't connect via pand.
> >I also tried to install BlueZ-4.96, but the problem was still the
> >same. So I think it's no problem of the patch or the newer
> >BlueZ-version, but I really have no idea what's wrong.
> >
> >If you need any of my configuration-files, just tell me and I will
> >send it.
> >
> >In the end, I show the hcidump message when I try to connect via
> >pand command.
> >
> >Hope anyone can help me.
> >
> >Regards,
> >Steffen
> >
> >
> ># hcidump -i hci0
> >HCI sniffer - Bluetooth packet analyzer ver 2.3
> >device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> >> HCI Event: Connect Request (0x04) plen 10
> > bdaddr 00:02:72:AE:58:73 class 0x420100 type ACL
> >< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> > bdaddr 00:02:72:AE:58:73 role 0x00
> > Role: Master
> >> HCI Event: Command Status (0x0f) plen 4
> > Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> >> HCI Event: Role Change (0x12) plen 8
> > status 0x00 bdaddr 00:02:72:AE:58:73 role 0x00
> > Role: Master
> >> HCI Event: Connect Complete (0x03) plen 11
> > status 0x00 handle 11 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
> >< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> > handle 11
> >> HCI Event: Max Slots Change (0x1b) plen 3
> > handle 11 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 11
> > Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
> >< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
> > handle 11 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 11 page 1 max 1
> > Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> >< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> > bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth1-0'
> >> HCI Event: IO Capability Response (0x32) plen 9
> > bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
> > Capability: NoInputNoOutput (OOB data not present)
> > Authentication: No Bonding (No MITM Protection)
> >> HCI Event: IO Capability Request (0x31) plen 6
> > bdaddr 00:02:72:AE:58:73
> >< HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
> > bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
> > Capability: NoInputNoOutput (OOB data not present)
> > Authentication: No Bonding (No MITM Protection)
> >> HCI Event: Command Complete (0x0e) plen 10
> > IO Capability Request Reply (0x01|0x002b) ncmd 1
> > status 0x00 bdaddr 00:02:72:AE:58:73
> >> HCI Event: User Confirmation Request (0x33) plen 10
> > bdaddr 00:02:72:AE:58:73 passkey 800553
> >< HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6
> > bdaddr 00:02:72:AE:58:73
> >> HCI Event: Command Complete (0x0e) plen 10
> > User Confirmation Request Reply (0x01|0x002c) ncmd 1
> > status 0x00 bdaddr 00:02:72:AE:58:73
> >> HCI Event: Simple Pairing Complete (0x36) plen 7
> > status 0x00 bdaddr 00:02:72:AE:58:73
> >> HCI Event: Link Key Notification (0x18) plen 23
> > bdaddr 00:02:72:AE:58:73 key E1C30FE5E1D620AC6DC78BB5A4AC299A type 4
> > Type: Unauthenticated Combination Key
> >> HCI Event: Encrypt Change (0x08) plen 4
> > status 0x00 handle 11 encrypt 0x01
> >> ACL data: handle 11 flags 0x02 dlen 10
> > L2CAP(s): Info req: type 2
> >< ACL data: handle 11 flags 0x00 dlen 16
> > L2CAP(s): Info rsp: type 2 result 0
> > Extended feature mask 0x00b8
> > Enhanced Retransmission mode
> > Streaming mode
> > FCS Option
> > Fixed Channels
> >> ACL data: handle 11 flags 0x02 dlen 10
> > L2CAP(s): Info req: type 3
> >< ACL data: handle 11 flags 0x00 dlen 20
> > L2CAP(s): Info rsp: type 3 result 0
> > Fixed channel list 0x00000002
> > L2CAP Signalling Channel
> >> HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 11 packets 2
> >> ACL data: handle 11 flags 0x02 dlen 12
> > L2CAP(s): Connect req: psm 15 scid 0x0040
> >< ACL data: handle 11 flags 0x00 dlen 16
> > L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
> > Connection pending - No futher information available
> >< ACL data: handle 11 flags 0x00 dlen 10
> > L2CAP(s): Info req: type 2
> >> HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 11 packets 2
> >> ACL data: handle 11 flags 0x02 dlen 16
> > L2CAP(s): Info rsp: type 2 result 0
> > Extended feature mask 0x00b8
> > Enhanced Retransmission mode
> > Streaming mode
> > FCS Option
> > Fixed Channels
> >< ACL data: handle 11 flags 0x00 dlen 10
> > L2CAP(s): Info req: type 3
> >> ACL data: handle 11 flags 0x02 dlen 20
> > L2CAP(s): Info rsp: type 3 result 0
> > Fixed channel list 0x00000002
> > L2CAP Signalling Channel
> >< ACL data: handle 11 flags 0x00 dlen 16
> > L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
> > Connection pending - Authorization pending
> >< ACL data: handle 11 flags 0x00 dlen 16
> > L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
> > Connection refused - security block
> >> HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 11 packets 2
> >> HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 11 packets 1
> >> HCI Event: Disconn Complete (0x05) plen 4
> > status 0x00 handle 11 reason 0x13
> > Reason: Remote User Terminated Connection
> >
> >--
> >To unsubscribe from this list: send the line "unsubscribe
> >linux-bluetooth" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> That's still my problem, but now I have a different question regarding
> to that:
> As I said, I deleted the stored linkkey to get my rfcomm-connection sniffed.
> Now I think this (deleting the linkkey) is the problem why I can't
> connect via pand. Am I right?
> With "deleting" I mean: I just deleted the file "linkkeys" in
> /var/lib/bluetooth/<local-bdaddr>/
>
> So my question is: How can I create a new linkkey (so that hopefully my
> pand-connection works) ?
A linkkey is created during the pairing procedure, just pair your
devices and you will be done.
And let only bluetoothd touch the /var/lib/bluetooth
directory, don't touch there yourself.
Gustavo
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-02 22:58 ` Gustavo Padovan
@ 2012-05-03 8:02 ` Steffen Becker
2012-05-03 9:44 ` Johan Hedberg
0 siblings, 1 reply; 11+ messages in thread
From: Steffen Becker @ 2012-05-03 8:02 UTC (permalink / raw)
To: Gustavo Padovan, linux-bluetooth
Hi Gustavo,
Am 03.05.2012 00:58, schrieb Gustavo Padovan:
> Hi Steffen,
>
> * Steffen Becker<steffen.becker@tu-ilmenau.de> [2012-05-03 00:54:20 +0200]:
>
>> Hello everyone,
>>
>> Am 24.04.2012 13:35, schrieb Steffen Becker:
>>> Hello,
>>>
>>> I still have a problem to connect my bluetooth devices via pand
>>> command. I've been searching the internet and asked in forums, but
>>> i didn't get an answer.
>>>
>>> I have 2 gentoo-PCs with a Bluetooth-3.0 Dongle at each PC.
>>> Circa 2 weeks ago, everything worked. BlueZ-4.96 was installed and
>>> I had no problems to connect my devices via pand and via rfcomm
>>> command.
>>> But then I asked you for an SSP debug mode patch, because I wanted
>>> to sniff my rfcomm connection. At the same time BlueZ-4.99 was
>>> released and so I installed the new BlueZ-version and the patch.
>>> I also deleted the stored linkkey and I was happy that I was able
>>> to sniff my rfcomm-connection.
>>> But thenceforth I can't connect my devices via pand command.
>>>
>>> Then I tried to install the BlueZ-4.99 *without* the patch, but I
>>> still couldn't connect via pand.
>>> I also tried to install BlueZ-4.96, but the problem was still the
>>> same. So I think it's no problem of the patch or the newer
>>> BlueZ-version, but I really have no idea what's wrong.
>>>
>>> If you need any of my configuration-files, just tell me and I will
>>> send it.
>>>
>>> In the end, I show the hcidump message when I try to connect via
>>> pand command.
>>>
>>> Hope anyone can help me.
>>>
>>> Regards,
>>> Steffen
>>>
>>>
>>> # hcidump -i hci0
>>> HCI sniffer - Bluetooth packet analyzer ver 2.3
>>> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>>> HCI Event: Connect Request (0x04) plen 10
>>> bdaddr 00:02:72:AE:58:73 class 0x420100 type ACL
>>> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
>>> bdaddr 00:02:72:AE:58:73 role 0x00
>>> Role: Master
>>>> HCI Event: Command Status (0x0f) plen 4
>>> Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
>>>> HCI Event: Role Change (0x12) plen 8
>>> status 0x00 bdaddr 00:02:72:AE:58:73 role 0x00
>>> Role: Master
>>>> HCI Event: Connect Complete (0x03) plen 11
>>> status 0x00 handle 11 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
>>> < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
>>> handle 11
>>>> HCI Event: Max Slots Change (0x1b) plen 3
>>> handle 11 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 11
>>> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
>>> < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
>>> handle 11 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 11 page 1 max 1
>>> Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>>> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
>>> bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth1-0'
>>>> HCI Event: IO Capability Response (0x32) plen 9
>>> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
>>> Capability: NoInputNoOutput (OOB data not present)
>>> Authentication: No Bonding (No MITM Protection)
>>>> HCI Event: IO Capability Request (0x31) plen 6
>>> bdaddr 00:02:72:AE:58:73
>>> < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
>>> bdaddr 00:02:72:AE:58:73 capability 0x03 oob 0x00 auth 0x00
>>> Capability: NoInputNoOutput (OOB data not present)
>>> Authentication: No Bonding (No MITM Protection)
>>>> HCI Event: Command Complete (0x0e) plen 10
>>> IO Capability Request Reply (0x01|0x002b) ncmd 1
>>> status 0x00 bdaddr 00:02:72:AE:58:73
>>>> HCI Event: User Confirmation Request (0x33) plen 10
>>> bdaddr 00:02:72:AE:58:73 passkey 800553
>>> < HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6
>>> bdaddr 00:02:72:AE:58:73
>>>> HCI Event: Command Complete (0x0e) plen 10
>>> User Confirmation Request Reply (0x01|0x002c) ncmd 1
>>> status 0x00 bdaddr 00:02:72:AE:58:73
>>>> HCI Event: Simple Pairing Complete (0x36) plen 7
>>> status 0x00 bdaddr 00:02:72:AE:58:73
>>>> HCI Event: Link Key Notification (0x18) plen 23
>>> bdaddr 00:02:72:AE:58:73 key E1C30FE5E1D620AC6DC78BB5A4AC299A type 4
>>> Type: Unauthenticated Combination Key
>>>> HCI Event: Encrypt Change (0x08) plen 4
>>> status 0x00 handle 11 encrypt 0x01
>>>> ACL data: handle 11 flags 0x02 dlen 10
>>> L2CAP(s): Info req: type 2
>>> < ACL data: handle 11 flags 0x00 dlen 16
>>> L2CAP(s): Info rsp: type 2 result 0
>>> Extended feature mask 0x00b8
>>> Enhanced Retransmission mode
>>> Streaming mode
>>> FCS Option
>>> Fixed Channels
>>>> ACL data: handle 11 flags 0x02 dlen 10
>>> L2CAP(s): Info req: type 3
>>> < ACL data: handle 11 flags 0x00 dlen 20
>>> L2CAP(s): Info rsp: type 3 result 0
>>> Fixed channel list 0x00000002
>>> L2CAP Signalling Channel
>>>> HCI Event: Number of Completed Packets (0x13) plen 5
>>> handle 11 packets 2
>>>> ACL data: handle 11 flags 0x02 dlen 12
>>> L2CAP(s): Connect req: psm 15 scid 0x0040
>>> < ACL data: handle 11 flags 0x00 dlen 16
>>> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
>>> Connection pending - No futher information available
>>> < ACL data: handle 11 flags 0x00 dlen 10
>>> L2CAP(s): Info req: type 2
>>>> HCI Event: Number of Completed Packets (0x13) plen 5
>>> handle 11 packets 2
>>>> ACL data: handle 11 flags 0x02 dlen 16
>>> L2CAP(s): Info rsp: type 2 result 0
>>> Extended feature mask 0x00b8
>>> Enhanced Retransmission mode
>>> Streaming mode
>>> FCS Option
>>> Fixed Channels
>>> < ACL data: handle 11 flags 0x00 dlen 10
>>> L2CAP(s): Info req: type 3
>>>> ACL data: handle 11 flags 0x02 dlen 20
>>> L2CAP(s): Info rsp: type 3 result 0
>>> Fixed channel list 0x00000002
>>> L2CAP Signalling Channel
>>> < ACL data: handle 11 flags 0x00 dlen 16
>>> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
>>> Connection pending - Authorization pending
>>> < ACL data: handle 11 flags 0x00 dlen 16
>>> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
>>> Connection refused - security block
>>>> HCI Event: Number of Completed Packets (0x13) plen 5
>>> handle 11 packets 2
>>>> HCI Event: Number of Completed Packets (0x13) plen 5
>>> handle 11 packets 1
>>>> HCI Event: Disconn Complete (0x05) plen 4
>>> status 0x00 handle 11 reason 0x13
>>> Reason: Remote User Terminated Connection
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>> linux-bluetooth" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> That's still my problem, but now I have a different question regarding
>> to that:
>> As I said, I deleted the stored linkkey to get my rfcomm-connection sniffed.
>> Now I think this (deleting the linkkey) is the problem why I can't
>> connect via pand. Am I right?
>> With "deleting" I mean: I just deleted the file "linkkeys" in
>> /var/lib/bluetooth/<local-bdaddr>/
>>
>> So my question is: How can I create a new linkkey (so that hopefully my
>> pand-connection works) ?
> A linkkey is created during the pairing procedure, just pair your
> devices and you will be done.
> And let only bluetoothd touch the /var/lib/bluetooth
> directory, don't touch there yourself.
>
> Gustavo
Thanks for your fast reply, but that's exactly what I don't know: How
can I pair my devices?
If I connect them via rfcomm, they create each time a new linkkey (with
disabled ssp debug mode).
Remember: Before I installed the sspdebug mode patch, there was a stored
linkkey. After installing the patch, deleting the linkkey-file &
enabling the sspdebug mode, I was not able to create a new linkkey.
Regards,
Steffen
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-03 8:02 ` Steffen Becker
@ 2012-05-03 9:44 ` Johan Hedberg
2012-05-06 18:35 ` Steffen Becker
0 siblings, 1 reply; 11+ messages in thread
From: Johan Hedberg @ 2012-05-03 9:44 UTC (permalink / raw)
To: Steffen Becker; +Cc: Gustavo Padovan, linux-bluetooth
Hi Steffen,
On Thu, May 03, 2012, Steffen Becker wrote:
> >A linkkey is created during the pairing procedure, just pair your
> >devices and you will be done.
> >And let only bluetoothd touch the /var/lib/bluetooth
> >directory, don't touch there yourself.
> >
> > Gustavo
>
> Thanks for your fast reply, but that's exactly what I don't know:
> How can I pair my devices?
You pair using the CreatePairedDevice D-Bus method that BlueZ provides.
There are various front-ends that you can use to call this method. If
you've got GNOME installed then a pairing wizard should be just a few
mouse clicks away through the Bluetooth icon in the upper right-hand
corner. If you've only got the command line you can use e.g. the
simple-agent python script (under the test subdirectory):
test/simple-agent hci0 <remote address>
Btw, is there something that the network plugin (which you can operate
using e.g. test/test-network) doesn't provide but pand does? We'll
probably remove pand from the source tree along with BlueZ 5.0 so it'd
be good to know any deficiencies it has.
Johan
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-03 9:44 ` Johan Hedberg
@ 2012-05-06 18:35 ` Steffen Becker
2012-05-09 12:05 ` Steffen Becker
0 siblings, 1 reply; 11+ messages in thread
From: Steffen Becker @ 2012-05-06 18:35 UTC (permalink / raw)
To: Johan Hedberg, linux-bluetooth
Hi Johan,
Am 03.05.2012 11:44, schrieb Johan Hedberg:
> Hi Steffen,
>
> On Thu, May 03, 2012, Steffen Becker wrote:
>>> A linkkey is created during the pairing procedure, just pair your
>>> devices and you will be done.
>>> And let only bluetoothd touch the /var/lib/bluetooth
>>> directory, don't touch there yourself.
>>>
>>> Gustavo
>> Thanks for your fast reply, but that's exactly what I don't know:
>> How can I pair my devices?
> You pair using the CreatePairedDevice D-Bus method that BlueZ provides.
> There are various front-ends that you can use to call this method. If
> you've got GNOME installed then a pairing wizard should be just a few
> mouse clicks away through the Bluetooth icon in the upper right-hand
> corner. If you've only got the command line you can use e.g. the
> simple-agent python script (under the test subdirectory):
>
> test/simple-agent hci0<remote address>
>
> Btw, is there something that the network plugin (which you can operate
> using e.g. test/test-network) doesn't provide but pand does? We'll
> probably remove pand from the source tree along with BlueZ 5.0 so it'd
> be good to know any deficiencies it has.
>
> Johan
Sorry for this late answer and thank you for that hint; but I haven't
tried it yet - will do this tomorrow.
To your question:
There are some special things I want to do using the pand-command
(because it worked well the last years with that):
1.) Using the "iperf" command to display & compare the data rate of a) a
bluetooth1.0-Dongle and b) a bluetooth3.0-Dongle
2.) Using the "iperf" command between two bluetooth-devices and at the
same time also using the "iperf"-command between two WLAN-devices (2
PC's: at each PC one bluetooth-device & one WLAN-Stick) -> With a
sniffing tool I want to check the AFH of Bluetooth.
3.) Send a "big" (media-)file to show how Bluetooth3.0 uses the "WLAN"-mode.
Is all this possible without pand-connection? If yes - how?
Reagrds,
Steffen
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-06 18:35 ` Steffen Becker
@ 2012-05-09 12:05 ` Steffen Becker
2012-05-09 14:28 ` Steffen Becker
0 siblings, 1 reply; 11+ messages in thread
From: Steffen Becker @ 2012-05-09 12:05 UTC (permalink / raw)
To: linux-bluetooth
Hello Johan & all the others,
Am 06.05.2012 20:35, schrieb Steffen Becker:
> Hi Johan,
>
> Am 03.05.2012 11:44, schrieb Johan Hedberg:
>> Hi Steffen,
>>
>> On Thu, May 03, 2012, Steffen Becker wrote:
>>>> A linkkey is created during the pairing procedure, just pair your
>>>> devices and you will be done.
>>>> And let only bluetoothd touch the /var/lib/bluetooth
>>>> directory, don't touch there yourself.
>>>>
>>>> Gustavo
>>> Thanks for your fast reply, but that's exactly what I don't know:
>>> How can I pair my devices?
>> You pair using the CreatePairedDevice D-Bus method that BlueZ provides.
>> There are various front-ends that you can use to call this method. If
>> you've got GNOME installed then a pairing wizard should be just a few
>> mouse clicks away through the Bluetooth icon in the upper right-hand
>> corner. If you've only got the command line you can use e.g. the
>> simple-agent python script (under the test subdirectory):
>>
>> test/simple-agent hci0<remote address>
>>
>> Btw, is there something that the network plugin (which you can operate
>> using e.g. test/test-network) doesn't provide but pand does? We'll
>> probably remove pand from the source tree along with BlueZ 5.0 so it'd
>> be good to know any deficiencies it has.
>>
>> Johan
>
> Sorry for this late answer and thank you for that hint; but I haven't
> tried it yet - will do this tomorrow.
>
> To your question:
> There are some special things I want to do using the pand-command
> (because it worked well the last years with that):
> 1.) Using the "iperf" command to display & compare the data rate of a)
> a bluetooth1.0-Dongle and b) a bluetooth3.0-Dongle
> 2.) Using the "iperf" command between two bluetooth-devices and at the
> same time also using the "iperf"-command between two WLAN-devices (2
> PC's: at each PC one bluetooth-device & one WLAN-Stick) -> With a
> sniffing tool I want to check the AFH of Bluetooth.
> 3.) Send a "big" (media-)file to show how Bluetooth3.0 uses the
> "WLAN"-mode.
>
> Is all this possible without pand-connection? If yes - how?
>
> Reagrds,
> Steffen
Do you have any information about how I can handle these 3 activities
without "pand"-connection?
Regards,
Steffen
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-09 12:05 ` Steffen Becker
@ 2012-05-09 14:28 ` Steffen Becker
2012-05-14 22:23 ` Steffen Becker
0 siblings, 1 reply; 11+ messages in thread
From: Steffen Becker @ 2012-05-09 14:28 UTC (permalink / raw)
To: linux-bluetooth
Hello,
you can ignore the last mail, but
Am 09.05.2012 14:05, schrieb Steffen Becker:
> Hello Johan & all the others,
>
> Am 06.05.2012 20:35, schrieb Steffen Becker:
>> Hi Johan,
>>
>> Am 03.05.2012 11:44, schrieb Johan Hedberg:
>>> Hi Steffen,
>>>
>>> On Thu, May 03, 2012, Steffen Becker wrote:
>>>>> A linkkey is created during the pairing procedure, just pair your
>>>>> devices and you will be done.
>>>>> And let only bluetoothd touch the /var/lib/bluetooth
>>>>> directory, don't touch there yourself.
>>>>>
>>>>> Gustavo
>>>> Thanks for your fast reply, but that's exactly what I don't know:
>>>> How can I pair my devices?
>>> You pair using the CreatePairedDevice D-Bus method that BlueZ provides.
>>> There are various front-ends that you can use to call this method. If
>>> you've got GNOME installed then a pairing wizard should be just a few
>>> mouse clicks away through the Bluetooth icon in the upper right-hand
>>> corner. If you've only got the command line you can use e.g. the
>>> simple-agent python script (under the test subdirectory):
>>>
>>> test/simple-agent hci0<remote address>
>>>
>>> Btw, is there something that the network plugin (which you can operate
>>> using e.g. test/test-network) doesn't provide but pand does? We'll
>>> probably remove pand from the source tree along with BlueZ 5.0 so it'd
>>> be good to know any deficiencies it has.
>>>
>>> Johan
>>
>> Sorry for this late answer and thank you for that hint; but I haven't
>> tried it yet - will do this tomorrow.
>>
>> To your question:
>> There are some special things I want to do using the pand-command
>> (because it worked well the last years with that):
>> 1.) Using the "iperf" command to display & compare the data rate of
>> a) a bluetooth1.0-Dongle and b) a bluetooth3.0-Dongle
>> 2.) Using the "iperf" command between two bluetooth-devices and at
>> the same time also using the "iperf"-command between two WLAN-devices
>> (2 PC's: at each PC one bluetooth-device & one WLAN-Stick) -> With a
>> sniffing tool I want to check the AFH of Bluetooth.
>> 3.) Send a "big" (media-)file to show how Bluetooth3.0 uses the
>> "WLAN"-mode.
>>
>> Is all this possible without pand-connection? If yes - how?
>>
>> Reagrds,
>> Steffen
>
> Do you have any information about how I can handle these 3 activities
> without "pand"-connection?
>
> Regards,
> Steffen
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
as I said, I have two gentoo-PCs with a Bluetooth3.0-Dongle at each PC.
Now I tried to use the bluetooth-test-network to connect:
But connection was refused and I don't know how to fix it. Down below
you find the
# bluez-test-network
# monitor-bluetooth
and
# hcidump -i hci0
-messages of both PCs. On top of that, there are different error
messages at both PCs!
Hope you can help me in this case.
Regards,
Steffen
So here it is:
PC1:
bluetooth1 ~ # bluez-test-discovery
[ 00:02:72:AE:58:73 ]
Name = bluetooth2-0
Paired = 1
LegacyPairing = 0
Alias = bluetooth2-0
UUIDs =
dbus.Array([dbus.String(u'00001116-0000-1000-8000-00805f9b34fb'),
dbus.String(u'00001103-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000110e-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000110c-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000110a-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000111f-0000-1000-8000-00805f9b34fb'),
dbus.String(u'00001112-0000-1000-8000-00805f9b34fb')],
signature=dbus.Signature('s'), variant_level=1)
Address = 00:02:72:AE:58:73
RSSI = -37
Class = 0x4a0100
Trusted = 1
Icon = computer
-------------------------------------------------------------------------------------
bluetooth1 ~ # bluez-test-network 00:02:72:AE:58:73 nap
Traceback (most recent call last):
File "/usr/bin/bluez-test-network", line 45, in <module>
iface = network.Connect(service)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 68,
in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 143,
in __call__
**keywords)
File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line
630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.Failed: Connection
refused (111)
-------------------------------------------------------------------------------------
bluetooth1 ~ # monitor-bluetooth
{Device.PropertyChanged} [/org/bluez/2821/hci0/dev_00_02_72_AE_58_73]
Connected = 1
{Device.PropertyChanged} [/org/bluez/2821/hci0/dev_00_02_72_AE_58_73]
Connected = 0
-------------------------------------------------------------------------------------
bluetooth1 ~ # hcidump -i hci0
HCI sniffer - Bluetooth packet analyzer ver 2.3
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 role 0x01
Role: Slave
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 12 bdaddr 00:02:72:AE:58:73 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: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
< 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 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth2-0'
< 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 00:02:72:AE:58:73
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:02:72:AE:58:73 key C6A4D268E42E81CAD233A2C61FA7993A
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:02:72:AE:58:73
> HCI Event: Auth Complete (0x06) plen 3
status 0x00 handle 12
< HCI Command: Set Connection Encryption (0x01|0x0013) plen 3
handle 12 encrypt 0x01
> HCI Event: Command Status (0x0f) plen 4
Set Connection Encryption (0x01|0x0013) status 0x00 ncmd 1
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 12 encrypt 0x01
< ACL data: handle 12 flags 0x00 dlen 10
L2CAP(s): Info req: type 2
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8
Enhanced Retransmission mode
Streaming mode
FCS Option
Fixed Channels
< ACL data: handle 12 flags 0x00 dlen 10
L2CAP(s): Info req: type 3
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 2
> ACL data: handle 12 flags 0x02 dlen 20
L2CAP(s): Info rsp: type 3 result 0
Fixed channel list 0x00000002
L2CAP Signalling Channel
< ACL data: handle 12 flags 0x00 dlen 12
L2CAP(s): Connect req: psm 15 scid 0x0040
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
> ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< ACL data: handle 12 flags 0x00 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8
Enhanced Retransmission mode
Streaming mode
FCS Option
Fixed Channels
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 2
> ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 3
< ACL data: handle 12 flags 0x00 dlen 20
L2CAP(s): Info rsp: type 3 result 0
Fixed channel list 0x00000002
L2CAP Signalling Channel
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
Connection refused - security block
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 1
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 12 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 12 reason 0x16
Reason: Connection Terminated by Local Host
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
PC2:
bluetooth2 ~ # bluez-test-discovery
[ 00:02:72:24:02:04 ]
Name = bluetooth1-0
Paired = 1
LegacyPairing = 0
Alias = bluetooth1-0
UUIDs =
dbus.Array([dbus.String(u'00001103-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000110e-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000110c-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000110a-0000-1000-8000-00805f9b34fb'),
dbus.String(u'0000111f-0000-1000-8000-00805f9b34fb'),
dbus.String(u'00001112-0000-1000-8000-00805f9b34fb')],
signature=dbus.Signature('s'), variant_level=1)
Address = 00:02:72:24:02:04
RSSI = -38
Class = 0x4a0100
Trusted = 1
Icon = computer
-------------------------------------------------------------------------------------
bluetooth2 ~ # bluez-test-network 00:02:72:24:02:04 nap
Traceback (most recent call last):
File "/usr/bin/bluez-test-network", line 45, in <module>
iface = network.Connect(service)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 68,
in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 143,
in __call__
**keywords)
File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line
630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
Method "Connect" with signature "s" on interface "org.bluez.Network"
doesn't exist
-------------------------------------------------------------------------------------
bluetooth2 ~ # monitor-bluetooth
-------------------------------------------------------------------------------------
bluetooth2 bluetooth # hcidump -i hci0
HCI sniffer - Bluetooth packet analyzer ver 2.3
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
monitor and hcidump at bluetooth2 when bluetooth1 tries to connect:
bluetooth2 ~ # monitor-bluetooth
{Device.PropertyChanged} [/org/bluez/2937/hci0/dev_00_02_72_24_02_04]
Connected = 1
{Device.PropertyChanged} [/org/bluez/2937/hci0/dev_00_02_72_24_02_04]
Connected = 0
-------------------------------------------------------------------------------------
bluetooth2 bluetooth # hcidump -i hci0
HCI sniffer - Bluetooth packet analyzer ver 2.3
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> HCI Event: Connect Request (0x04) plen 10
bdaddr 00:02:72:24:02:04 class 0x4a0100 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:02:72:24:02:04 role 0x00
Role: Master
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
status 0x00 bdaddr 00:02:72:24:02:04 role 0x00
Role: Master
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 12 bdaddr 00:02:72:24:02:04 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: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
handle 12 page 1
> HCI Event: Max Slots Change (0x1b) plen 3
handle 12 slots 5
> 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 00:02:72:24:02:04 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 00:02:72:24:02:04 name 'bluetooth1-0'
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:02:72:24:02:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:02:72:24:02:04 key C6A4D268E42E81CAD233A2C61FA7993A
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:02:72:24:02:04
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 12 encrypt 0x01
> ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< ACL data: handle 12 flags 0x00 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8
Enhanced Retransmission mode
Streaming mode
FCS Option
Fixed Channels
> ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 3
< ACL data: handle 12 flags 0x00 dlen 20
L2CAP(s): Info rsp: type 3 result 0
Fixed channel list 0x00000002
L2CAP Signalling Channel
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 2
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 15 scid 0x0040
< ACL data: handle 12 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 12 flags 0x00 dlen 10
L2CAP(s): Info req: type 2
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 2
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8
Enhanced Retransmission mode
Streaming mode
FCS Option
Fixed Channels
< ACL data: handle 12 flags 0x00 dlen 10
L2CAP(s): Info req: type 3
> ACL data: handle 12 flags 0x02 dlen 20
L2CAP(s): Info rsp: type 3 result 0
Fixed channel list 0x00000002
L2CAP Signalling Channel
< ACL data: handle 12 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
< ACL data: handle 12 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
Connection refused - security block
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 2
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 12 packets 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 12 reason 0x13
Reason: Remote User Terminated Connection
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Can't connect Bluetooth Devices
2012-05-09 14:28 ` Steffen Becker
@ 2012-05-14 22:23 ` Steffen Becker
0 siblings, 0 replies; 11+ messages in thread
From: Steffen Becker @ 2012-05-14 22:23 UTC (permalink / raw)
To: linux-bluetooth
Hello everyone,
> as I said, I have two gentoo-PCs with a Bluetooth3.0-Dongle at each PC.
> Now I tried to use the bluetooth-test-network to connect:
> But connection was refused and I don't know how to fix it. Down below
> you find the
> # bluez-test-network
> # monitor-bluetooth
> and
> # hcidump -i hci0
> -messages of both PCs. On top of that, there are different error
> messages at both PCs!
>
> Hope you can help me in this case.
>
> Regards,
> Steffen
>
>
> So here it is:
>
> PC1:
> bluetooth1 ~ # bluez-test-discovery
> [ 00:02:72:AE:58:73 ]
> Name = bluetooth2-0
> Paired = 1
> LegacyPairing = 0
> Alias = bluetooth2-0
> UUIDs =
> dbus.Array([dbus.String(u'00001116-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'00001103-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000110e-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000110c-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000110a-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000111f-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'00001112-0000-1000-8000-00805f9b34fb')],
> signature=dbus.Signature('s'), variant_level=1)
> Address = 00:02:72:AE:58:73
> RSSI = -37
> Class = 0x4a0100
> Trusted = 1
> Icon = computer
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth1 ~ # bluez-test-network 00:02:72:AE:58:73 nap
> Traceback (most recent call last):
> File "/usr/bin/bluez-test-network", line 45, in <module>
> iface = network.Connect(service)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 68,
> in __call__
> return self._proxy_method(*args, **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 143,
> in __call__
> **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line
> 630, in call_blocking
> message, timeout)
> dbus.exceptions.DBusException: org.bluez.Error.Failed: Connection
> refused (111)
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth1 ~ # monitor-bluetooth
> {Device.PropertyChanged} [/org/bluez/2821/hci0/dev_00_02_72_AE_58_73]
> Connected = 1
> {Device.PropertyChanged} [/org/bluez/2821/hci0/dev_00_02_72_AE_58_73]
> Connected = 0
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth1 ~ # hcidump -i hci0
> HCI sniffer - Bluetooth packet analyzer ver 2.3
> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:02:72:AE:58:73 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 00:02:72:AE:58:73 role 0x01
> Role: Slave
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x00 handle 12 bdaddr 00:02:72:AE:58:73 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: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
> < 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 00:02:72:AE:58:73 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 00:02:72:AE:58:73 name 'bluetooth2-0'
> < 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 00:02:72:AE:58:73
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> bdaddr 00:02:72:AE:58:73 key C6A4D268E42E81CAD233A2C61FA7993A
> > HCI Event: Command Complete (0x0e) plen 10
> Link Key Request Reply (0x01|0x000b) ncmd 1
> status 0x00 bdaddr 00:02:72:AE:58:73
> > HCI Event: Auth Complete (0x06) plen 3
> status 0x00 handle 12
> < HCI Command: Set Connection Encryption (0x01|0x0013) plen 3
> handle 12 encrypt 0x01
> > HCI Event: Command Status (0x0f) plen 4
> Set Connection Encryption (0x01|0x0013) status 0x00 ncmd 1
> > HCI Event: Encrypt Change (0x08) plen 4
> status 0x00 handle 12 encrypt 0x01
> < ACL data: handle 12 flags 0x00 dlen 10
> L2CAP(s): Info req: type 2
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> < ACL data: handle 12 flags 0x00 dlen 10
> L2CAP(s): Info req: type 3
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 2
> > ACL data: handle 12 flags 0x02 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> < ACL data: handle 12 flags 0x00 dlen 12
> L2CAP(s): Connect req: psm 15 scid 0x0040
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
> Connection pending - No futher information available
> > ACL data: handle 12 flags 0x02 dlen 10
> L2CAP(s): Info req: type 2
> < ACL data: handle 12 flags 0x00 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 2
> > ACL data: handle 12 flags 0x02 dlen 10
> L2CAP(s): Info req: type 3
> < ACL data: handle 12 flags 0x00 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
> Connection pending - Authorization pending
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
> Connection refused - security block
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 1
> < HCI Command: Disconnect (0x01|0x0006) plen 3
> handle 12 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 12 reason 0x16
> Reason: Connection Terminated by Local Host
>
>
> -------------------------------------------------------------------------------------
>
> -------------------------------------------------------------------------------------
>
>
> PC2:
> bluetooth2 ~ # bluez-test-discovery
> [ 00:02:72:24:02:04 ]
> Name = bluetooth1-0
> Paired = 1
> LegacyPairing = 0
> Alias = bluetooth1-0
> UUIDs =
> dbus.Array([dbus.String(u'00001103-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000110e-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000110c-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000110a-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'0000111f-0000-1000-8000-00805f9b34fb'),
> dbus.String(u'00001112-0000-1000-8000-00805f9b34fb')],
> signature=dbus.Signature('s'), variant_level=1)
> Address = 00:02:72:24:02:04
> RSSI = -38
> Class = 0x4a0100
> Trusted = 1
> Icon = computer
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth2 ~ # bluez-test-network 00:02:72:24:02:04 nap
> Traceback (most recent call last):
> File "/usr/bin/bluez-test-network", line 45, in <module>
> iface = network.Connect(service)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 68,
> in __call__
> return self._proxy_method(*args, **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 143,
> in __call__
> **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line
> 630, in call_blocking
> message, timeout)
> dbus.exceptions.DBusException:
> org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with
> signature "s" on interface "org.bluez.Network" doesn't exist
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth2 ~ # monitor-bluetooth
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth2 bluetooth # hcidump -i hci0
> HCI sniffer - Bluetooth packet analyzer ver 2.3
> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>
> -------------------------------------------------------------------------------------
>
> -------------------------------------------------------------------------------------
>
>
> monitor and hcidump at bluetooth2 when bluetooth1 tries to connect:
>
> bluetooth2 ~ # monitor-bluetooth
> {Device.PropertyChanged} [/org/bluez/2937/hci0/dev_00_02_72_24_02_04]
> Connected = 1
> {Device.PropertyChanged} [/org/bluez/2937/hci0/dev_00_02_72_24_02_04]
> Connected = 0
>
> -------------------------------------------------------------------------------------
>
>
> bluetooth2 bluetooth # hcidump -i hci0
> HCI sniffer - Bluetooth packet analyzer ver 2.3
> device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> > HCI Event: Connect Request (0x04) plen 10
> bdaddr 00:02:72:24:02:04 class 0x4a0100 type ACL
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> bdaddr 00:02:72:24:02:04 role 0x00
> Role: Master
> > HCI Event: Command Status (0x0f) plen 4
> Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> > HCI Event: Role Change (0x12) plen 8
> status 0x00 bdaddr 00:02:72:24:02:04 role 0x00
> Role: Master
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x00 handle 12 bdaddr 00:02:72:24:02:04 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: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
> < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
> handle 12 page 1
> > HCI Event: Max Slots Change (0x1b) plen 3
> handle 12 slots 5
> > 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 00:02:72:24:02:04 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 00:02:72:24:02:04 name 'bluetooth1-0'
> > HCI Event: Link Key Request (0x17) plen 6
> bdaddr 00:02:72:24:02:04
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> bdaddr 00:02:72:24:02:04 key C6A4D268E42E81CAD233A2C61FA7993A
> > HCI Event: Command Complete (0x0e) plen 10
> Link Key Request Reply (0x01|0x000b) ncmd 1
> status 0x00 bdaddr 00:02:72:24:02:04
> > HCI Event: Encrypt Change (0x08) plen 4
> status 0x00 handle 12 encrypt 0x01
> > ACL data: handle 12 flags 0x02 dlen 10
> L2CAP(s): Info req: type 2
> < ACL data: handle 12 flags 0x00 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> > ACL data: handle 12 flags 0x02 dlen 10
> L2CAP(s): Info req: type 3
> < ACL data: handle 12 flags 0x00 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 2
> > ACL data: handle 12 flags 0x02 dlen 12
> L2CAP(s): Connect req: psm 15 scid 0x0040
> < ACL data: handle 12 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
> Connection pending - No futher information available
> < ACL data: handle 12 flags 0x00 dlen 10
> L2CAP(s): Info req: type 2
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 2
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x00b8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Fixed Channels
> < ACL data: handle 12 flags 0x00 dlen 10
> L2CAP(s): Info req: type 3
> > ACL data: handle 12 flags 0x02 dlen 20
> L2CAP(s): Info rsp: type 3 result 0
> Fixed channel list 0x00000002
> L2CAP Signalling Channel
> < ACL data: handle 12 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
> Connection pending - Authorization pending
> < ACL data: handle 12 flags 0x00 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 3 status 0
> Connection refused - security block
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 2
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12 packets 1
> > HCI Event: Disconn Complete (0x05) plen 4
> status 0x00 handle 12 reason 0x13
> Reason: Remote User Terminated Connection
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I dealed the last few days with this problem, but I didn't gained any
new information =(
I really don't know how to fix this problem.
Why can't I create a connection between my two devices?
Please help me, I really don't know what to do.
Regards,
Steffen
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2012-05-14 22:23 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-24 11:35 Can't connect Bluetooth Devices Steffen Becker
2012-04-24 20:57 ` Steffen Becker
2012-04-27 7:31 ` Steffen Becker
2012-05-02 22:54 ` Steffen Becker
2012-05-02 22:58 ` Gustavo Padovan
2012-05-03 8:02 ` Steffen Becker
2012-05-03 9:44 ` Johan Hedberg
2012-05-06 18:35 ` Steffen Becker
2012-05-09 12:05 ` Steffen Becker
2012-05-09 14:28 ` Steffen Becker
2012-05-14 22:23 ` Steffen Becker
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).