← Older revision

Revision as of 14:21, 20 May 2013

(One intermediate revision by one user not shown)

Line 10:

'''tcpflow''' is a program that captures data transmitted as part of TCP connections (flows), and stores the data in a way that is convenient for protocol analysis and debugging. Each TCP flow is stored in its own file. Thus, the typical TCP flow will be stored in two files, one for each direction. tcpflow can also process stored ‘tcpdump’ packet flows.

−

tcpflow is similar to ‘tcpdump’, in that both process packets from the wire or from a stored file. ~~But it’s different~~ in that it reconstructs ~~the actual data streams~~ and ~~stores each flow~~ in ~~a separate file for later analysis~~.

+

tcpflow is similar to ‘tcpdump’, in that both process packets from the wire or from a stored file. It's also similar to WireShark, in that both allow analysis of network traffic. But unlike either tcpdump or WireShark, tcpflow reconstructs thousands (or millions) of TCP connections at a time and saves the results in ordinary files, making it easy to analyze the data with conventional tools.

tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery.

+

== Overview ==

+

tcpflow stores all captured data in files that have names of the form

+

: 128.129.130.131.02345-010.011.012.013.45103

+

where the contents of the above file would be data transmitted from host ''128.129.131.131'' port ''2345'', to host ''10.11.12.13'' port ''45103''.

+

Specify the '''-Fk''' , '''-Fm'' or '''-Fg''' options if you are likely to have more than 1000 connections; this will cause tcpflow to create subdirectories automatically. You can also use other options to create directors for each host or port.

+

Specify the '''-e netviz''' option to enable the network visualization layer, and make a pretty picture like this:

+

[[Image:Tcpflow14-demo.png]]

+

== Limitations ==

+

* tcpflow does not understand IP fragments;

+

* tcpflow does not understand 802.11 headers.

+

== History ==

Jeremy Elson developed the first version of tcpflow in 1999 but stopped maintaining it in 2003. In 2006 Simson Garfinkel took over maintenance of the program and added:

Line 25:

Line 43:

tcpflow is based on the LBL Packet Capture Library (available from LBL) and therefore supports the same rich filtering expressions that programs like ‘tcpdump’ support. It should compile under most popular versions of UNIX; see the INSTALL file for details.

−

~~tcpflow stores all captured data in files that have names of the form:~~

−

~~128.129.130.131.02345-010.011.012.013.45103[VLAN]~~

−

~~where the contents of the above file would be data transmitted from host 128.129.131.131 port 2345, to host 10.11.12.13 port 45103. VLAN information, if provided is stored in brackets.~~

−

~~== Overview ==~~

−

~~tcpflow stores all captured data in files that have names of the form~~

−

~~: 128.129.130.131.02345-010.011.012.013.45103~~

−

~~where the contents of the above file would be data transmitted from host ''128.129.131.131'' port ''2345'', to host ''10.11.12.13'' port ''45103''.~~

−

~~== Limitations ==~~

−

* tcpflow does not understand IP fragments;

−

* tcpflow does not understand 802.11 headers.

== Distributions==

← Older revision		Revision as of 15:26, 24 May 2013
Line 15:		Line 15:

	* [http://www.brendangregg.com/chaosreader.html Chaosreader author's website]		* [http://www.brendangregg.com/chaosreader.html Chaosreader author's website]
		+	* [http://www.informationelle-selbstbestimmung-im-internet.de/chaosreader.html Enhanced, non-official version of Chaosreader (with diffs)]

	[[Category:Network Forensics]]		[[Category:Network Forensics]]

@@ Line 10: / Line 10: @@
 '''tcpflow''' is a program that captures data transmitted as part of TCP connections (flows), and stores the data in a way that is convenient for protocol analysis and debugging. Each TCP flow is stored in its own file. Thus, the typical TCP flow will be stored in two files, one for each direction. tcpflow can also process stored ‘tcpdump’ packet flows.
-tcpflow is similar to ‘tcpdump’, in that both process packets from the wire or from a stored file. But it’s different in that it reconstructs the actual data streams and stores each flow in a separate file for later analysis.
+tcpflow is similar to ‘tcpdump’, in that both process packets from the wire or from a stored file. It's also similar to WireShark, in that both allow analysis of network traffic. But unlike either tcpdump or WireShark, tcpflow reconstructs thousands (or millions) of TCP connections at a time and saves the results in ordinary files, making it easy to analyze the data with conventional tools.
 tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery.
 Jeremy Elson developed the first version of tcpflow in 1999 but stopped maintaining it in 2003. In 2006 Simson Garfinkel took over maintenance of the program and added:
@@ Line 25: / Line 43: @@
 tcpflow is based on the LBL Packet Capture Library (available from LBL) and therefore supports the same rich filtering expressions that programs like ‘tcpdump’ support. It should compile under most popular versions of UNIX; see the INSTALL file for details.
 == Distributions==

Forensics Wiki - Changes related to "Category:Network Forensics" [en]

Chaosreader

Tcpflow