Thanks. I see some information on adding dissectors but I wonder if anybody here would briefly explain ethreal internals. Even a hint like how ethereal is intercepting the packets on their way to the upper layers and what hooks it uses in the (Linux) kernel can help me to begin tracing the code and see how it basically works.
thanks,
Farshad
--- On Sun 11/03, Joerg Mayer wrote:
From: Joerg Mayer [mailto: jmayer@xxxxxxxxx]
To: farshadas@xxxxxxxxxx
Cc: ethereal-dev@xxxxxxxxxxxx
Date: Mon, 4 Nov 2002 03:39:45 +0100
Subject: Re: [Ethereal-dev] a naive question
> On Sun, Nov 03, 2002 at 08:36:19PM -0500, Farshad wrote:
> > Is there any document that explains ethereal internals and
> documents
> > its source code?
>
> There exists documentation in the Ethereal source package in the doc/
> subdirectory.
> While it isn't a description of the whole internal workings of ethereal,
> it should contain all (ok, most :-) documentation needed to write your
> own dissector (README.design, README.developer, README.tvbuff), plugin
> (the previous ones + README.plugins) or tap (README.tapping) plus, of
> course the sources. In case questions remain, this list is the right
> place to ask them.
>
> Ciao
> Jörg
>
> --
> Joerg Mayer
>
> I found out that "pro" means "instead of" (as in
> proconsul). Now I know
> what proactive means.
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
