Re: [TCPIP V5.4] Found a bug again ;-)

From: Matt Muggeridge (Matt.Muggeridge_at_hp.com)
Date: 02/29/04 

Date: Sun, 29 Feb 2004 22:41:53 GMT

"Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message
news:newscache$dk8rth$02v$1@news.sil.at...

>
>Unfortunately, TCPTRACE stops after 10 packets (unless you specify
/PACKET=xx
>where xx isn't 10) so it seems TCPTRACE treats /PACKETS as default.
>And I think, this is not good, so the software should be fixed.
>
>Do you agree ?

In this case, there is no real sense of what is right, or wrong behaviour.
If we polled 100 people, 40 would say go left, 40 would say go right, and 20
would run into the lampost we were trying to avoid.

This starts getting into the more emotional justification versus
straight-forward technical decisions. Though, for the sake of avoiding the
lampost, some decision needs to be made.

Since the default behaviour can readily be overridden, and it is well
documented, I am not in favour of changing existing (even if a littly
quirky) behaviour that others may have come to rely upon.

As an aside... as of V5.4, you can also use 'tcpdump' to obtain your trace
data. It is a far more powerful tool, and happens to provide the default
behaviour you desire. Further, since it uses PCAP, you can readily analyse
capture files using tools on other platforms (e.g. Ethereal, NetMon, tcpdump
on any platform, etc). I use and recommend.

Matt.