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: Jeff Foster <jfoste@xxxxxxxxxxxx>
Date: Fri, 13 Jul 2001 13:58:33 -0500
1) Fix printing in Windows. This should look like a standard Window print dialog. 2) Add Stop Capture to main window menus in Windows version. 3) Convert the H323 code to a plugin. This sounds easy but involves using C++ to compile, and I don't know what issues may arise. 4) Better name resolution support. This should include - Options to enable/disable reverse lookups Use name data in the capture Reverse lookup cache Option to save reverse lookup cache information to file User defined mappings. Ability to set the order that tables are checked i.e. 1st. Check Users Maps 2nd. Check cache... 5) Put Protocol preferences on one tabbed item in the preferences dialog box and use a scrolled list for all the protocols. Beyond version 1.0 - A distributed sniffer system - This would entail breaking the sniffer into a client-server system with the server to capture the data and transmit information back to client. The system should be designed to operate over slow remote links. I can dream can't I... Jeff Foster jfoste@xxxxxxxxxxxx -----Original Message----- From: Ed Warnicke [mailto:hagbard@xxxxxxxxxxxxxxxxxxx] Sent: Friday, July 13, 2001 8:48 AM To: Ronnie Sahlberg Cc: ethereal-dev@xxxxxxxxxxxx Subject: Re: [Ethereal-dev] ethereal 1.0 features? I would also like us to consider addressing the following two possibilities for 1.0: 1) Splitting the libethereal backend and the wiretap library cleanly free of ethereal so they can be used by other programs. 2) Improving ethereals capacity to scale with very large captures. Let's face it, the current algorithms and data structures we use, while fine for small to medium size captures, scale really badly. Other Comments inline... On Fri, 13 Jul 2001, Ronnie Sahlberg wrote: > Hi list. > > Some thoughts of what I would like to see in a future 1.0 release: > (very incomplete list) > > 1, More documentation: > When defining a preference option, as say the IPv4 reassemble button, one > should also specify an additional > parameter which contains a long long text string, or as an alternative a > pointer into a text file. > This would be implemented so that in addition to the button in preferences > which toggles the option on/off > there would be a HELP button which would display the specified text. > Would perhaps be easy for the GTK gurus to implement. > > 2, Help system, online documentation > Index, Examples and Tutorial. > > 3, More datagram reassembly > IPX, NBDGM, the three TRANSACTION functions in SMB, fragments in PGM should > get reassembly support. > > 4, Infrastructure for reassembly of streams > (Needs small changes/additions for packet-tcp and reassembly to fit in > nicely) > so we easily can get reassembly for > NBSS, RPCoverTCP, (SPX?) > > 5, TVBuffification of the remaining dissectors. > > 6, Check existing dissectors so all fields have a corresponding hf_ entry > and are searchable. This is a big task ( but a VERY important one I think ). One of the big selling points of ethereal to my coworkers is the filtering capacity. Without the hf_ enteries to tag ALL of the the data there is not searchability. > > (stuff that less people really care about. I would want it though) > 7, NFS filehandle->filename snooping. > Implement snooping of NFS packets to determine fhandle->filename mapping of > nfs files. > Update the dissector for NFS filehandles to show the filename as well for > all fhandles where a match is found. > Perhaps as a generic API so the same code can be reused for > SMB,AFS,DNS,Ethernet->IP, Ethernet->hostname, ... > > > 8, Informing the web/network-magazines when 1.0 is released. A lot of people > would use ethereal if only they knew it existed. > In my opinion ethereal is really today much more competent and useful for > analyzing captures than almost anything else out there. > It is an honour to me to be able to contribute to such an extremely > competent and useful tool. This is a good idea. > > 9, Have even more fun using and hacking ethereal. > > > best regards > ronnie sahlberg > > > > _______________________________________________ > Ethereal-dev mailing list > Ethereal-dev@xxxxxxxxxxxx > http://www.ethereal.com/mailman/listinfo/ethereal-dev > _______________________________________________ Ethereal-dev mailing list Ethereal-dev@xxxxxxxxxxxx http://www.ethereal.com/mailman/listinfo/ethereal-dev *** The information in this e-mail is confidential and intended solely for the individual or entity to whom it is addressed. If you have received this e-mail in error please notify the sender by return e-mail, delete this e-mail, and refrain from any disclosure or action based on the information. ****
- Follow-Ups:
- Re: [Ethereal-dev] ethereal 1.0 features?
- From: Guy Harris
- Re: [Ethereal-dev] ethereal 1.0 features?
- Prev by Date: Re: [Ethereal-dev] General plugins
- Next by Date: Re: [Ethereal-dev] ethereal 1.0 features?
- Previous by thread: Re: [Ethereal-dev] ethereal 1.0 features?
- Next by thread: Re: [Ethereal-dev] ethereal 1.0 features?
- Index(es):