* [Bluez-devel] BlueZ: Accepting incoming traffic
@ 2005-05-01 13:38 Joshua Davis
2005-05-01 13:51 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Joshua Davis @ 2005-05-01 13:38 UTC (permalink / raw)
To: bluez-devel
Hi! I've been working on a nice little Linux app using bluez. To
finalize it, I need to create a routine that listens for devices searching
for other devices. I've tried reading hcid source, but couldn't ffigure
out how it does this. I've also gone through the bluez-lib source and
couldn't find any routine designed for this. I've also tried opening a
sock_raw hci socket, and that doesn't work either (reading from it simply
blocks; probing for listening devices with my pda, my computer sees this
but doesn't pass it to my program).
Any thoughts?
Thanks.
----
Joshua Davis
Transient Infrastructure Security Solutions
/"\
\ / ASCII Ribbon Campaign
X against HTML email & vCards
/ \
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 13:38 [Bluez-devel] BlueZ: Accepting incoming traffic Joshua Davis
@ 2005-05-01 13:51 ` Marcel Holtmann
2005-05-01 14:26 ` Joshua Davis
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2005-05-01 13:51 UTC (permalink / raw)
To: bluez-devel
Hi Joshua,
> I've been working on a nice little Linux app using bluez. To
> finalize it, I need to create a routine that listens for devices searching
> for other devices. I've tried reading hcid source, but couldn't ffigure
> out how it does this. I've also gone through the bluez-lib source and
> couldn't find any routine designed for this. I've also tried opening a
> sock_raw hci socket, and that doesn't work either (reading from it simply
> blocks; probing for listening devices with my pda, my computer sees this
> but doesn't pass it to my program).
you won't see remote devices that are inquiring you.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 13:51 ` Marcel Holtmann
@ 2005-05-01 14:26 ` Joshua Davis
2005-05-01 14:56 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Joshua Davis @ 2005-05-01 14:26 UTC (permalink / raw)
To: bluez-devel
This is an impossibility? I know that using hciconfigure and hcid I can
set what name my computer uses to respond to probes. Something on my
computer is thus hearing these probes. Is this just taking place in the
kernel?
----
Joshua Davis
Transient Infrastructure Security Solutions
/"\
\ / ASCII Ribbon Campaign
X against HTML email & vCards
/ \
On Sun, 1 May 2005, Marcel Holtmann wrote:
> Hi Joshua,
>
> > I've been working on a nice little Linux app using bluez. To
> > finalize it, I need to create a routine that listens for devices searching
> > for other devices. I've tried reading hcid source, but couldn't ffigure
> > out how it does this. I've also gone through the bluez-lib source and
> > couldn't find any routine designed for this. I've also tried opening a
> > sock_raw hci socket, and that doesn't work either (reading from it simply
> > blocks; probing for listening devices with my pda, my computer sees this
> > but doesn't pass it to my program).
>
> you won't see remote devices that are inquiring you.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 14:26 ` Joshua Davis
@ 2005-05-01 14:56 ` Marcel Holtmann
2005-05-01 15:13 ` Joshua Davis
2005-05-01 20:10 ` [Bluez-devel] authentication problem - link_key prevents from pairing Ruben Jenster
0 siblings, 2 replies; 13+ messages in thread
From: Marcel Holtmann @ 2005-05-01 14:56 UTC (permalink / raw)
To: bluez-devel
Hi Joshua,
> This is an impossibility? I know that using hciconfigure and hcid I can
> set what name my computer uses to respond to probes. Something on my
> computer is thus hearing these probes. Is this just taking place in the
> kernel?
it is taking place inside the Bluetooth chip itself. No further
interaction with the host stack is needed.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 14:56 ` Marcel Holtmann
@ 2005-05-01 15:13 ` Joshua Davis
2005-05-01 15:23 ` Marcel Holtmann
2005-05-01 20:10 ` [Bluez-devel] authentication problem - link_key prevents from pairing Ruben Jenster
1 sibling, 1 reply; 13+ messages in thread
From: Joshua Davis @ 2005-05-01 15:13 UTC (permalink / raw)
To: bluez-devel
I see. So when we tell it not to respond to probes, we are just setting
a bit in the chip? There is memory in the chip to store the name, then?
THis is correct?
Thanks :)
----
Joshua Davis
Transient Infrastructure Security Solutions
/"\
\ / ASCII Ribbon Campaign
X against HTML email & vCards
/ \
On Sun, 1 May 2005, Marcel Holtmann wrote:
> Hi Joshua,
>
> > This is an impossibility? I know that using hciconfigure and hcid I can
> > set what name my computer uses to respond to probes. Something on my
> > computer is thus hearing these probes. Is this just taking place in the
> > kernel?
>
> it is taking place inside the Bluetooth chip itself. No further
> interaction with the host stack is needed.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 15:13 ` Joshua Davis
@ 2005-05-01 15:23 ` Marcel Holtmann
2005-05-01 15:41 ` Joshua Davis
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2005-05-01 15:23 UTC (permalink / raw)
To: bluez-devel
Hi Jushua,
> I see. So when we tell it not to respond to probes, we are just setting
> a bit in the chip? There is memory in the chip to store the name, then?
> THis is correct?
yes, this is correct.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 15:23 ` Marcel Holtmann
@ 2005-05-01 15:41 ` Joshua Davis
2005-05-01 15:48 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Joshua Davis @ 2005-05-01 15:41 UTC (permalink / raw)
To: bluez-devel
Is this spec? Would you ever expect to see software-controlled versions
of this funcitonality in the future?
----
Joshua Davis
Transient Infrastructure Security Solutions
/"\
\ / ASCII Ribbon Campaign
X against HTML email & vCards
/ \
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] BlueZ: Accepting incoming traffic
2005-05-01 15:41 ` Joshua Davis
@ 2005-05-01 15:48 ` Marcel Holtmann
0 siblings, 0 replies; 13+ messages in thread
From: Marcel Holtmann @ 2005-05-01 15:48 UTC (permalink / raw)
To: bluez-devel
Hi Joshua,
> Is this spec? Would you ever expect to see software-controlled versions
> of this funcitonality in the future?
the HCI separates the host stack from the link manager, baseband and
radio inside the Bluetooth chip. This is how Bluetooth was designed and
I doubt that there will be any software-controlled version. However you
might wanna look at the GNU radio project and build up your own
Bluetooth chip based on it.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bluez-devel] authentication problem - link_key prevents from pairing
2005-05-01 14:56 ` Marcel Holtmann
2005-05-01 15:13 ` Joshua Davis
@ 2005-05-01 20:10 ` Ruben Jenster
2005-05-01 23:19 ` Marcel Holtmann
1 sibling, 1 reply; 13+ messages in thread
From: Ruben Jenster @ 2005-05-01 20:10 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
Hi,
I've a really enerving problem.
On my desktop I'm not able to pair my headset without
deleting /etc/bluetooth/link_key. After deleting the link_key
the pinhelper pops up and asks for the pin. I insert them and
I'm able to connect.
My bluetooth dongle is from allnet and is attached to the usb port of a
nforce2 mobo.
I allready submitted a bug report at the kde bugtracker cause I thought
this is a kdebluetooth problem. Please look at
http://bugs.kde.org/show_bug.cgi?id=104876 which could also be usefull
information.
I tried all versions of bluez-utils and bluez-libs from 2.7 till 2.16
and kdebluetooth from 20041107 till 0.99_beta1 in nearly every combination but
everytime the same problem.
Curious is that on my thinkpad (T41p) evertime I pair my headset with the
buildtin bluetooth module I'm asked for the PIN.
I'm really stumped. Please help me.
Regards
Ruben
[-- Attachment #2: hciconfig.info --]
[-- Type: text/plain, Size: 1277 bytes --]
Bluetooth Dongle Allnet 1575
hci0: Type: USB
BD Address: 00:0C:55:FD:8E:6B ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:708 acl:0 sco:0 events:25 errors:0
TX bytes:335 acl:0 sco:0 commands:23 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Thinkpad (0)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
Thinkpad T41p internal bluetooth
hci0: Type: USB
BD Address: 00:20:E0:7D:21:C7 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:384 acl:0 sco:0 events:17 errors:0
TX bytes:309 acl:0 sco:0 commands:16 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Thinkpad (1)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x222 LMP Ver: 1.1 (0x1) LMP Subver: 0x222
Manufacturer: Cambridge Silicon Radio (10)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] authentication problem - link_key prevents from pairing
2005-05-01 20:10 ` [Bluez-devel] authentication problem - link_key prevents from pairing Ruben Jenster
@ 2005-05-01 23:19 ` Marcel Holtmann
2005-05-02 11:27 ` Ruben Jenster
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2005-05-01 23:19 UTC (permalink / raw)
To: bluez-devel
Hi Ruben,
> I've a really enerving problem.
>
> On my desktop I'm not able to pair my headset without
> deleting /etc/bluetooth/link_key. After deleting the link_key
> the pinhelper pops up and asks for the pin. I insert them and
> I'm able to connect.
use the latest BlueZ utilities and run "hcidump -X -V" as root, so we
can see what is going on.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] authentication problem - link_key prevents from pairing
2005-05-01 23:19 ` Marcel Holtmann
@ 2005-05-02 11:27 ` Ruben Jenster
2005-05-02 12:05 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Ruben Jenster @ 2005-05-02 11:27 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Monday 02 May 2005 01:19, Marcel Holtmann wrote:
> Hi Ruben,
>
> > I've a really enerving problem.
> >
> > On my desktop I'm not able to pair my headset without
> > deleting /etc/bluetooth/link_key. After deleting the link_key
> > the pinhelper pops up and asks for the pin. I insert them and
> > I'm able to connect.
>
> use the latest BlueZ utilities and run "hcidump -X -V" as root, so we
> can see what is going on.
Ok, I've attached the hcidump output
test sequence:
deleting link_key (if existent)
pair with headset (btsco2 00:0D:B5:80:21:04 )
success -> successfull attempt (after having link_key deleted)
switching headset off
pair with headset (btsco2 00:0D:B5:80:21:04 )
failure -> authentication problem (when not having link_key deleted)
Regards
Ruben
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
--
a bug a day keeps the boredom away
--
a bug a day keeps the boredom away
[-- Attachment #2: failure --]
[-- Type: text/plain, Size: 6937 bytes --]
HCI sniffer - Bluetooth packet analyzer ver 1.20
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
Read Voice Setting (0x03|0x0025) ncmd 1
status 0x00 voice setting 0x0060
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0D:B5:80:21:04 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 Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -79
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 b1 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -71
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 b9 ....
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 41 bdaddr 00:0D:B5:80:21:04 type ACL encrypt 0x00
Error: Authentication Failure
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0D:B5:80:21:04 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 Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -63
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 c1 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -56
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 c8 ....
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -48
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 d0 ....
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 42 bdaddr 00:0D:B5:80:21:04 type ACL encrypt 0x00
Error: Authentication Failure
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0D:B5:80:21:04 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 Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -25
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 e7 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -18
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 ef ....
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -10
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 f6 ....
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 43 bdaddr 00:0D:B5:80:21:04 type ACL encrypt 0x00
Error: Authentication Failure
[-- Attachment #3: success --]
[-- Type: text/plain, Size: 21506 bytes --]
HCI sniffer - Bluetooth packet analyzer ver 1.20
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
Read Voice Setting (0x03|0x0025) ncmd 1
status 0x00 voice setting 0x0060
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0D:B5:80:21:04 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 Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -39
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 d9 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -31
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 e1 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -24
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 e9 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -16
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 f0 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -8
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 f8 ....
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi -1
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 ff ....
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
bdaddr 00:0D:B5:80:21:04
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0D:B5:80:21:04
Link key: 9e4a271a86f19fbc2574dd53cb0db94c
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
> HCI Event: PIN Code Request (0x16) plen 6
bdaddr 00:0D:B5:80:21:04
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
bdaddr 00:0D:B5:80:21:04 len 4 pin '1234'
> HCI Event: Command Complete (0x0e) plen 10
PIN Code Request Reply (0x01|0x000d) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
bdaddr 00:0D:B5:80:21:04 len 4 pin '1234'
> HCI Event: Command Complete (0x0e) plen 10
PIN Code Request Reply (0x01|0x000d) ncmd 1
status 0x00 bdaddr 00:0D:B5:80:21:04
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x02 handle 0 rssi 7
Error: Unknown Connection Identifier
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 0
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 02 00 00 07 ....
> HCI Event: Link Key Notification (0x18) plen 23
bdaddr 00:0D:B5:80:21:04 type 0x00
Link key: 3a0b633d4f2fae8b4d8df66ccee1f766
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 41 bdaddr 00:0D:B5:80:21:04 type ACL encrypt 0x01
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 41 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
bdaddr 00:0D:B5:80:21:04 mode 1
> HCI Event: Command Complete (0x0e) plen 6
Write Link Policy Settings (0x02|0x000d) ncmd 1
status 0x00 handle 41
> HCI Event: Max Slots Change (0x1b) plen 3
handle 41 slots 5
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0042 scid 0x0040 result 1 status 2
Connection pending - Authorization pending
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0042 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0042 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 48
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0042 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 24
L2CAP(d): cid 0x0042 len 20 [psm 1]
SDP SSA Req: tid 0x0 len 0xf
pat uuid-16 0x1108 (Headset)
max 65535
aid(s) 0x0000 - 0xffff
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 52
L2CAP(d): cid 0x0040 len 48 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x2b
count 38
cont 02 00 36
< ACL data: handle 41 flags 0x02 dlen 26
L2CAP(d): cid 0x0042 len 22 [psm 1]
SDP SSA Req: tid 0x1 len 0x11
pat uuid-16 0x1108 (Headset)
max 65535
aid(s) 0x0000 - 0xffff
cont 02 00 36
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 4
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
> ACL data: handle 41 flags 0x02 dlen 52
L2CAP(d): cid 0x0040 len 48 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x2b
count 38
cont 02 00 10
< ACL data: handle 41 flags 0x02 dlen 26
L2CAP(d): cid 0x0042 len 22 [psm 1]
SDP SSA Req: tid 0x2 len 0x11
pat uuid-16 0x1108 (Headset)
max 65535
aid(s) 0x0000 - 0xffff
cont 02 00 10
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 28
L2CAP(d): cid 0x0040 len 24 [psm 1]
SDP SSA Rsp: tid 0x2 len 0x13
count 16
record #0
aid 0x0000 (SrvRecHndl)
uint 0x10000
aid 0x0001 (SrvClassIDList)
< uuid-16 0x1108 (Headset) uuid-16 0x1203 (Audio) >
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0x1 > >
aid 0x0006 (LangBaseAttrIDList)
< uint 0x656e uint 0x6a uint 0x100 >
aid 0x0009 (BTProfileDescList)
< < uuid-16 0x1108 (Headset) uint 0x100 > >
aid 0x0100 (SrvName)
str "BT808 Headset"
aid 0x0302 (unknown)
bool 0x1
cont 00
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0042 scid 0x0040
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0042 scid 0x0040
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0043 scid 0x0041 result 1 status 2
Connection pending - Authorization pending
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0043 scid 0x0041 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0043 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
MTU 1024
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0043 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0043 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 41
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0043 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 41
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 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 127 max_retrans 0 credits 0
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0043 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 41
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0043 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 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 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 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0043 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 41
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 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 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 15
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 4
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0043 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0043 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0043 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0043 scid 0x0041
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] authentication problem - link_key prevents from pairing
2005-05-02 11:27 ` Ruben Jenster
@ 2005-05-02 12:05 ` Marcel Holtmann
2005-05-02 14:57 ` Ruben Jenster
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2005-05-02 12:05 UTC (permalink / raw)
To: bluez-devel
Hi Ruben,
> > > I've a really enerving problem.
> > >
> > > On my desktop I'm not able to pair my headset without
> > > deleting /etc/bluetooth/link_key. After deleting the link_key
> > > the pinhelper pops up and asks for the pin. I insert them and
> > > I'm able to connect.
> >
> > use the latest BlueZ utilities and run "hcidump -X -V" as root, so we
> > can see what is going on.
>
> Ok, I've attached the hcidump output
>
> test sequence:
> deleting link_key (if existent)
> pair with headset (btsco2 00:0D:B5:80:21:04 )
> success -> successfull attempt (after having link_key deleted)
> switching headset off
> pair with headset (btsco2 00:0D:B5:80:21:04 )
> failure -> authentication problem (when not having link_key deleted)
make sure that only _one_ hcid is running at a time and I don't know
what else programs are you running, but all this RSSI etc. stuff that
uses the handle 0 is wrong.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-devel] authentication problem - link_key prevents from pairing
2005-05-02 12:05 ` Marcel Holtmann
@ 2005-05-02 14:57 ` Ruben Jenster
0 siblings, 0 replies; 13+ messages in thread
From: Ruben Jenster @ 2005-05-02 14:57 UTC (permalink / raw)
To: bluez-devel
On Monday 02 May 2005 14:05, Marcel Holtmann wrote:
> Hi Ruben,
>
> > > > I've a really enerving problem.
> > > >
> > > > On my desktop I'm not able to pair my headset without
> > > > deleting /etc/bluetooth/link_key. After deleting the link_key
> > > > the pinhelper pops up and asks for the pin. I insert them and
> > > > I'm able to connect.
> > >
> > > use the latest BlueZ utilities and run "hcidump -X -V" as root, so we
> > > can see what is going on.
> >
> > Ok, I've attached the hcidump output
> >
> > test sequence:
> > deleting link_key (if existent)
> > pair with headset (btsco2 00:0D:B5:80:21:04 )
> > success -> successfull attempt (after having link_key deleted)
> > switching headset off
> > pair with headset (btsco2 00:0D:B5:80:21:04 )
> > failure -> authentication problem (when not having link_key deleted)
>
> make sure that only _one_ hcid is running at a time and I don't know
> what else programs are you running, but all this RSSI etc. stuff that
> uses the handle 0 is wrong.
This problem even exists when I restart bluetooth services. i checked that
only one instance of hcid is running.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
--
a bug a day keeps the boredom away
--
a bug a day keeps the boredom away
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2005-05-02 14:57 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-01 13:38 [Bluez-devel] BlueZ: Accepting incoming traffic Joshua Davis
2005-05-01 13:51 ` Marcel Holtmann
2005-05-01 14:26 ` Joshua Davis
2005-05-01 14:56 ` Marcel Holtmann
2005-05-01 15:13 ` Joshua Davis
2005-05-01 15:23 ` Marcel Holtmann
2005-05-01 15:41 ` Joshua Davis
2005-05-01 15:48 ` Marcel Holtmann
2005-05-01 20:10 ` [Bluez-devel] authentication problem - link_key prevents from pairing Ruben Jenster
2005-05-01 23:19 ` Marcel Holtmann
2005-05-02 11:27 ` Ruben Jenster
2005-05-02 12:05 ` Marcel Holtmann
2005-05-02 14:57 ` Ruben Jenster
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.