public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth sniff mode
Date: Wed, 01 Dec 2004 20:36:59 +0100	[thread overview]
Message-ID: <1101929819.15615.28.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A48BA128@goofy.vitronics.com>

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 19:14 [Bluez-users] bluetooth sniff mode Cruz, Maria
2004-12-01 19:36 ` Marcel Holtmann [this message]
  -- 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=1101929819.15615.28.camel@pegasus \
    --to=marcel@holtmann.org \
    --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