This is needed for inter-operability with other systems, as 3.7.0 and
3.8.0 don't talk together.
Also, 3.8.0 fixes some important bugs, and it compresses bitmaps, which
means it can be used in various situations where it was completely useless
before.
-
tcpflow is a program that captures data transmitted as part of TCP
connections (flows), and stores it in a way that is convenient for
protocol analysis or debugging. A program like 'tcpdump' only shows a
summary of packets seen on the wire, but usually doesn't store the
data that's actually being transmitted. In contrast, tcpflow
reconstructs the actual data streams and stores each flow in a
separate file for later analysis.
tcpflow understands sequence numbers and will correctly reconstruct
data streams regardless of retransmissions or out-of-order delivery.
However, it currently does not understand IP fragments; flows
containing IP fragments will not be recorded properly.
Note: this port includes a small patch that adds the capability of
reading the packets from a tcpdump(1) capture file, using
a new option (-r).
-
tcptrace is a TCP dump file analysis tool written by Shawn Ostermann
at Ohio University. It is NOT a packet capture program. It reads
output dump files in the formats of several popular packet capturing
programs: tcpdump, snoop, etherpeek, and netm
For each connection, it keeps track of elapsed time, bytes/segments
sent and received, retransmissions, round trip times, window
advertisements, throughput, etc. Its output format ranges from
Simple to Long to Very Detailed.
someone is expecting substitution here.
tar: Unable to access bin/%%DISTNAME%% <No such file or directory>
tar: Unable to access lib/%%DISTNAME%%-lib/CHANGES <No such file or directory>
tar: Unable to access lib/%%DISTNAME%%-lib/README <No such file or directory>
tar: Unable to access lib/%%DISTNAME%%-lib/alias.tf <No such file or directory>
