At 04:59 PM 4/4/2002 -0800, you wrote:
>On Thu, Apr 04, 2002 at 06:41:29PM -0600, George Sanderson wrote:
What about suggestion number 1.
1) Place a one line header at the beginning of the print output that
provides the program name, version, output format, and the date time of the
capture.
This could be used to differentiate future changes in the output format
and provide a time reference if the time output only is in seconds.
>> 2) Add a column for the packet size.
>>
>> This would enable utilization (bytes/seconds) to be calculated.
>
>The summary output format is not fixed; it's specified by an item in the
>configuration file.
>
This should probably be enabled by default, since it is one of the critical
values that is needed to calculate packet statistics. If it was available
by default then utilization could normally be calculated by most (default)
summary text output files. If it is not available by default, the
likelihood of being able to calculate utilization from a summary text file
output is remote.
>> 3) Always include the source and destination layer 3 socket addresses,
>> if they are available.
>
>If you meant "port numbers", those are layer 4 (tranport layer), not
>layer 3 (network layer).
Yes, of course layer 4, is what I meant. Sorry about the confusion.
> Those can also be added as columns;
>
This is good, but again, these should always be provided as numbers by
default in addition to any resolved application port numbers provided.
This way, reasonable statistical data can be calculated from a default
summary text file.
============
BTW
Is there an available application or scripts which can take a binary
capture file as input and generate a custom summary text file output?
+================================+
| George Sanderson <george@xxxxxxxxxxx>
| http://www.xorgate.com
+================================+