Ethereal-dev: Re: [Ethereal-dev] Plugins.c

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

From: Guy Harris <gharris@xxxxxxxxx>
Date: Sat, 2 Mar 2002 11:47:50 -0800
On Sat, Mar 02, 2002 at 10:55:36AM -0800, Rajan S wrote (in HTML; please
    don't sent HTML-only mail to these lists):
> I am trying to build ethereal 0.9.1 on WinNT platform.  I have
> downloaded WinPCAP, GTK+, GLIB and ZLIB development packages.  I am
> getting errors related to "DIR" and "dirent" while compiling.  Do I need
> any other packages???

No.

There's probably something else going wrong.  I, and a number of other
people, have compiled Ethereal from source, using Microsoft Visual C++
6.0 (and some have also used 5.0, I think), with no problem.  Without
seeing the exact text of those errors, I cannot guess what the cause
might be.

> Also, I need to generate statistics for PPP (CRC Errors), IP, TCP
> (Retransmissions) and UDP (Checksum) for a specific link (Once I
> calculate the necessary checksums I will discard the packets).  Is there
> a better way than Ethereal to generate just this.  Or can I extend
> "ethereal" libraries to get this information.

You could modify the Ethereal dissectors for PPP, IP, TCP, and UDP to
calculate those statistics.  There's currently no mechanism in Ethereal
to allow dissectors to register statistics so that other code in
Ethereal (or Tethereal) can display them, however.

Note, though, that, on Windows, you will not necessarily see PPP headers
when you capture on a PPP device - in fact, you probably won't even be
able to capture on PPP devices:

	http://netgroup-serv.polito.it/winpcap/misc/faq.htm

"Q-4: Can I use WinPcap on a PPP connection?

A: We have tested WinPcap on PPP connections under Windows 95, Windows
98 and Windows ME.  In Windows 95, due to a bug in NDIS, WinPcap
sometimes resets the PPP connection.  In Windows 98/ME this bug appears
to be corrected, and WinPcap seems to work properly.  Under Windows NT
and Windows 2000 there are problems with the binding process, that
prevents a protocol driver from working properly on the WAN adapter."