Hi,
I'm running slackware Linux 7.0, with v 2.2.17 of the kernal,
GTK 1.2.6, and ethereal v 0.8.18, and am having a problem
looking at the Protocol Hierarchy stats on the file included
(reading the file uncompressed, zipped here to make the mail
smaller).
I start up ethereal (installed both by compiling it myself and
from a pre-compiled binary), and it gives the following messages
to the shell:
pc055.cs.york.ac.uk$ ethereal -v
Cannot find module (IP-MIB): At line 1 in (none)
Cannot find module (IF-MIB): At line 1 in (none)
Cannot find module (TCP-MIB): At line 1 in (none)
Cannot find module (UDP-MIB): At line 1 in (none)
Cannot find module (SNMPv2-MIB): At line 1 in (none)
Cannot find module (SNMPv2-SMI): At line 1 in (none)
Cannot find module (UCD-SNMP-MIB): At line 1 in (none)
Cannot find module (UCD-DEMO-MIB): At line 1 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 1 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 1 in (none)
Cannot find module (UCD-DLMOD-MIB): At line 1 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 1 in (none)
Cannot find module (SNMP-MPD-MIB): At line 1 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 1 in (none)
Cannot find module (SNMP-NOTIFICATION-MIB): At line 1 in (none)
Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Cannot find module (SNMPv2-TM): At line 1 in (none)
Gdk-WARNING **: locale not supported by C library
ethereal 0.8.18, with GTK+ 1.2.6, with GLib 1.2.6, without libpcap, with libz 1.1.3, with UCD SNMP 4.2
I then open the included file (packet06_afternoon_03.3804), go
to tools, protocol hierarchy statistics, then the progress bar
gets to about 95%, before ethereal bombs out, with the following
error to the shell:
pc055.cs.york.ac.uk$
** ERROR **: file proto.c: line 998 (proto_tree_add_string): assertion failed: (hfinfo->type == FT_STRING)
aborting...
[4]+ Aborted ethereal (wd: /local/hda3/davidh/netmonitor/ethereal-0.8.18)
(wd now: /local/hda3/davidh/netlogs)
I have a few other examples of files which cause this error,
which I can provide if you wish. I also have a few files,
gathered in the same way, which will produce this protocol
information.
The files are produced using tcpdump, on a linux box, of the
same build, using the options:
tcpdump -s 196 -w filename
I was interested in the breakdown of what protocols are appearing in a troubbled segment of my network.
Also, a facility to print this screen would be really useful, at present I take a snapshot and print the gif produced.
Yours
Dave Hartburn
--
Dave Hartburn ex: 4725 Room: CS/120J
Network Manager, Department Of Computer Science
University Of York, Heslington
York, YO10 5DD Tel: 01904 434725