From 5f667694d3bbd57f13c26d3588d5671dfd30d09a Mon Sep 17 00:00:00 2001 From: Michael Mann Date: Thu, 21 Sep 2017 23:20:03 -0400 Subject: Add Flow Graph functionality to TShark Add flow graph functionality to tshark through -z option. Output is same as ASCII format saved from GUI. Change-Id: Iee0bfea7215858e6488b4728581be28287e9ea1a Reviewed-on: https://code.wireshark.org/review/23652 Petri-Dish: Michael Mann Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman --- doc/tshark.pod | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'doc') diff --git a/doc/tshark.pod b/doc/tshark.pod index 185409468d..67c538544e 100644 --- a/doc/tshark.pod +++ b/doc/tshark.pod @@ -1109,6 +1109,26 @@ on those calls that match that filter. Example: B<-z "expert,note,tcp"> will only collect expert items for frames that include the tcp protocol, with a severity of note or higher. +=item B<-z> flow,I,I,[I] + +Displays the flow of data between two nodes. Output is the same as ASCII format +saved from GUI. + +I specifies the flow name. It can be one of: + + any All frames + icmp ICMP + icmpv6 ICMPv6 + lbm_uim UIM + tcp TCP + +I specifies the address type. It can be one of: + + standard Any address + network Network address + +Example: B<-z flow,tcp,network> will show data flow for all TCP frames + =item B<-z> follow,I,I,I[I<,range>] Displays the contents of a TCP or UDP stream between two nodes. The data -- cgit v1.2.3