From: Pete Zaitcev <zaitcev@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: How to snoop traffic
Date: Mon, 28 Dec 2009 17:44:08 -0700 [thread overview]
Message-ID: <20091228174408.30cc5065@redhat.com> (raw)
In-Reply-To: <1262043222.16627.100.camel@localhost.localdomain>
On Mon, 28 Dec 2009 15:33:42 -0800
Marcel Holtmann <marcel@holtmann.org> wrote:
> > What is the preferred method to snoop the Bluetooth traffic?
> just use hcidump -X -V. It will trace and decode the Bluetooth HCI
> traffic for you.
Thanks a lot. As it turned out, my distribution (Fedora) packaged
it into a nondefault package (bluez-hcidump), so I missed it, sorry.
I thought we might've moved to a libpcap-based capture while I wasn't
looking, but fortunately not.
-- Pete
next prev parent reply other threads:[~2009-12-29 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 23:28 How to snoop traffic Pete Zaitcev
2009-12-28 23:33 ` Marcel Holtmann
2009-12-29 0:44 ` Pete Zaitcev [this message]
2009-12-29 2:20 ` 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=20091228174408.30cc5065@redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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;
as well as URLs for NNTP newsgroup(s).