Aaron Turner wrote:
Comments inline...
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?
I took a quick look, and I'd say they were developed independantly. One
would also think that if Ian knew about my capinfo, he wouldn't of used
the same name.
Yes.
As I've had a deeper thinking about the name, I will simply rename our
tool to capinfos (don't like the other suggestions).
We only need a different name, and capinfos reflects that IMHO.
Even the first line under the man page description's for
both capinfo's look remarkably similar to me.
Would a (long term) better course of action be for both
packages, ethereal and tcprelay to use the same
capinfo tool?
I'm agreable to just about anything honestly. If you guys are going to
be maintaining and improving your capinfo, I prolly would even be
willing to pull mine since Ethereal is more well known and that way I
can worry about other things.
Well, as there are already tcprelay and Ethereal packets out there, I
would like to rename our tool.
If someone needs a new feature and implements it, that will be included
into the program. Of course, we will maintain the tool, just like all
the other command line tools we ship.
It might be a good idea to point your users to our capinfos and drop it
from your package (as our's can handle a lot more filetypes). But of
course, that decision is on you.
One other funny thing is, I ship "pcapmerge" and Ethereal ships
"mergepcap". Apparently we've had a few common ideas. :)
Well, I don't wonder :-)
Regards, ULFL
