From: Marcel Holtmann <marcel@holtmann.org>
To: Guy Harris <guy@alum.mit.edu>
Cc: Paul Ionescu <paul@acorp.ro>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
ethereal-dev@ethereal.com
Subject: Re: [Ethereal-dev] Re: [Bluez-devel] bluetooth ethereal dissector
Date: 30 Oct 2003 13:22:38 +0100 [thread overview]
Message-ID: <1067516563.11791.23.camel@pegasus> (raw)
In-Reply-To: <81F98C36-0AA1-11D8-BD2F-000A958097E4@alum.mit.edu>
Hi Guy,
> > here is my patch that adds a Wiretap module for reading files created
> > with "hcidump -w".
>
> OK, it reads them - but it supplies a link-layer encapsulation type of
> WTAP_ENCAP_BLUETOOTH_H4, for which there isn't any dissector. Do you
> have dissectors for various Bluetooth protocols, or should we take the
> ones from the affix patches to Ethereal and modify one of them (HCI?)
> to register for an encapsulation of WTAP_ENCAP_BLUETOOTH_H4?
it is the first step ;)
Actually I don't want to use the Affix code, because I don't like the
idea of using code that I don't understand. And at the moment I have
limited knowlodge how the Ethereal dissectors work.
However the Bluetooth H4 format is a standard definied in the Bluetooth
specification and my plan is to write a packet-bt-hci.c dissector that
can decode it. All other Bluetooth layers like L2CAP, RFCOMM, BNEP etc.
should be done by someone else. The HCI dissector is the important one,
because it can make it reusable for other Bluetooth protocol stacks and
my plan is to do it from scratch and not hacking the current Affix code.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-10-30 12:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 22:11 [Bluez-devel] bluetooth ethereal dissector Paul Ionescu
2003-10-29 8:54 ` James Courtier-Dutton
2003-10-29 11:17 ` Marcel Holtmann
2003-10-29 20:16 ` [Ethereal-dev] " Guy Harris
2003-10-29 11:07 ` Marcel Holtmann
2003-10-29 19:26 ` [Ethereal-dev] " Guy Harris
2003-10-30 2:50 ` Marcel Holtmann
2003-10-30 3:13 ` Guy Harris
2003-10-30 11:39 ` Marcel Holtmann
2003-10-30 11:54 ` Guy Harris
2003-10-30 12:49 ` Marcel Holtmann
2003-10-30 6:22 ` Guy Harris
2003-10-30 12:22 ` 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=1067516563.11791.23.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ethereal-dev@ethereal.com \
--cc=guy@alum.mit.edu \
--cc=paul@acorp.ro \
/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.