Jim Young wrote:
How about: "capstat" or "capstats"?
I think they're OK, but, when the name was being discussed, the author
of capinfo mentioned capstat as a possible name, but said he considered
it misleading:
http://www.ethereal.com/lists/ethereal-dev/200407/msg00572.html
Of course a quick google search will show that both the
capstat and capstats names have a meaning and use
elsewhere!
Yes, but a quick look at the first pages of those Google searches didn't
show any network-capture-handling software with those names.
Is it just me or do these tools have similar functionality?
I haven't looked at the tcprelay's capinfo source nor
the reports it generates (yet) but it smells like they
both may have diverged from common source?
Unless the tcpreplay people picked up the Wiretap code for reading
capture files at the time that they did capinfo or before they did
capinfo, they didn't diverge from common source.
Would a (long term) better course of action be for both
packages, ethereal and tcprelay to use the same
capinfo tool?
Perhaps, but tcpreplay (or, at least, its capinfo) would then depend on
the Wiretap library from the Ethereal distribution; the tcpreplay people
might not want that. Note that the Wiretap API is subject to change
(and probably *will* change when the next-generation libpcap format
comes out, in order to support the new file format's capabilities).