Ethereal-dev: Re: [Ethereal-dev] console errors while loading a capture

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, 1 Jun 2002 14:54:33 -0700
On Sun, Jun 02, 2002 at 12:10:00AM +0200, Yaniv Kaul wrote:
> Happens in 0.9.3/Linux and 0.9.4/Windows.
> 
> While loading a big capture (sorry, I can't send its data...), I'm getting:
> 
> ** WARNING **: Diameter: Unable to open
> /etc/ethereal/diameter/dictionary.xml

Well, the fact that it got that far suggests that you have libxml on
your machine, and Ethereal was able to find the libxml shared object and
load it.

However, it also appears that the XML dictionary for Diameter wasn't
found.

The Diameter dissector thinks it's in the "diameter" subdirectory of the
Ethereal data file directory; however, that's not where the Makefile
installs it, which is a bug.

If any of the files "dictionary.xml", "mobileipv4.xml", "nasreq.xml",
and "sunping.xml" are in the "/etc/ethereal" directory, make a
"diameter" subdirectory of "/etc/ethereal", and move what of those XML
files exist into that subdirectory.

> or in Windows:
> XMLStub: Unable to open module libxml2.dll

Unfortunately, on Windows, it *didn't* find the libxml shared object. 
Check out

	http://xmlsoft.org/

That stuff gets loaded and read if Ethereal sees what it thinks is
Diameter traffic.  By default, it thinks any TCP or SCTP traffic on port
1812 is Diameter traffic; setting those ports to 0 in the protocol
preference item for Diameter should disable that.