public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Cruz, Maria" <maria.cruz@VITRONICS.com>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] bluetooth sniff mode
Date: Wed, 1 Dec 2004 14:14:58 -0500	[thread overview]
Message-ID: <A1F0D47583A2D711919F00600819B3A48BA128@goofy.vitronics.com> (raw)

[-- 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 --]

             reply	other threads:[~2004-12-01 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 19:14 Cruz, Maria [this message]
2004-12-01 19:36 ` [Bluez-users] bluetooth sniff mode Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-12-01 21:42 Cruz, Maria
2004-11-30 15:16 Cruz, Maria
2004-12-01  6:29 ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A1F0D47583A2D711919F00600819B3A48BA128@goofy.vitronics.com \
    --to=maria.cruz@vitronics.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox