From: Joshua Wright <jwright@hasborg.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] hcidump version 1.30 and DBT-120 version B-4
Date: Fri, 17 Feb 2006 15:15:11 -0500 [thread overview]
Message-ID: <43F62ECF.7040702@hasborg.com> (raw)
In-Reply-To: <20060217195408.21336.qmail@web61223.mail.yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Deva,
deva seetharam wrote:
> i am trying to run hcidump to sniff bluetooth packets. for some
> reason, hcidump doesn't produce any output eventhough the there is
> plenty of bluetooth traffic in the vicinity (i have verified it
> using MAC OS bluetooth packet logger).
hcidump is a local sniffer, it only is capable of sniffing local HCI
messages. Because Bluetooth is based on FHSS, sniffing traffic out of
the air is a bit more challenging.
The Frontline Test Equipment FTS4BT sniffer is designed to help
developers troubleshoot Bluetooth applications and does give you the
ability to sniff Bluetooth frames. www.fte.com
- -Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFD9i7PTS8i9jZYpL8RAoVSAKDT0wELkbN2ZHP+Ax1z3VH0163lIQCg6pEv
/yB8S42w2/iQCS3y0ivj7h0=
=i66O
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-02-17 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 19:54 [Bluez-users] hcidump version 1.30 and DBT-120 version B-4 deva seetharam
2006-02-17 20:15 ` Joshua Wright [this message]
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=43F62ECF.7040702@hasborg.com \
--to=jwright@hasborg.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;
as well as URLs for NNTP newsgroup(s).