ali alkhalidi wrote:
> greetings All,
>
> I know that this sounds boring (a new wireshark dissector is in the
> block), but no matter how I tackel this problem it beats be off.
>
> I'm following on the README.developer instructions in that after I
> craft my dissector, I only need to place the
Currently wireshark is support to some ERF header format.
ERF header format have a totally 11 types according to document at
http://www.endace.com/support/EndaceRecordFormat.pdf
But wireshark 0.55.9 is only support for type 1 to 4.
I need more type of supported format.
Who can help me..?
On Feb 15, 2007, at 5:35 PM, Michael Lum wrote:
> It would also be nice to have filters associated to the saved
> settings.
"Associated" in the sense that a profile would include a set of
filters as well as a set of properties?
> I believe the capture file is loaded a second time after the
Luis's description is what I was thinking of when I made a suggestion a
long time ago.
I frequently switch between protocol settings, for example:
ANSI MAP
ANSI TCAP
ANSI SCCP
ANSI MTP3
versus
ANSI MAP
ANSI TCAP
ITU SCCP
ITU MTP3
versus
GSM MAP
GSM TCAP
ITU SCCP
ITU MTP3
versus
GSM MAP
GSM
Guy Harris wrote:
> On Feb 15, 2007, at 1:22 PM, Andy Howell wrote:
>
>> Saving setting based on just the file name would not work for me, as I
>> often have files with the same name but different settings. The files
>> end up in different directories.
>
> You probably don't have two files with t
On 2/15/07, Ulf Lamping <[EMAIL PROTECTED]> wrote:
> Luis Ontanon wrote:
> > Overall it looks like a feasable project not something *very* complex
> > to implement.
> >
> You might miss the most work intensive point here: how to compare /
> merge two different sets in a GUI way?
I do not see why t
On Feb 15, 2007, at 1:22 PM, Andy Howell wrote:
> Saving setting based on just the file name would not work for me, as I
> often have files with the same name but different settings. The files
> end up in different directories.
You probably don't have two files with the same name *in the same
Hi,
This patch replaces g_assert() calls in epan/stream.c with
DISSECTOR_ASSERT().
Cheers
Richard
Index: epan/stream.c
===
--- epan/stream.c (revision 11875)
+++ epan/stream.c (working copy)
@@ -380,7 +380,7 @@
/* we don't
Guy Harris wrote:
> One feature that might be useful would be support for a "Wireshark
> settings file" that could be associated with a capture, so that if a
> file named foo.{pcap,cap,...} were opened, Wireshark could look for
> foo.wssettings, or something such as that, and, if it finds, load
Luis Ontanon wrote:
> Well I thought of something similar to this solution as well for some
> time. And yes it is somewhat complex but not *so much*.
>
> Having variuos directories like today's user_dir (from now on a
> prefset) in a meta-user_dir (from now on the prefsets_dir) and being
> able to
Well I thought of something similar to this solution as well for some
time. And yes it is somewhat complex but not *so much*.
Having variuos directories like today's user_dir (from now on a
prefset) in a meta-user_dir (from now on the prefsets_dir) and being
able to switch between them, by loadin
Joerg Mayer wrote:
> On Thu, Feb 15, 2007 at 09:56:56AM -0800, Guy Harris wrote:
>
>> Douglas Pratley wrote:
>>
>>
>>> Following on from recent comments about being able to save "user
>>> decodes", has anyone been working on being able to save Wireshark
>>> settings under different "profi
On Thu, Feb 15, 2007 at 09:56:56AM -0800, Guy Harris wrote:
> Douglas Pratley wrote:
>
> > Following on from recent comments about being able to save "user
> > decodes", has anyone been working on being able to save Wireshark
> > settings under different "profiles"? There's some discussion of th
Douglas Pratley wrote:
> Following on from recent comments about being able to save "user
> decodes", has anyone been working on being able to save Wireshark
> settings under different "profiles"? There's some discussion of this on
> the Wiki, and it would obviously be a very useful feature if
Hi guys
Has anyone had a chance to look at this - I know it's a biggish chunk of
new code.
I ask because I'm sorry to say that I have found some (non-fatal) bugs
that I'd like to correct.
(a) The code causes a GLib assert on start-up (but then goes on working
fine, as this causes NULL to be r
Hi guys
Following on from recent comments about being able to save "user
decodes", has anyone been working on being able to save Wireshark
settings under different "profiles"? There's some discussion of this on
the Wiki, and it would obviously be a very useful feature if user
decodes are persisted
Or you can comment out HHC_DIR in config.nmake.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ulf Lamping
Sent: Thursday, February 15, 2007 9:27 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] help_dlg.c(49) : fatal error C108
Luis Ontanon wrote:
> I got stuck at this point while compiling on windows (MSVC6), what am I
> missing?
>
>
Well, obviously htmlhelp.h ;-)))
You'll need to install the HTML Help Workshop, see the devel guide.
Regards, ULFL
___
Wireshark-dev mailing
I got stuck at this point while compiling on windows (MSVC6), what am I missing?
Thanks,
Luis
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
19 matches
Mail list logo
