Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: [Ethereal-dev] Re: [Ethereal-users] Ethereal binary for Sharp Zaurus (fwd)

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

From: Philippe Biondi <biondi@xxxxxxxxxxxxxxxxxx>
Date: Fri, 14 Mar 2003 12:15:35 +0100 (CET)
Hi!

On Thu, 13 Mar 2003, Gerald Combs wrote:

> Someone sent me a link to ZEthereal today, and you're listed in the README
> file.  It looks great!

Well, it's only a hack for the moment :)

> We're having a discussion about it on ethereal-users.  It appears that
> you're creating a library "libzethereal" from several of Ethereal's object
> files, and linking it to your frontend.  Would it be possible to use this
> method to create an interface using the regular QT libraries,  WxWindows,
> or MFC?

I did this lib because I wanted to use qpe developping tools (ui
and makefile generators) which prevented me from linking to, say,
packet-*.o. So I built a library to gather them :

ar r libzethereal.a packet-*.o afn.o asn1.o column.o conditions.o
capture_stop_conditions.o follow.o in_cksum.o ipproto.o pcap-util.o
prefs.o print.o ps.o ptvcursor.o reassemble.o ringbuffer.o util.o xdlc.o
xmlstub.o register.o


>From the experience I acquired developping zethereal, I see some points
that need to be fixed to easily add new frontends. I've been doing a kind
of wishlist during my experiments, emphasing on what prevented me to do
things quickly.

Don't misunderstand me, the list that follow only focus on problems.
Ethereal is really a great project :)

- put every packet-*.c sources in their own directory !
- make a libpacket from packet-*.o
- lot of code about packet capture is generic but is not made available.
  A direct consequence is that it is duplicated between ethereal
  and tethereal.
  An indirect consequence is that it is also duplicated in zethereal.
  (if tethereal did not have a main, I could have linked to thetereal.o)
- The simultaneous use of wiretap and libpcap does not help clarity.
  There are callbacks, callback wrappers, and so on..
- Lot's of functions seems to be integrated into the UI, like "follow tcp
  stream", or masking packet in the UI (I may be wrong)

The abstract is : it lacks a clean API between core functions and UI.

Anyway, don't hesitate to look at the source
(http://www.cartel-securite.fr/pbiondi/zaurus/). It is very short.



-- 
Philippe Biondi <biondi@ cartel-securite.fr> Cartel Sécurité
Security Consultant/R&D                      http://www.cartel-securite.fr
Phone: +33 1 44 06 97 94                     Fax: +33 1 44 06 97 99
PGP KeyID:3D9A43E2  FingerPrint:C40A772533730E39330DC0985EE8FF5F3D9A43E2