From: Marcel Holtmann <marcel@holtmann.org>
To: JOSERIVERAPONCE@terra.es,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] MSWindows bluetooth sniffer?
Date: Wed, 22 Nov 2006 07:49:55 +0100 [thread overview]
Message-ID: <1164178195.23477.20.camel@localhost> (raw)
In-Reply-To: <23917817.1164177063296.JavaMail.root@cps6>
Hi Jose,
> I am looking for a good MSWindows bluetooth protocol sniffer.
you can use the Merlin from LeCroy or FTS4BT from Frontline, but both
solution will be expensive.
If you are lucky there is a Windows equivalent to hcidump, but don't ask
me. I don't use Windows at all.
> I want to launch the bluetooth application that connects to my
> bluetooth
> mobile phone and be able to see what are they communicating so I can
> write software in Linux to manage that mobile phone.
You can do that without a sniffer. Create the correct SDP records on
another Linux machines and copy the class of device and simple pretend
to be a phone. This way, I hacked most of the secret protocols.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-11-22 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 6:31 [Bluez-devel] MSWindows bluetooth sniffer? JOSERIVERAPONCE
2006-11-22 6:49 ` Marcel Holtmann [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=1164178195.23477.20.camel@localhost \
--to=marcel@holtmann.org \
--cc=JOSERIVERAPONCE@terra.es \
--cc=bluez-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.