Andrew Schweitzer wrote:
> Ok, I think I got it, thanks. So I guess the hf[] array is just a flat
> repository for information about how to display fields in the gui?
The hf[] array is a list of all the fields the dissector *could* use
when dissecting a packet. It has nothing whatsoever to do
On Fri, Sep 01, 2006 at 01:08:53PM -0400, Jose Graziani wrote:
> The current AVS-WLAN header/spec doesn't provide for support for 802.11n
> radio cards.
802.11n doesn't exist yet, and won't for some time. While the first
draft is out, I expect many more revisions before it settles down. If
past 8
Checked in with some changes and reindentation
it would be very nice with a wiki page for this protocol with links to
the standards
On 9/2/06, David Büchi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in addition to the recently submitted dissector for the EPL v2 protocol,
> this is the dissector for
Guy Harris wrote:
> The common practice, however, is to define one array, even with
> protocols that have one data structure per message. There is no
> practical difference between calling proto_register_field_array() once
> and calling it multiple times, other than the latter being slightly le
Andrew Schweitzer wrote:
> Thanks. Is it possible to define multiple arrays of fields, or is it
> common practice to just make one big one? One array per message might
> actually fit quite nicely with the way we have one data structure per
> message in code (more or less).
You *could* have mul
Guy Harris wrote:
>
> Does each of the 100 packet types have fields that appear in no other
> packet type? If so, then, yes, that's a lot of fields, but that's how
> we do it in other protocols.
>
>
Thanks. Is it possible to define multiple arrays of fields, or is it
common practice to just
Bill Meier wrote:
> Minor problem:
>
> I build wireshark only for gtk2.
> For gtk2, a gtk2.tmp directory is created and the Makefile is run from that
> directory.
>
> This causes the 'cd codecs' below (in gtk Makefile.nmake) to fail.
>
> ..\gtk\codecs\codecs.lib:
> cd codecs <<=== f
Andrew Schweitzer wrote:
> Should I use field arrays? That seems like an awful lot of fields (100 *
>about 10) to add to the protocol's field list.
Does each of the 100 packet types have fields that appear in no other
packet type? If so, then, yes, that's a lot of fields, but that's how
w
Hi,
in addition to the recently submitted dissector for the EPL v2 protocol,
this is the dissector for the first version of the EPL protocol.
Best Regards,
David
--
David BuechiZurich University of Applied Sciences Winterthur
Dipl. Ing. FH Institute of Emb
Hi, I'm trying to write a dissector for a proprietary protocol we have,
and I'm trying to figure out the "preffered" way to write this code.
Any suggestions, including "go read X" or "go read X AGAIN" are welcome. :)
I've taken a look at the developer PDF and readme, and they've got me
pretty f
Hi,
I removed that output completely.
Brg
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Oleg Kostenko
Skickat: den 30 augusti 2006 20:17
Till: wireshark-dev@wireshark.org
Ämne: [Wireshark-dev] Megaco dissector: problem with dissection
ofMediaDescrip
Joerg Mayer wrote:
> Well, for me it detects portaudio, but either my version is too new or
> too old, at least my portaudio.h doesn't contain a definition of
> PortAudioStream, and thus compilation fails in line rtp_player.c, line
> 150: PortAudioStream *pa_stream;
I've got a similar problem on a
12 matches
Mail list logo
