Ethereal-dev: Re: [Ethereal-dev] ethereal 1.0 features?

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

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Fri, 13 Jul 2001 16:51:36 +0200
On Fri, Jul 13, 2001 at 05:17:20PM +1000, Ronnie Sahlberg wrote:
> 2, Help system, online documentation
> Index, Examples and Tutorial.

IIRC there is some sort of tutorial written by Richard (?)
I agree with the examples. Quite a lot of sample captures have been
posted to the list, but only a few of them are on the web site.
Maybe setting up an archive as "complete" as possible would help
(including a short description what that trace is about: protocol(s),
packets to look at specifically etc).

> 3, More datagram reassembly
> 4, Infrastructure for reassembly of streams

At least the infrastructure should be there - if we want to put every-
thing into 1.0 there won't be much left - just imagine that only dissec-
tors for new protoclls remained to be writeen :-)

> 5, TVBuffification of the remaining dissectors.

a 0.9 thing, so it should be done in 1.0

> 6, Check existing dissectors so all fields have a corresponding hf_ entry
> and are searchable.

see my comment to reassembly and also the post 1.0 comment below.

> 9, Have even more fun using and hacking ethereal.

Yep!

In addition:
10. Move the packet-xxx.[ch] stuff into epan/packet/xxx.[ch]
11. Add capture from stdin to tethereal (maybe this should go into
    wiretap anyway.
12. add capture from RMON probes (IIRC Richard wanted to give it a try)
    to wiretap
13. curses/slang frontend
14. A "compiler" to translate Ethereal (Display) syntax into Tcpdump
    (capture) syntax  so there is only on syntax left. It might just
    tell you which options were ignored because the capture engine
    doesn't support them
15. Add some sort of metadata frames to captures including name resolving
    info and maybe comments about the capture itself


Post 1.0 stuff:

16. Some "packet description language" (as discussed on this list)
17. A compiler to generate dissectors from 16.
18. Graphics frontend to create 16.

  Ciao
       Jï¿œrg

--
Joerg Mayer                                          <jmayer@xxxxxxxxx>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.