Ethereal-dev: Re: [ethereal-dev] [LEEDSNET] Error output & logginf whilst developing ethereal

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Florian Lohoff <flo@xxxxxxxxxx>
Date: Fri, 24 Mar 2000 14:03:50 +0100
On Fri, Mar 24, 2000 at 06:32:13AM -0600, Gilbert Ramirez wrote:
> On Thu, Mar 23, 2000 at 07:51:21PM +0000, Leedsnet wrote:
> > 
> > On a separate issue, has putting the packet-*.c sources in their
> > own directory ever been proposed?
> > 
> > Ben.
> 
> Not for the current incarnation of Ethereal. After we finish up
> a few long outstanding items, we'll announce 1.0 and work on a
> re-design of Ethereal, putting the dissectors and the infrastructure
> (display filters, proto_tree) in a library so that other applications
> can share the work we've done with the packet dissectors. During
> that work we'll arrange the directories better. When Gerald started
> Ethereal I don't think he had any idea that Ethereal would become so
> popular and attract so many developers, so he just placed the
> few dissectors he had in the top-level directory along with all the
> source.

Just for the whishlist - A generic "Find answer ..." and/or "Find request ..."
to find DNS Requests/DNS Responses, Radius, ICMP Echo etc for all the protocols
consisting of Request/Response mechanisms.

Another one: Some kind of "Recursive" packet-dissect for all the "Tunneling"
and or "Encapsulate" protocols like L2TP/GRE/PPTP etc to have a deeper
look into the packets in the tunnel - Probably just like Follow-tcp-stream
to save a dump of the encapsulated packets and reopen it seperatly.

Flo
-- 
Florian Lohoff		flo@xxxxxxxxxx		      	+49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."