[Bluez-users] bluetooth sniff mode

[Bluez-users] bluetooth sniff mode

[Cruz, Maria]

[-- Attachment #1: Type: text/plain, Size: 192 bytes --]

Hi, I have an 5550 IPAQ I placed in sniff mode (once a BNEP was setup).
How can I verify that the ipaq is really IN sniff mode?  Any hcitool?
hciconfig  commands?

Thanks

Maria Cruz


[-- Attachment #2: Type: text/html, Size: 1540 bytes --]

Re: [Bluez-users] bluetooth sniff mode

[Marcel Holtmann]

Hi Maria,

> I have an 5550 IPAQ I placed in sniff mode (once a BNEP was setup).
> How can I verify that the ipaq is really IN sniff mode?  Any hcitool?
> hciconfig  commands?

I don't know of a command that can read the current power safe mode, but
you can monitor the HCI mode changed event.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] bluetooth sniff mode

[Cruz, Maria]

[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]

Marcel wrote:

Hi Maria, ... I don"t know of a command that can read the current power
safe mode, but you can monitor the HCI mode changed event. Regards
Marcel 

 

Thanks Marcel,

Here is the output from my command:

# hcitool cmd 0x02 0x0003 0x01 0x00 0x00 0x05 0x00 0x01 0x06 0x00 0x10
0x00

< HCI Command: ogf 0x02, ocf 0x0003, plen 10

  01 00 00 05 00 01 06 00 10 00

> HCI Event: 0x0f plen 4

  00 01 03 08

I looked in the "BLUETOOTH SPECIFICATION Version 1.1" for the HCI Event
of 0x0f.  I am not confident in reading the specification.  But I think
this event 0x0f = Command Status.  And the Event Parameters:  (0) "00" =
Command currently in pending. 

 

Not sure if this indicates a success (or just pending not sure yet of
success).  Additionally, I am using bluez-libs&bluez-utils2.10.  Should
I reference the "BLUETOOTH SPECIFICATION Version 2.0 + EDR" instead?  I
found version 2.0 at "Bluetooth.org" web site.  AND the version 2.0 spec
is slightly different.  For example the error codes listed in 2.0 are
different.  

 

Sometimes with the hci cmd for sniff mode I get:

# hcitool cmd 0x02 0x0003 0x01 0x01 0x00 0x00 0x05 0x00

0x01 0x06 0x00 0x10 0x00

< HCI Command: ogf 0x02, ocf 0x0003, plen 11

  01 01 00 00 05 00 01 06 00 10 00

> HCI Event: 0x0f plen 4

  02 01 03 08

 

Here the HCI Event indicates "Status" of 0x02.  

Version 1.1 = 0x02 No Connection.

Version 2.0 = 0x02 Unknown Connection Identifier

 

Maybe it is only semantics... either way I do not understand what either
really mean.  For the sniff mode I have setup a bnep connection.  I can
ping "host", I have static IPs setup.  And 

hcitool con

Connections:

        < ACL 00:02:72:41:2E:1D handle 1 state 1 lm MASTER

 

Should this indicate "SLAVE"?  Somes times hcitool con will show SLAVE
instead.  Your advice on what spec to use and how to decipher hictool
output is appreciated.

maria

 

 

 

 

 


[-- Attachment #2: Type: text/html, Size: 10480 bytes --]

Re: [Bluez-users] bluetooth sniff mode

[Marcel Holtmann]

Hi Maria,

> Here is the output from my command:
>=20
> # hcitool cmd 0x02 0x0003 0x01 0x00 0x00 0x05 0x00 0x01 0x06 0x00 0x10
> 0x00
>=20
> < HCI Command: ogf 0x02, ocf 0x0003, plen 10
>=20
>   01 00 00 05 00 01 06 00 10 00
>=20
> > HCI Event: 0x0f plen 4
>=20
>   00 01 03 08

run "hcidump -X" as root at the same time and see what it produces.

> Not sure if this indicates a success (or just pending not sure yet of
> success).  Additionally, I am using bluez-libs&bluez-utils2.10.
> Should I reference the =93BLUETOOTH SPECIFICATION Version 2.0 + EDR=94
> instead?  I found version 2.0 at =93Bluetooth.org=94 web site.  AND the
> version 2.0 spec is slightly different.  For example the error codes
> listed in 2.0 are different. =20

The BlueZ versions have nothing to do with the version of the Bluetooth
specification.

> Maybe it is only semantics=85 either way I do not understand what eithe=
r
> really mean.  For the sniff mode I have setup a bnep connection.  I
> can ping =93host=94, I have static IPs setup.  And=20
>=20
> hcitool con
>=20
> Connections:
>=20
>         < ACL 00:02:72:41:2E:1D handle 1 state 1 lm MASTER
>=20
> =20
>=20
> Should this indicate =93SLAVE=94?  Somes times hcitool con will show SL=
AVE
> instead.  Your advice on what spec to use and how to decipher hictool
> output is appreciated.

The device that initiates the connection is the master until it switches
its role.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

RE: [Bluez-users] bluetooth sniff mode

[Cruz, Maria]

Thanks Marcel.  I found out that after a "sniff mode" command the HCI
Event : Mode Change occurs.  I found reference to this in both specs.
This event shows a "current_mode" field.  If it is set to "0x02" then in
sniff mode.

Running hcidump -x captures this event.

Thanks
maria

-----Original Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org]=20
Sent: Wednesday, December 01, 2004 2:37 PM
To: BlueZ Mailing List
Subject: Re: [Bluez-users] bluetooth sniff mode

Hi Maria,

> Here is the output from my command:
>=20
> # hcitool cmd 0x02 0x0003 0x01 0x00 0x00 0x05 0x00 0x01 0x06 0x00 0x10
> 0x00
>=20
> < HCI Command: ogf 0x02, ocf 0x0003, plen 10
>=20
>   01 00 00 05 00 01 06 00 10 00
>=20
> > HCI Event: 0x0f plen 4
>=20
>   00 01 03 08

run "hcidump -X" as root at the same time and see what it produces.

> Not sure if this indicates a success (or just pending not sure yet of
> success).  Additionally, I am using bluez-libs&bluez-utils2.10.
> Should I reference the "BLUETOOTH SPECIFICATION Version 2.0 + EDR"
> instead?  I found version 2.0 at "Bluetooth.org" web site.  AND the
> version 2.0 spec is slightly different.  For example the error codes
> listed in 2.0 are different. =20

The BlueZ versions have nothing to do with the version of the Bluetooth
specification.

> Maybe it is only semantics... either way I do not understand what
either
> really mean.  For the sniff mode I have setup a bnep connection.  I
> can ping "host", I have static IPs setup.  And=20
>=20
> hcitool con
>=20
> Connections:
>=20
>         < ACL 00:02:72:41:2E:1D handle 1 state 1 lm MASTER
>=20
> =20
>=20
> Should this indicate "SLAVE"?  Somes times hcitool con will show SLAVE
> instead.  Your advice on what spec to use and how to decipher hictool
> output is appreciated.

The device that initiates the connection is the master until it switches
its role.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.=20
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users