This file is indexed.

/usr/share/wireshark/tshark.html is in libwireshark-data 2.0.2+ga16e22e-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

   1
   2
   3
   4
   5
   6
   7
   8
   9
  10
  11
  12
  13
  14
  15
  16
  17
  18
  19
  20
  21
  22
  23
  24
  25
  26
  27
  28
  29
  30
  31
  32
  33
  34
  35
  36
  37
  38
  39
  40
  41
  42
  43
  44
  45
  46
  47
  48
  49
  50
  51
  52
  53
  54
  55
  56
  57
  58
  59
  60
  61
  62
  63
  64
  65
  66
  67
  68
  69
  70
  71
  72
  73
  74
  75
  76
  77
  78
  79
  80
  81
  82
  83
  84
  85
  86
  87
  88
  89
  90
  91
  92
  93
  94
  95
  96
  97
  98
  99
 100
 101
 102
 103
 104
 105
 106
 107
 108
 109
 110
 111
 112
 113
 114
 115
 116
 117
 118
 119
 120
 121
 122
 123
 124
 125
 126
 127
 128
 129
 130
 131
 132
 133
 134
 135
 136
 137
 138
 139
 140
 141
 142
 143
 144
 145
 146
 147
 148
 149
 150
 151
 152
 153
 154
 155
 156
 157
 158
 159
 160
 161
 162
 163
 164
 165
 166
 167
 168
 169
 170
 171
 172
 173
 174
 175
 176
 177
 178
 179
 180
 181
 182
 183
 184
 185
 186
 187
 188
 189
 190
 191
 192
 193
 194
 195
 196
 197
 198
 199
 200
 201
 202
 203
 204
 205
 206
 207
 208
 209
 210
 211
 212
 213
 214
 215
 216
 217
 218
 219
 220
 221
 222
 223
 224
 225
 226
 227
 228
 229
 230
 231
 232
 233
 234
 235
 236
 237
 238
 239
 240
 241
 242
 243
 244
 245
 246
 247
 248
 249
 250
 251
 252
 253
 254
 255
 256
 257
 258
 259
 260
 261
 262
 263
 264
 265
 266
 267
 268
 269
 270
 271
 272
 273
 274
 275
 276
 277
 278
 279
 280
 281
 282
 283
 284
 285
 286
 287
 288
 289
 290
 291
 292
 293
 294
 295
 296
 297
 298
 299
 300
 301
 302
 303
 304
 305
 306
 307
 308
 309
 310
 311
 312
 313
 314
 315
 316
 317
 318
 319
 320
 321
 322
 323
 324
 325
 326
 327
 328
 329
 330
 331
 332
 333
 334
 335
 336
 337
 338
 339
 340
 341
 342
 343
 344
 345
 346
 347
 348
 349
 350
 351
 352
 353
 354
 355
 356
 357
 358
 359
 360
 361
 362
 363
 364
 365
 366
 367
 368
 369
 370
 371
 372
 373
 374
 375
 376
 377
 378
 379
 380
 381
 382
 383
 384
 385
 386
 387
 388
 389
 390
 391
 392
 393
 394
 395
 396
 397
 398
 399
 400
 401
 402
 403
 404
 405
 406
 407
 408
 409
 410
 411
 412
 413
 414
 415
 416
 417
 418
 419
 420
 421
 422
 423
 424
 425
 426
 427
 428
 429
 430
 431
 432
 433
 434
 435
 436
 437
 438
 439
 440
 441
 442
 443
 444
 445
 446
 447
 448
 449
 450
 451
 452
 453
 454
 455
 456
 457
 458
 459
 460
 461
 462
 463
 464
 465
 466
 467
 468
 469
 470
 471
 472
 473
 474
 475
 476
 477
 478
 479
 480
 481
 482
 483
 484
 485
 486
 487
 488
 489
 490
 491
 492
 493
 494
 495
 496
 497
 498
 499
 500
 501
 502
 503
 504
 505
 506
 507
 508
 509
 510
 511
 512
 513
 514
 515
 516
 517
 518
 519
 520
 521
 522
 523
 524
 525
 526
 527
 528
 529
 530
 531
 532
 533
 534
 535
 536
 537
 538
 539
 540
 541
 542
 543
 544
 545
 546
 547
 548
 549
 550
 551
 552
 553
 554
 555
 556
 557
 558
 559
 560
 561
 562
 563
 564
 565
 566
 567
 568
 569
 570
 571
 572
 573
 574
 575
 576
 577
 578
 579
 580
 581
 582
 583
 584
 585
 586
 587
 588
 589
 590
 591
 592
 593
 594
 595
 596
 597
 598
 599
 600
 601
 602
 603
 604
 605
 606
 607
 608
 609
 610
 611
 612
 613
 614
 615
 616
 617
 618
 619
 620
 621
 622
 623
 624
 625
 626
 627
 628
 629
 630
 631
 632
 633
 634
 635
 636
 637
 638
 639
 640
 641
 642
 643
 644
 645
 646
 647
 648
 649
 650
 651
 652
 653
 654
 655
 656
 657
 658
 659
 660
 661
 662
 663
 664
 665
 666
 667
 668
 669
 670
 671
 672
 673
 674
 675
 676
 677
 678
 679
 680
 681
 682
 683
 684
 685
 686
 687
 688
 689
 690
 691
 692
 693
 694
 695
 696
 697
 698
 699
 700
 701
 702
 703
 704
 705
 706
 707
 708
 709
 710
 711
 712
 713
 714
 715
 716
 717
 718
 719
 720
 721
 722
 723
 724
 725
 726
 727
 728
 729
 730
 731
 732
 733
 734
 735
 736
 737
 738
 739
 740
 741
 742
 743
 744
 745
 746
 747
 748
 749
 750
 751
 752
 753
 754
 755
 756
 757
 758
 759
 760
 761
 762
 763
 764
 765
 766
 767
 768
 769
 770
 771
 772
 773
 774
 775
 776
 777
 778
 779
 780
 781
 782
 783
 784
 785
 786
 787
 788
 789
 790
 791
 792
 793
 794
 795
 796
 797
 798
 799
 800
 801
 802
 803
 804
 805
 806
 807
 808
 809
 810
 811
 812
 813
 814
 815
 816
 817
 818
 819
 820
 821
 822
 823
 824
 825
 826
 827
 828
 829
 830
 831
 832
 833
 834
 835
 836
 837
 838
 839
 840
 841
 842
 843
 844
 845
 846
 847
 848
 849
 850
 851
 852
 853
 854
 855
 856
 857
 858
 859
 860
 861
 862
 863
 864
 865
 866
 867
 868
 869
 870
 871
 872
 873
 874
 875
 876
 877
 878
 879
 880
 881
 882
 883
 884
 885
 886
 887
 888
 889
 890
 891
 892
 893
 894
 895
 896
 897
 898
 899
 900
 901
 902
 903
 904
 905
 906
 907
 908
 909
 910
 911
 912
 913
 914
 915
 916
 917
 918
 919
 920
 921
 922
 923
 924
 925
 926
 927
 928
 929
 930
 931
 932
 933
 934
 935
 936
 937
 938
 939
 940
 941
 942
 943
 944
 945
 946
 947
 948
 949
 950
 951
 952
 953
 954
 955
 956
 957
 958
 959
 960
 961
 962
 963
 964
 965
 966
 967
 968
 969
 970
 971
 972
 973
 974
 975
 976
 977
 978
 979
 980
 981
 982
 983
 984
 985
 986
 987
 988
 989
 990
 991
 992
 993
 994
 995
 996
 997
 998
 999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>tshark\ -\ The\ Wireshark\ Network\ Analyzer\ 2.0.2</title>
<link rel="stylesheet" href="ws.css" type="text/css" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body>



<h1 id="NAME">NAME</h1>

<p>tshark - Dump and analyze network traffic</p>

<h1 id="SYNOPSIS">SYNOPSIS</h1>

<p><b>tshark</b> <span style="white-space: nowrap;">[ <b>-2</b> ]</span> <span style="white-space: nowrap;">[ <b>-a</b> &lt;capture autostop condition&gt; ] ...</span> <span style="white-space: nowrap;">[ <b>-b</b> &lt;capture ring buffer option&gt;] ...</span> <span style="white-space: nowrap;">[ <b>-B</b> &lt;capture buffer size&gt; ] </span> <span style="white-space: nowrap;">[ <b>-c</b> &lt;capture packet count&gt; ]</span> <span style="white-space: nowrap;">[ <b>-C</b> &lt;configuration profile&gt; ]</span> <span style="white-space: nowrap;">[ <b>-d</b> &lt;layer type&gt;==&lt;selector&gt;,&lt;decode-as protocol&gt; ]</span> <span style="white-space: nowrap;">[ <b>-D</b> ]</span> <span style="white-space: nowrap;">[ <b>-e</b> &lt;field&gt; ]</span> <span style="white-space: nowrap;">[ <b>-E</b> &lt;field print option&gt; ]</span> <span style="white-space: nowrap;">[ <b>-f</b> &lt;capture filter&gt; ]</span> <span style="white-space: nowrap;">[ <b>-F</b> &lt;file format&gt; ]</span> <span style="white-space: nowrap;">[ <b>-g</b> ]</span> <span style="white-space: nowrap;">[ <b>-h</b> ]</span> <span style="white-space: nowrap;">[ <b>-H</b> &lt;input hosts file&gt; ]</span> <span style="white-space: nowrap;">[ <b>-i</b> &lt;capture interface&gt;|- ]</span> <span style="white-space: nowrap;">[ <b>-I</b> ]</span> <span style="white-space: nowrap;">[ <b>-K</b> &lt;keytab&gt; ]</span> <span style="white-space: nowrap;">[ <b>-l</b> ]</span> <span style="white-space: nowrap;">[ <b>-L</b> ]</span> <span style="white-space: nowrap;">[ <b>-n</b> ]</span> <span style="white-space: nowrap;">[ <b>-N</b> &lt;name resolving flags&gt; ]</span> <span style="white-space: nowrap;">[ <b>-o</b> &lt;preference setting&gt; ] ...</span> <span style="white-space: nowrap;">[ <b>-O</b> &lt;protocols&gt; ]</span> <span style="white-space: nowrap;">[ <b>-p</b> ]</span> <span style="white-space: nowrap;">[ <b>-P</b> ]</span> <span style="white-space: nowrap;">[ <b>-q</b> ]</span> <span style="white-space: nowrap;">[ <b>-Q</b> ]</span> <span style="white-space: nowrap;">[ <b>-r</b> &lt;infile&gt; ]</span> <span style="white-space: nowrap;">[ <b>-R</b> &lt;Read filter&gt; ]</span> <span style="white-space: nowrap;">[ <b>-s</b> &lt;capture snaplen&gt; ]</span> <span style="white-space: nowrap;">[ <b>-S</b> &lt;separator&gt; ]</span> <span style="white-space: nowrap;">[ <b>-t</b> a|ad|adoy|d|dd|e|r|u|ud|udoy ]</span> <span style="white-space: nowrap;">[ <b>-T</b> fields|pdml|ps|psml|text ]</span> <span style="white-space: nowrap;">[ <b>-u</b> &lt;seconds type&gt;]</span> <span style="white-space: nowrap;">[ <b>-v</b> ]</span> <span style="white-space: nowrap;">[ <b>-V</b> ]</span> <span style="white-space: nowrap;">[ <b>-w</b> &lt;outfile&gt;|- ]</span> <span style="white-space: nowrap;">[ <b>-W</b> &lt;file format option&gt;]</span> <span style="white-space: nowrap;">[ <b>-x</b> ]</span> <span style="white-space: nowrap;">[ <b>-X</b> &lt;eXtension option&gt;]</span> <span style="white-space: nowrap;">[ <b>-y</b> &lt;capture link type&gt; ]</span> <span style="white-space: nowrap;">[ <b>-Y</b> &lt;displaY filter&gt; ]</span> <span style="white-space: nowrap;">[ <b>-z</b> &lt;statistics&gt; ]</span> <span style="white-space: nowrap;">[ <b>--capture-comment</b> &lt;comment&gt; ]</span> <span style="white-space: nowrap;">[ &lt;capture filter&gt; ]</span></p>

<p><b>tshark</b> <b>-G</b> [ &lt;report type&gt; ]</p>

<h1 id="DESCRIPTION">DESCRIPTION</h1>

<p><b>TShark</b> is a network protocol analyzer. It lets you capture packet data from a live network, or read packets from a previously saved capture file, either printing a decoded form of those packets to the standard output or writing the packets to a file. <b>TShark</b>&#39;s native capture file format is <b>pcap</b> format, which is also the format used by <b>tcpdump</b> and various other tools.</p>

<p>Without any options set, <b>TShark</b> will work much like <b>tcpdump</b>. It will use the pcap library to capture traffic from the first available network interface and displays a summary line on stdout for each received packet.</p>

<p><b>TShark</b> is able to detect, read and write the same capture files that are supported by <b>Wireshark</b>. The input file doesn&#39;t need a specific filename extension; the file format and an optional gzip compression will be automatically detected. Near the beginning of the DESCRIPTION section of wireshark(1) or <a href="https://www.wireshark.org/docs/man-pages/wireshark.html">https://www.wireshark.org/docs/man-pages/wireshark.html</a> is a detailed description of the way <b>Wireshark</b> handles this, which is the same way <b>Tshark</b> handles this.</p>

<p>Compressed file support uses (and therefore requires) the zlib library. If the zlib library is not present, <b>TShark</b> will compile, but will be unable to read compressed files.</p>

<p>If the <b>-w</b> option is not specified, <b>TShark</b> writes to the standard output the text of a decoded form of the packets it captures or reads. If the <b>-w</b> option is specified, <b>TShark</b> writes to the file specified by that option the raw data of the packets, along with the packets&#39; time stamps.</p>

<p>When writing a decoded form of packets, <b>TShark</b> writes, by default, a summary line containing the fields specified by the preferences file (which are also the fields displayed in the packet list pane in <b>Wireshark</b>), although if it&#39;s writing packets as it captures them, rather than writing packets from a saved capture file, it won&#39;t show the &quot;frame number&quot; field. If the <b>-V</b> option is specified, it writes instead a view of the details of the packet, showing all the fields of all protocols in the packet. If the <b>-O</b> option is specified, it will only show the full protocols specified. Use the output of &quot;<b>tshark -G protocols</b>&quot; to find the abbreviations of the protocols you can specify.</p>

<p>If you want to write the decoded form of packets to a file, run <b>TShark</b> without the <b>-w</b> option, and redirect its standard output to the file (do <i>not</i> use the <b>-w</b> option).</p>

<p>When writing packets to a file, <b>TShark</b>, by default, writes the file in <b>pcap</b> format, and writes all of the packets it sees to the output file. The <b>-F</b> option can be used to specify the format in which to write the file. This list of available file formats is displayed by the <b>-F</b> flag without a value. However, you can&#39;t specify a file format for a live capture.</p>

<p>Read filters in <b>TShark</b>, which allow you to select which packets are to be decoded or written to a file, are very powerful; more fields are filterable in <b>TShark</b> than in other protocol analyzers, and the syntax you can use to create your filters is richer. As <b>TShark</b> progresses, expect more and more protocol fields to be allowed in read filters.</p>

<p>Packet capturing is performed with the pcap library. The capture filter syntax follows the rules of the pcap library. This syntax is different from the read filter syntax. A read filter can also be specified when capturing, and only packets that pass the read filter will be displayed or saved to the output file; note, however, that capture filters are much more efficient than read filters, and it may be more difficult for <b>TShark</b> to keep up with a busy network if a read filter is specified for a live capture.</p>

<p>A capture or read filter can either be specified with the <b>-f</b> or <b>-R</b> option, respectively, in which case the entire filter expression must be specified as a single argument (which means that if it contains spaces, it must be quoted), or can be specified with command-line arguments after the option arguments, in which case all the arguments after the filter arguments are treated as a filter expression. Capture filters are supported only when doing a live capture; read filters are supported when doing a live capture and when reading a capture file, but require TShark to do more work when filtering, so you might be more likely to lose packets under heavy load if you&#39;re using a read filter. If the filter is specified with command-line arguments after the option arguments, it&#39;s a capture filter if a capture is being done (i.e., if no <b>-r</b> option was specified) and a read filter if a capture file is being read (i.e., if a <b>-r</b> option was specified).</p>

<p>The <b>-G</b> option is a special mode that simply causes <b>Tshark</b> to dump one of several types of internal glossaries and then exit.</p>

<h1 id="OPTIONS">OPTIONS</h1>

<dl>

<dt id="pod-2">-2</dt>
<dd>

<p>Perform a two-pass analysis. This causes tshark to buffer output until the entire first pass is done, but allows it to fill in fields that require future knowledge, such as &#39;response in frame #&#39; fields. Also permits reassembly frame dependencies to be calculated correctly.</p>

</dd>
<dt id="a-capture-autostop-condition">-a &lt;capture autostop condition&gt;</dt>
<dd>

<p>Specify a criterion that specifies when <b>TShark</b> is to stop writing to a capture file. The criterion is of the form <i>test</i><b>:</b><i>value</i>, where <i>test</i> is one of:</p>

<p><b>duration</b>:<i>value</i> Stop writing to a capture file after <i>value</i> seconds have elapsed.</p>

<p><b>filesize</b>:<i>value</i> Stop writing to a capture file after it reaches a size of <i>value</i> kB. If this option is used together with the -b option, <b>TShark</b> will stop writing to the current capture file and switch to the next one if filesize is reached. When reading a capture file, <b>TShark</b> will stop reading the file after the number of bytes read exceeds this number (the complete packet will be read, so more bytes than this number may be read). Note that the filesize is limited to a maximum value of 2 GiB.</p>

<p><b>files</b>:<i>value</i> Stop writing to capture files after <i>value</i> number of files were written.</p>

</dd>
<dt id="b-capture-ring-buffer-option">-b &lt;capture ring buffer option&gt;</dt>
<dd>

<p>Cause <b>TShark</b> to run in &quot;multiple files&quot; mode. In &quot;multiple files&quot; mode, <b>TShark</b> will write to several capture files. When the first capture file fills up, <b>TShark</b> will switch writing to the next file and so on.</p>

<p>The created filenames are based on the filename given with the <b>-w</b> option, the number of the file and on the creation date and time, e.g. outfile_00001_20050604120117.pcap, outfile_00002_20050604120523.pcap, ...</p>

<p>With the <i>files</i> option it&#39;s also possible to form a &quot;ring buffer&quot;. This will fill up new files until the number of files specified, at which point <b>TShark</b> will discard the data in the first file and start writing to that file and so on. If the <i>files</i> option is not set, new files filled up until one of the capture stop conditions match (or until the disk is full).</p>

<p>The criterion is of the form <i>key</i><b>:</b><i>value</i>, where <i>key</i> is one of:</p>

<p><b>duration</b>:<i>value</i> switch to the next file after <i>value</i> seconds have elapsed, even if the current file is not completely filled up.</p>

<p><b>filesize</b>:<i>value</i> switch to the next file after it reaches a size of <i>value</i> kB. Note that the filesize is limited to a maximum value of 2 GiB.</p>

<p><b>files</b>:<i>value</i> begin again with the first file after <i>value</i> number of files were written (form a ring buffer). This value must be less than 100000. Caution should be used when using large numbers of files: some filesystems do not handle many files in a single directory well. The <b>files</b> criterion requires either <b>duration</b> or <b>filesize</b> to be specified to control when to go to the next file. It should be noted that each <b>-b</b> parameter takes exactly one criterion; to specify two criterion, each must be preceded by the <b>-b</b> option.</p>

<p>Example: <b>-b filesize:1000 -b files:5</b> results in a ring buffer of five files of size one megabyte each.</p>

</dd>
<dt id="B-capture-buffer-size">-B &lt;capture buffer size&gt;</dt>
<dd>

<p>Set capture buffer size (in MiB, default is 2 MiB). This is used by the capture driver to buffer packet data until that data can be written to disk. If you encounter packet drops while capturing, try to increase this size. Note that, while <b>Tshark</b> attempts to set the buffer size to 2 MiB by default, and can be told to set it to a larger value, the system or interface on which you&#39;re capturing might silently limit the capture buffer size to a lower value or raise it to a higher value.</p>

<p>This is available on UNIX systems with libpcap 1.0.0 or later and on Windows. It is not available on UNIX systems with earlier versions of libpcap.</p>

<p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default capture buffer size. If used after an <b>-i</b> option, it sets the capture buffer size for the interface specified by the last <b>-i</b> option occurring before this option. If the capture buffer size is not set specifically, the default capture buffer size is used instead.</p>

</dd>
<dt id="c-capture-packet-count">-c &lt;capture packet count&gt;</dt>
<dd>

<p>Set the maximum number of packets to read when capturing live data. If reading a capture file, set the maximum number of packets to read.</p>

</dd>
<dt id="C-configuration-profile">-C &lt;configuration profile&gt;</dt>
<dd>

<p>Run with the given configuration profile.</p>

</dd>
<dt id="d-layer-type-selector-decode-as-protocol">-d &lt;layer type&gt;==&lt;selector&gt;,&lt;decode-as protocol&gt;</dt>
<dd>

<p>Like Wireshark&#39;s <b>Decode As...</b> feature, this lets you specify how a layer type should be dissected. If the layer type in question (for example, <b>tcp.port</b> or <b>udp.port</b> for a TCP or UDP port number) has the specified selector value, packets should be dissected as the specified protocol.</p>

<p>Example: <b>-d tcp.port==8888,http</b> will decode any traffic running over TCP port 8888 as HTTP.</p>

<p>Example: <b>-d tcp.port==8888:3,http</b> will decode any traffic running over TCP ports 8888, 8889 or 8890 as HTTP.</p>

<p>Example: <b>-d tcp.port==8888-8890,http</b> will decode any traffic running over TCP ports 8888, 8889 or 8890 as HTTP.</p>

<p>Using an invalid selector or protocol will print out a list of valid selectors and protocol names, respectively.</p>

<p>Example: <b>-d .</b> is a quick way to get a list of valid selectors.</p>

<p>Example: <b>-d ethertype==0x0800.</b> is a quick way to get a list of protocols that can be selected with an ethertype.</p>

</dd>
<dt id="D">-D</dt>
<dd>

<p>Print a list of the interfaces on which <b>TShark</b> can capture, and exit. For each network interface, a number and an interface name, possibly followed by a text description of the interface, is printed. The interface name or the number can be supplied to the <b>-i</b> option to specify an interface on which to capture.</p>

<p>This can be useful on systems that don&#39;t have a command to list them (e.g., Windows systems, or UNIX systems lacking <b>ifconfig -a</b>); the number can be useful on Windows 2000 and later systems, where the interface name is a somewhat complex string.</p>

<p>Note that &quot;can capture&quot; means that <b>TShark</b> was able to open that device to do a live capture. Depending on your system you may need to run tshark from an account with special privileges (for example, as root) to be able to capture network traffic. If <b>TShark -D</b> is not run from such an account, it will not list any interfaces.</p>

</dd>
<dt id="e-field">-e &lt;field&gt;</dt>
<dd>

<p>Add a field to the list of fields to display if <b>-T fields</b> is selected. This option can be used multiple times on the command line. At least one field must be provided if the <b>-T fields</b> option is selected. Column names may be used prefixed with &quot;_ws.col.&quot;</p>

<p>Example: <b>-e frame.number -e ip.addr -e udp -e _ws.col.Info</b></p>

<p>Giving a protocol rather than a single field will print multiple items of data about the protocol as a single field. Fields are separated by tab characters by default. <b>-E</b> controls the format of the printed fields.</p>

</dd>
<dt id="E-field-print-option">-E &lt;field print option&gt;</dt>
<dd>

<p>Set an option controlling the printing of fields when <b>-T fields</b> is selected.</p>

<p>Options are:</p>

<p><b>header=y|n</b> If <b>y</b>, print a list of the field names given using <b>-e</b> as the first line of the output; the field name will be separated using the same character as the field values. Defaults to <b>n</b>.</p>

<p><b>separator=/t|/s|</b>&lt;character&gt; Set the separator character to use for fields. If <b>/t</b> tab will be used (this is the default), if <b>/s</b>, a single space will be used. Otherwise any character that can be accepted by the command line as part of the option may be used.</p>

<p><b>occurrence=f|l|a</b> Select which occurrence to use for fields that have multiple occurrences. If <b>f</b> the first occurrence will be used, if <b>l</b> the last occurrence will be used and if <b>a</b> all occurrences will be used (this is the default).</p>

<p><b>aggregator=,|/s|</b>&lt;character&gt; Set the aggregator character to use for fields that have multiple occurrences. If <b>,</b> a comma will be used (this is the default), if <b>/s</b>, a single space will be used. Otherwise any character that can be accepted by the command line as part of the option may be used.</p>

<p><b>quote=d|s|n</b> Set the quote character to use to surround fields. <b>d</b> uses double-quotes, <b>s</b> single-quotes, <b>n</b> no quotes (the default).</p>

</dd>
<dt id="f-capture-filter">-f &lt;capture filter&gt;</dt>
<dd>

<p>Set the capture filter expression.</p>

<p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default capture filter expression. If used after an <b>-i</b> option, it sets the capture filter expression for the interface specified by the last <b>-i</b> option occurring before this option. If the capture filter expression is not set specifically, the default capture filter expression is used if provided.</p>

</dd>
<dt id="F-file-format">-F &lt;file format&gt;</dt>
<dd>

<p>Set the file format of the output capture file written using the <b>-w</b> option. The output written with the <b>-w</b> option is raw packet data, not text, so there is no <b>-F</b> option to request text output. The option <b>-F</b> without a value will list the available formats.</p>

</dd>
<dt id="g">-g</dt>
<dd>

<p>This option causes the output file(s) to be created with group-read permission (meaning that the output file(s) can be read by other members of the calling user&#39;s group).</p>

</dd>
<dt id="G-report-type">-G [ &lt;report type&gt; ]</dt>
<dd>

<p>The <b>-G</b> option will cause <b>Tshark</b> to dump one of several types of glossaries and then exit. If no specific glossary type is specified, then the <b>fields</b> report will be generated by default.</p>

<p>The available report types include:</p>

<p><b>column-formats</b> Dumps the column formats understood by tshark. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = format string (e.g. &quot;%rD&quot;)
 * Field 2 = text description of format string (e.g. &quot;Dest port (resolved)&quot;)</code></pre>

<p><b>currentprefs</b> Dumps a copy of the current preferences file to stdout.</p>

<p><b>decodes</b> Dumps the &quot;layer type&quot;/&quot;decode as&quot; associations to stdout. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = layer type, e.g. &quot;tcp.port&quot;
 * Field 2 = selector in decimal
 * Field 3 = &quot;decode as&quot; name, e.g. &quot;http&quot;</code></pre>

<p><b>defaultprefs</b> Dumps a default preferences file to stdout.</p>

<p><b>dissector-tables</b> Dumps a list of dissector tables to stdout. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = dissector table name, e.g. &quot;tcp.port&quot;
 * Field 2 = name used for the dissector table in the GUI
 * Field 3 = type (textual representation of the ftenum type)
 * Field 4 = base for display (for integer types)</code></pre>

<p><b>fieldcount</b> Dumps the number of header fields to stdout.</p>

<p><b>fields</b> Dumps the contents of the registration database to stdout. An independent program can take this output and format it into nice tables or HTML or whatever. There is one record per line. Each record is either a protocol or a header field, differentiated by the first field. The fields are tab-delimited.</p>

<pre><code> * Protocols
 * ---------
 * Field 1 = &#39;P&#39;
 * Field 2 = descriptive protocol name
 * Field 3 = protocol abbreviation
 *
 * Header Fields
 * -------------
 * Field 1 = &#39;F&#39;
 * Field 2 = descriptive field name
 * Field 3 = field abbreviation
 * Field 4 = type (textual representation of the ftenum type)
 * Field 5 = parent protocol abbreviation
 * Field 6 = base for display (for integer types); &quot;parent bitfield width&quot; for FT_BOOLEAN
 * Field 7 = bitmask: format: hex: 0x....
 * Field 8 = blurb describing field</code></pre>

<p><b>ftypes</b> Dumps the &quot;ftypes&quot; (fundamental types) understood by tshark. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = FTYPE (e.g &quot;FT_IPv6&quot;)
 * Field 2 = text description of type (e.g. &quot;IPv6 address&quot;)</code></pre>

<p><b>heuristic-decodes</b> Dumps the heuristic decodes currently installed. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = underlying dissector (e.g. &quot;tcp&quot;)
 * Field 2 = name of heuristic decoder (e.g. ucp&quot;)
 * Field 3 = heuristic enabled (e.g. &quot;T&quot; or &quot;F&quot;)</code></pre>

<p><b>plugins</b> Dumps the plugins currently installed. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = plugin library (e.g. &quot;gryphon.so&quot;)
 * Field 2 = plugin version (e.g. 0.0.4)
 * Field 3 = plugin type (e.g. &quot;dissector&quot; or &quot;tap&quot;)
 * Field 4 = full path to plugin file</code></pre>

<p><b>protocols</b> Dumps the protocols in the registration database to stdout. An independent program can take this output and format it into nice tables or HTML or whatever. There is one record per line. The fields are tab-delimited.</p>

<pre><code> * Field 1 = protocol name
 * Field 2 = protocol short name
 * Field 3 = protocol filter name</code></pre>

<p><b>values</b> Dumps the value_strings, range_strings or true/false strings for fields that have them. There is one record per line. Fields are tab-delimited. There are three types of records: Value String, Range String and True/False String. The first field, &#39;V&#39;, &#39;R&#39; or &#39;T&#39;, indicates the type of record.</p>

<pre><code> * Value Strings
 * -------------
 * Field 1 = &#39;V&#39;
 * Field 2 = field abbreviation to which this value string corresponds
 * Field 3 = Integer value
 * Field 4 = String
 *
 * Range Strings
 * -------------
 * Field 1 = &#39;R&#39;
 * Field 2 = field abbreviation to which this range string corresponds
 * Field 3 = Integer value: lower bound
 * Field 4 = Integer value: upper bound
 * Field 5 = String
 *
 * True/False Strings
 * ------------------
 * Field 1 = &#39;T&#39;
 * Field 2 = field abbreviation to which this true/false string corresponds
 * Field 3 = True String
 * Field 4 = False String</code></pre>

</dd>
<dt id="h">-h</dt>
<dd>

<p>Print the version and options and exits.</p>

</dd>
<dt id="H-input-hosts-file">-H &lt;input hosts file&gt;</dt>
<dd>

<p>Read a list of entries from a &quot;hosts&quot; file, which will then be written to a capture file. Implies <b>-W n</b>. Can be called multiple times.</p>

<p>The &quot;hosts&quot; file format is documented at <a href="http://en.wikipedia.org/wiki/Hosts_(file)">http://en.wikipedia.org/wiki/Hosts_(file)</a>.</p>

</dd>
<dt id="i-capture-interface">-i &lt;capture interface&gt; | -</dt>
<dd>

<p>Set the name of the network interface or pipe to use for live packet capture.</p>

<p>Network interface names should match one of the names listed in &quot;<b>tshark -D</b>&quot; (described above); a number, as reported by &quot;<b>tshark -D</b>&quot;, can also be used. If you&#39;re using UNIX, &quot;<b>netstat -i</b>&quot; or &quot;<b>ifconfig -a</b>&quot; might also work to list interface names, although not all versions of UNIX support the <b>-a</b> option to <b>ifconfig</b>.</p>

<p>If no interface is specified, <b>TShark</b> searches the list of interfaces, choosing the first non-loopback interface if there are any non-loopback interfaces, and choosing the first loopback interface if there are no non-loopback interfaces. If there are no interfaces at all, <b>TShark</b> reports an error and doesn&#39;t start the capture.</p>

<p>Pipe names should be either the name of a FIFO (named pipe) or ``-&#39;&#39; to read data from the standard input. Data read from pipes must be in standard pcap format.</p>

<p>This option can occur multiple times. When capturing from multiple interfaces, the capture file will be saved in pcap-ng format.</p>

<p>Note: the Win32 version of <b>TShark</b> doesn&#39;t support capturing from pipes!</p>

</dd>
<dt id="I">-I</dt>
<dd>

<p>Put the interface in &quot;monitor mode&quot;; this is supported only on IEEE 802.11 Wi-Fi interfaces, and supported only on some operating systems.</p>

<p>Note that in monitor mode the adapter might disassociate from the network with which it&#39;s associated, so that you will not be able to use any wireless networks with that adapter. This could prevent accessing files on a network server, or resolving host names or network addresses, if you are capturing in monitor mode and are not connected to another network with another adapter.</p>

<p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it enables the monitor mode for all interfaces. If used after an <b>-i</b> option, it enables the monitor mode for the interface specified by the last <b>-i</b> option occurring before this option.</p>

</dd>
<dt id="K-keytab">-K &lt;keytab&gt;</dt>
<dd>

<p>Load kerberos crypto keys from the specified keytab file. This option can be used multiple times to load keys from several files.</p>

<p>Example: <b>-K krb5.keytab</b></p>

</dd>
<dt id="l">-l</dt>
<dd>

<p>Flush the standard output after the information for each packet is printed. (This is not, strictly speaking, line-buffered if <b>-V</b> was specified; however, it is the same as line-buffered if <b>-V</b> wasn&#39;t specified, as only one line is printed for each packet, and, as <b>-l</b> is normally used when piping a live capture to a program or script, so that output for a packet shows up as soon as the packet is seen and dissected, it should work just as well as true line-buffering. We do this as a workaround for a deficiency in the Microsoft Visual C++ C library.)</p>

<p>This may be useful when piping the output of <b>TShark</b> to another program, as it means that the program to which the output is piped will see the dissected data for a packet as soon as <b>TShark</b> sees the packet and generates that output, rather than seeing it only when the standard output buffer containing that data fills up.</p>

</dd>
<dt id="L">-L</dt>
<dd>

<p>List the data link types supported by the interface and exit. The reported link types can be used for the <b>-y</b> option.</p>

</dd>
<dt id="n">-n</dt>
<dd>

<p>Disable network object name resolution (such as hostname, TCP and UDP port names); the <b>-N</b> flag might override this one.</p>

</dd>
<dt id="N-name-resolving-flags">-N &lt;name resolving flags&gt;</dt>
<dd>

<p>Turn on name resolving only for particular types of addresses and port numbers, with name resolving for other types of addresses and port numbers turned off. This flag overrides <b>-n</b> if both <b>-N</b> and <b>-n</b> are present. If both <b>-N</b> and <b>-n</b> flags are not present, all name resolutions are turned on.</p>

<p>The argument is a string that may contain the letters:</p>

<p><b>C</b> to enable concurrent (asynchronous) DNS lookups</p>

<p><b>d</b> to enable resolution from captured DNS packets</p>

<p><b>m</b> to enable MAC address resolution</p>

<p><b>n</b> to enable network address resolution</p>

<p><b>N</b> to enable using external resolvers (e.g., DNS) for network address resolution</p>

<p><b>t</b> to enable transport-layer port number resolution</p>

</dd>
<dt id="o-preference:value">-o &lt;preference&gt;:&lt;value&gt;</dt>
<dd>

<p>Set a preference value, overriding the default value and any value read from a preference file. The argument to the option is a string of the form <i>prefname</i><b>:</b><i>value</i>, where <i>prefname</i> is the name of the preference (which is the same name that would appear in the preference file), and <i>value</i> is the value to which it should be set.</p>

</dd>
<dt id="O-protocols">-O &lt;protocols&gt;</dt>
<dd>

<p>Similar to the <b>-V</b> option, but causes <b>TShark</b> to only show a detailed view of the comma-separated list of <i>protocols</i> specified, rather than a detailed view of all protocols. Use the output of &quot;<b>tshark -G protocols</b>&quot; to find the abbreviations of the protocols you can specify.</p>

</dd>
<dt id="p">-p</dt>
<dd>

<p><i>Don&#39;t</i> put the interface into promiscuous mode. Note that the interface might be in promiscuous mode for some other reason; hence, <b>-p</b> cannot be used to ensure that the only traffic that is captured is traffic sent to or from the machine on which <b>TShark</b> is running, broadcast traffic, and multicast traffic to addresses received by that machine.</p>

<p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, no interface will be put into the promiscuous mode. If used after an <b>-i</b> option, the interface specified by the last <b>-i</b> option occurring before this option will not be put into the promiscuous mode.</p>

</dd>
<dt id="P">-P</dt>
<dd>

<p>Decode and display the packet summary, even if writing raw packet data using the <b>-w</b> option.</p>

</dd>
<dt id="q">-q</dt>
<dd>

<p>When capturing packets, don&#39;t display the continuous count of packets captured that is normally shown when saving a capture to a file; instead, just display, at the end of the capture, a count of packets captured. On systems that support the SIGINFO signal, such as various BSDs, you can cause the current count to be displayed by typing your &quot;status&quot; character (typically control-T, although it might be set to &quot;disabled&quot; by default on at least some BSDs, so you&#39;d have to explicitly set it to use it).</p>

<p>When reading a capture file, or when capturing and not saving to a file, don&#39;t print packet information; this is useful if you&#39;re using a <b>-z</b> option to calculate statistics and don&#39;t want the packet information printed, just the statistics.</p>

</dd>
<dt id="Q">-Q</dt>
<dd>

<p>When capturing packets, only display true errors. This outputs less than the <b>-q</b> option, so the interface name and total packet count and the end of a capture are not sent to stderr.</p>

</dd>
<dt id="r-infile">-r &lt;infile&gt;</dt>
<dd>

<p>Read packet data from <i>infile</i>, can be any supported capture file format (including gzipped files). It is possible to use named pipes or stdin (-) here but only with certain (not compressed) capture file formats (in particular: those that can be read without seeking backwards).</p>

</dd>
<dt id="R-Read-filter">-R &lt;Read filter&gt;</dt>
<dd>

<p>Cause the specified filter (which uses the syntax of read/display filters, rather than that of capture filters) to be applied during the first pass of analysis. Packets not matching the filter are not considered for future passes. Only makes sense with multiple passes, see -2. For regular filtering on single-pass dissect see -Y instead.</p>

<p>Note that forward-looking fields such as &#39;response in frame #&#39; cannot be used with this filter, since they will not have been calculate when this filter is applied.</p>

</dd>
<dt id="s-capture-snaplen">-s &lt;capture snaplen&gt;</dt>
<dd>

<p>Set the default snapshot length to use when capturing live data. No more than <i>snaplen</i> bytes of each network packet will be read into memory, or saved to disk. A value of 0 specifies a snapshot length of 65535, so that the full packet is captured; this is the default.</p>

<p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default snapshot length. If used after an <b>-i</b> option, it sets the snapshot length for the interface specified by the last <b>-i</b> option occurring before this option. If the snapshot length is not set specifically, the default snapshot length is used if provided.</p>

</dd>
<dt id="S-separator">-S &lt;separator&gt;</dt>
<dd>

<p>Set the line separator to be printed between packets.</p>

</dd>
<dt id="t-a-ad-adoy-d-dd-e-r-u-ud-udoy">-t a|ad|adoy|d|dd|e|r|u|ud|udoy</dt>
<dd>

<p>Set the format of the packet timestamp printed in summary lines. The format can be one of:</p>

<p><b>a</b> absolute: The absolute time, as local time in your time zone, is the actual time the packet was captured, with no date displayed</p>

<p><b>ad</b> absolute with date: The absolute date, displayed as YYYY-MM-DD, and time, as local time in your time zone, is the actual time and date the packet was captured</p>

<p><b>adoy</b> absolute with date using day of year: The absolute date, displayed as YYYY/DOY, and time, as local time in your time zone, is the actual time and date the packet was captured</p>

<p><b>d</b> delta: The delta time is the time since the previous packet was captured</p>

<p><b>dd</b> delta_displayed: The delta_displayed time is the time since the previous displayed packet was captured</p>

<p><b>e</b> epoch: The time in seconds since epoch (Jan 1, 1970 00:00:00)</p>

<p><b>r</b> relative: The relative time is the time elapsed between the first packet and the current packet</p>

<p><b>u</b> UTC: The absolute time, as UTC, is the actual time the packet was captured, with no date displayed</p>

<p><b>ud</b> UTC with date: The absolute date, displayed as YYYY-MM-DD, and time, as UTC, is the actual time and date the packet was captured</p>

<p><b>udoy</b> UTC with date using day of year: The absolute date, displayed as YYYY/DOY, and time, as UTC, is the actual time and date the packet was captured</p>

<p>The default format is relative.</p>

</dd>
<dt id="T-fields-pdml-ps-psml-text">-T fields|pdml|ps|psml|text</dt>
<dd>

<p>Set the format of the output when viewing decoded packet data. The options are one of:</p>

<p><b>fields</b> The values of fields specified with the <b>-e</b> option, in a form specified by the <b>-E</b> option. For example,</p>

<pre><code>  -T fields -E separator=, -E quote=d</code></pre>

<p>would generate comma-separated values (CSV) output suitable for importing into your favorite spreadsheet program.</p>

<p><b>pdml</b> Packet Details Markup Language, an XML-based format for the details of a decoded packet. This information is equivalent to the packet details printed with the <b>-V</b> flag.</p>

<p><b>ps</b> PostScript for a human-readable one-line summary of each of the packets, or a multi-line view of the details of each of the packets, depending on whether the <b>-V</b> flag was specified.</p>

<p><b>psml</b> Packet Summary Markup Language, an XML-based format for the summary information of a decoded packet. This information is equivalent to the information shown in the one-line summary printed by default.</p>

<p><b>text</b> Text of a human-readable one-line summary of each of the packets, or a multi-line view of the details of each of the packets, depending on whether the <b>-V</b> flag was specified. This is the default.</p>

</dd>
<dt id="u-seconds-type">-u &lt;seconds type&gt;</dt>
<dd>

<p>Specifies the seconds type. Valid choices are:</p>

<p><b>s</b> for seconds</p>

<p><b>hms</b> for hours, minutes and seconds</p>

</dd>
<dt id="v">-v</dt>
<dd>

<p>Print the version and exit.</p>

</dd>
<dt id="V">-V</dt>
<dd>

<p>Cause <b>TShark</b> to print a view of the packet details.</p>

</dd>
<dt id="w-outfile">-w &lt;outfile&gt; | -</dt>
<dd>

<p>Write raw packet data to <i>outfile</i> or to the standard output if <i>outfile</i> is &#39;-&#39;.</p>

<p>NOTE: -w provides raw packet data, not text. If you want text output you need to redirect stdout (e.g. using &#39;&gt;&#39;), don&#39;t use the <b>-w</b> option for this.</p>

</dd>
<dt id="W-file-format-option">-W &lt;file format option&gt;</dt>
<dd>

<p>Save extra information in the file if the format supports it. For example,</p>

<pre><code>  -F pcapng -W n</code></pre>

<p>will save host name resolution records along with captured packets.</p>

<p>Future versions of Wireshark may automatically change the capture format to <b>pcapng</b> as needed.</p>

<p>The argument is a string that may contain the following letter:</p>

<p><b>n</b> write network address resolution information (pcapng only)</p>

</dd>
<dt id="x">-x</dt>
<dd>

<p>Cause <b>TShark</b> to print a hex and ASCII dump of the packet data after printing the summary and/or details, if either are also being displayed.</p>

</dd>
<dt id="X-eXtension-options">-X &lt;eXtension options&gt;</dt>
<dd>

<p>Specify an option to be passed to a <b>TShark</b> module. The eXtension option is in the form <i>extension_key</i><b>:</b><i>value</i>, where <i>extension_key</i> can be:</p>

<p><b>lua_script</b>:<i>lua_script_filename</i> tells <b>TShark</b> to load the given script in addition to the default Lua scripts.</p>

<p><b>lua_script</b><i>num</i>:<i>argument</i> tells <b>TShark</b> to pass the given argument to the lua script identified by &#39;num&#39;, which is the number indexed order of the &#39;lua_script&#39; command. For example, if only one script was loaded with &#39;-X lua_script:my.lua&#39;, then &#39;-X lua_script1:foo&#39; will pass the string &#39;foo&#39; to the &#39;my.lua&#39; script. If two scripts were loaded, such as &#39;-X lua_script:my.lua&#39; and &#39;-X lua_script:other.lua&#39; in that order, then a &#39;-X lua_script2:bar&#39; would pass the string &#39;bar&#39; to the second lua script, namely &#39;other.lua&#39;.</p>

<p><b>read_format</b>:<i>file_format</i> tells <b>TShark</b> to use the given file format to read in the file (the file given in the <b>-r</b> command option). Providing no <i>file_format</i> argument, or an invalid one, will produce a file of available file formats to use.</p>

</dd>
<dt id="y-capture-link-type">-y &lt;capture link type&gt;</dt>
<dd>

<p>Set the data link type to use while capturing packets. The values reported by <b>-L</b> are the values that can be used.</p>

<p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default capture link type. If used after an <b>-i</b> option, it sets the capture link type for the interface specified by the last <b>-i</b> option occurring before this option. If the capture link type is not set specifically, the default capture link type is used if provided.</p>

</dd>
<dt id="Y-displaY-filter">-Y &lt;displaY filter&gt;</dt>
<dd>

<p>Cause the specified filter (which uses the syntax of read/display filters, rather than that of capture filters) to be applied before printing a decoded form of packets or writing packets to a file. Packets matching the filter are printed or written to file; packets that the matching packets depend upon (e.g., fragments), are not printed but are written to file; packets not matching the filter nor depended upon are discarded rather than being printed or written.</p>

<p>Use this instead of -R for filtering using single-pass analysis. If doing two-pass analysis (see -2) then only packets matching the read filter (if there is one) will be checked against this filter.</p>

</dd>
<dt id="z-statistics">-z &lt;statistics&gt;</dt>
<dd>

<p>Get <b>TShark</b> to collect various types of statistics and display the result after finishing reading the capture file. Use the <b>-q</b> flag if you&#39;re reading a capture file and only want the statistics printed, not any per-packet information.</p>

<p>Note that the <b>-z proto</b> option is different - it doesn&#39;t cause statistics to be gathered and printed when the capture is complete, it modifies the regular packet summary output to include the values of fields specified with the option. Therefore you must not use the <b>-q</b> option, as that option would suppress the printing of the regular packet summary output, and must also not use the <b>-V</b> option, as that would cause packet detail information rather than packet summary information to be printed.</p>

<p>Currently implemented statistics are:</p>

<dl>

<dt id="z-help"><b>-z help</b></dt>
<dd>

<p>Display all possible values for <b>-z</b>.</p>

</dd>
<dt id="z-afp-srt-filter"><b>-z</b> afp,srt[,<i>filter</i>]</dt>
<dd>

<p>Show Apple Filing Protocol service response time statistics.</p>

</dd>
<dt id="z-camel-srt"><b>-z</b> camel,srt</dt>
<dd>

</dd>
<dt id="z-compare-start-stop-ttl-0-1-order-0-1-variance-filter"><b>-z</b> compare,<i>start</i>,<i>stop</i>,<i>ttl[0|1]</i>,<i>order[0|1]</i>,<i>variance</i>[,<i>filter</i>]</dt>
<dd>

<p>If the optional <i>filter</i> is specified, only those packets that match the filter will be used in the calculations.</p>

</dd>
<dt id="z-conv-type-filter"><b>-z</b> conv,<i>type</i>[,<i>filter</i>]</dt>
<dd>

<p>Create a table that lists all conversations that could be seen in the capture. <i>type</i> specifies the conversation endpoint types for which we want to generate the statistics; currently the supported ones are:</p>

<pre><code>  &quot;bluetooth&quot;  Bluetooth addresses
  &quot;eth&quot;   Ethernet addresses
  &quot;fc&quot;    Fibre Channel addresses
  &quot;fddi&quot;  FDDI addresses
  &quot;ip&quot;    IPv4 addresses
  &quot;ipv6&quot;  IPv6 addresses
  &quot;ipx&quot;   IPX addresses
  &quot;jxta&quot;  JXTA message addresses
  &quot;ncp&quot;   NCP connections
  &quot;rsvp&quot;  RSVP connections
  &quot;sctp&quot;  SCTP addresses
  &quot;tcp&quot;   TCP/IP socket pairs  Both IPv4 and IPv6 are supported
  &quot;tr&quot;    Token Ring addresses
  &quot;usb&quot;   USB addresses
  &quot;udp&quot;   UDP/IP socket pairs  Both IPv4 and IPv6 are supported
  &quot;wlan&quot;  IEEE 802.11 addresses</code></pre>

<p>If the optional <i>filter</i> is specified, only those packets that match the filter will be used in the calculations.</p>

<p>The table is presented with one line for each conversation and displays the number of packets/bytes in each direction as well as the total number of packets/bytes. The table is sorted according to the total number of frames.</p>

</dd>
<dt id="z-dcerpc-srt-uuid-major.minor-filter"><b>-z</b> dcerpc,srt,<i>uuid</i>,<i>major</i>.<i>minor</i>[,<i>filter</i>]</dt>
<dd>

<p>Collect call/reply SRT (Service Response Time) data for DCERPC interface <i>uuid</i>, version <i>major</i>.<i>minor</i>. Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.</p>

<p>Example: <span style="white-space: nowrap;"><b>-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0</b></span> will collect data for the CIFS SAMR Interface.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter.</p>

<p>Example: <span style="white-space: nowrap;"><b>-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4</b></span> will collect SAMR SRT statistics for a specific host.</p>

</dd>
<dt id="z-bootp-stat-filter"><b>-z</b> bootp,stat[,<i>filter</i>]</dt>
<dd>

<p>Show DHCP (BOOTP) statistics.</p>

</dd>
<dt id="z-diameter-avp-cmd.code-field-field"><b>-z</b> diameter,avp[,<i>cmd.code</i>,<i>field</i>,<i>field</i>,<i>...</i>]</dt>
<dd>

<p>This option enables extraction of most important diameter fields from large capture files. Exactly one text line for each diameter message with matched <b>diameter.cmd.code</b> will be printed.</p>

<p>Empty diameter command code or &#39;*&#39; can be specified to mach any <b>diameter.cmd.code</b></p>

<p>Example: <b>-z diameter,avp</b> extract default field set from diameter messages.</p>

<p>Example: <b>-z diameter,avp,280</b> extract default field set from diameter DWR messages.</p>

<p>Example: <b>-z diameter,avp,272</b> extract default field set from diameter CC messages.</p>

<p>Extract most important fields from diameter CC messages:</p>

<p><b>tshark -r file.cap.gz -q -z diameter,avp,272,CC-Request-Type,CC-Request-Number,Session-Id,Subscription-Id-Data,Rating-Group,Result-Code</b></p>

<p>Following fields will be printed out for each diameter message:</p>

<pre><code>  &quot;frame&quot;        Frame number.
  &quot;time&quot;         Unix time of the frame arrival.
  &quot;src&quot;          Source address.
  &quot;srcport&quot;      Source port.
  &quot;dst&quot;          Destination address.
  &quot;dstport&quot;      Destination port.
  &quot;proto&quot;        Constant string &#39;diameter&#39;, which can be used for post processing of tshark output.  E.g. grep/sed/awk.
  &quot;msgnr&quot;        seq. number of diameter message within the frame.  E.g. &#39;2&#39; for the third diameter message in the same frame.
  &quot;is_request&quot;   &#39;0&#39; if message is a request, &#39;1&#39; if message is an answer.
  &quot;cmd&quot;          diameter.cmd_code, E.g. &#39;272&#39; for credit control messages.
  &quot;req_frame&quot;    Number of frame where matched request was found or &#39;0&#39;.
  &quot;ans_frame&quot;    Number of frame where matched answer was found or &#39;0&#39;.
  &quot;resp_time&quot;    response time in seconds, &#39;0&#39; in case if matched Request/Answer is not found in trace.  E.g. in the begin or end of capture.</code></pre>

<p><b>-z diameter,avp</b> option is much faster than <b>-V -T text</b> or <b>-T pdml</b> options.</p>

<p><b>-z diameter,avp</b> option is more powerful than <b>-T field</b> and <b>-z proto,colinfo</b> options.</p>

<p>Multiple diameter messages in one frame are supported.</p>

<p>Several fields with same name within one diameter message are supported, e.g. <i>diameter.Subscription-Id-Data</i> or <i>diameter.Rating-Group</i>.</p>

<p>Note: <b>tshark -q</b> option is recommended to suppress default <b>tshark</b> output.</p>

</dd>
<dt id="z-dns-tree-filter"><b>-z</b> dns,tree[,<i>filter</i>]</dt>
<dd>

<p>Create a summary of the captured DNS packets. General information are collected such as qtype and qclass distribution. For some data (as qname length or DNS payload) max, min and average values are also displayed.</p>

</dd>
<dt id="z-endpoints-type-filter"><b>-z</b> endpoints,<i>type</i>[,<i>filter</i>]</dt>
<dd>

<p>Create a table that lists all endpoints that could be seen in the capture. <i>type</i> specifies the endpoint types for which we want to generate the statistics; currently the supported ones are:</p>

<pre><code>  &quot;bluetooth&quot;  Bluetooth addresses
  &quot;eth&quot;   Ethernet addresses
  &quot;fc&quot;    Fibre Channel addresses
  &quot;fddi&quot;  FDDI addresses
  &quot;ip&quot;    IPv4 addresses
  &quot;ipv6&quot;  IPv6 addresses
  &quot;ipx&quot;   IPX addresses
  &quot;jxta&quot;  JXTA message addresses
  &quot;ncp&quot;   NCP connections
  &quot;rsvp&quot;  RSVP connections
  &quot;sctp&quot;  SCTP addresses
  &quot;tcp&quot;   TCP/IP socket pairs  Both IPv4 and IPv6 are supported
  &quot;tr&quot;    Token Ring addresses
  &quot;usb&quot;   USB addresses
  &quot;udp&quot;   UDP/IP socket pairs  Both IPv4 and IPv6 are supported
  &quot;wlan&quot;  IEEE 802.11 addresses</code></pre>

<p>If the optional <i>filter</i> is specified, only those packets that match the filter will be used in the calculations.</p>

<p>The table is presented with one line for each conversation and displays the number of packets/bytes in each direction as well as the total number of packets/bytes. The table is sorted according to the total number of frames.</p>

</dd>
<dt id="z-expert-error-warn-note-chat-filter"><b>-z</b> expert[<i>,error|,warn|,note|,chat</i>][<i>,filter</i>]</dt>
<dd>

<p>Collects information about all expert info, and will display them in order, grouped by severity.</p>

<p>Example: <b>-z expert,sip</b> will show expert items of all severity for frames that match the sip protocol.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter.</p>

<p>Example: <b>-z &quot;expert,note,tcp&quot;</b> will only collect expert items for frames that include the tcp protocol, with a severity of note or higher.</p>

</dd>
<dt id="z-follow-prot-mode-filter-range"><b>-z</b> follow,<i>prot</i>,<i>mode</i>,<i>filter</i>[<i>,range</i>]</dt>
<dd>

<p>Displays the contents of a TCP or UDP stream between two nodes. The data sent by the second node is prefixed with a tab to differentiate it from the data sent by the first node.</p>

<p><i>prot</i> specifies the transport protocol. It can be one of:</p>

<pre><code>  tcp   TCP
  udp   UDP
  ssl   SSL</code></pre>

<p><i>mode</i> specifies the output mode. It can be one of:</p>

<pre><code>  ascii  ASCII output with dots for non-printable characters
  ebcdic EBCDIC output with dots for non-printable characters
  hex    Hexadecimal and ASCII data with offsets
  raw    Hexadecimal data</code></pre>

<p>Since the output in <b>ascii</b> or <b>ebcdic</b> mode may contain newlines, the length of each section of output plus a newline precedes each section of output.</p>

<p><i>filter</i> specifies the stream to be displayed. UDP/TCP streams are selected with either the stream index or IP address plus port pairs. SSL streams are selected with the stream index. For example:</p>

<pre><code>  ip-addr0:port0,ip-addr1:port1
  stream-index</code></pre>

<p><i>range</i> optionally specifies which &quot;chunks&quot; of the stream should be displayed.</p>

<p>Example: <b>-z &quot;follow,tcp,hex,1&quot;</b> will display the contents of the first TCP stream in &quot;hex&quot; format.</p>

<pre><code>  ===================================================================
  Follow: tcp,hex
  Filter: tcp.stream eq 1
  Node 0: 200.57.7.197:32891
  Node 1: 200.57.7.198:2906
  00000000  00 00 00 22 00 00 00 07  00 0a 85 02 07 e9 00 02  ...&quot;.... ........
  00000010  07 e9 06 0f 00 0d 00 04  00 00 00 01 00 03 00 06  ........ ........
  00000020  1f 00 06 04 00 00                                 ......
      00000000  00 01 00 00                                       ....
      00000026  00 02 00 00</code></pre>

<p>Example: <b>-z &quot;follow,tcp,ascii,200.57.7.197:32891,200.57.7.198:2906&quot;</b> will display the contents of a TCP stream between 200.57.7.197 port 32891 and 200.57.7.98 port 2906.</p>

<pre><code>  ===================================================================
  Follow: tcp,ascii
  Filter: (omitted for readability)
  Node 0: 200.57.7.197:32891
  Node 1: 200.57.7.198:2906
  38
  ...&quot;.....
  ................
      4
      ....</code></pre>

</dd>
<dt id="z-h225-counter-filter"><b>-z</b> h225,counter[<i>,filter</i>]</dt>
<dd>

<p>Count ITU-T H.225 messages and their reasons. In the first column you get a list of H.225 messages and H.225 message reasons, which occur in the current capture file. The number of occurrences of each message or reason is displayed in the second column.</p>

<p>Example: <b>-z h225,counter</b>.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter. Example: use <b>-z &quot;h225,counter,ip.addr==1.2.3.4&quot;</b> to only collect stats for H.225 packets exchanged by the host at IP address 1.2.3.4 .</p>

<p>This option can be used multiple times on the command line.</p>

</dd>
<dt id="z-h225-srt-filter"><b>-z</b> h225,srt[<i>,filter</i>]</dt>
<dd>

<p>Collect requests/response SRT (Service Response Time) data for ITU-T H.225 RAS. Data collected is number of calls of each ITU-T H.225 RAS Message Type, Minimum SRT, Maximum SRT, Average SRT, Minimum in Packet, and Maximum in Packet. You will also get the number of Open Requests (Unresponded Requests), Discarded Responses (Responses without matching request) and Duplicate Messages.</p>

<p>Example: <b>-z h225,srt</b></p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter.</p>

<p>Example: <b>-z &quot;h225,srt,ip.addr==1.2.3.4&quot;</b> will only collect stats for ITU-T H.225 RAS packets exchanged by the host at IP address 1.2.3.4 .</p>

</dd>
<dt id="z-hosts-ipv4-ipv6"><b>-z</b> hosts[,ipv4][,ipv6]</dt>
<dd>

<p>Dump any collected IPv4 and/or IPv6 addresses in &quot;hosts&quot; format. Both IPv4 and IPv6 addresses are dumped by default.</p>

<p>Addresses are collected from a number of sources, including standard &quot;hosts&quot; files and captured traffic.</p>

</dd>
<dt id="z-hpfeeds-tree-filter"><b>-z</b> hpfeeds,tree[,<i>filter</i>]</dt>
<dd>

<p>Calculate statistics for HPFEEDS traffic such as publish per channel, and opcode distribution.</p>

</dd>
<dt id="z-http-stat"><b>-z</b> http,stat,</dt>
<dd>

<p>Calculate the HTTP statistics distribution. Displayed values are the HTTP status codes and the HTTP request methods.</p>

</dd>
<dt id="z-http-tree"><b>-z</b> http,tree</dt>
<dd>

<p>Calculate the HTTP packet distribution. Displayed values are the HTTP request modes and the HTTP status codes.</p>

</dd>
<dt id="z-http_req-tree"><b>-z</b> http_req,tree</dt>
<dd>

<p>Calculate the HTTP requests by server. Displayed values are the server name and the URI path.</p>

</dd>
<dt id="z-http_srv-tree"><b>-z</b> http_srv,tree</dt>
<dd>

<p>Calculate the HTTP requests and responses by server. For the HTTP requests, displayed values are the server IP address and server hostname. For the HTTP responses, displayed values are the server IP address and status.</p>

</dd>
<dt id="z-icmp-srt-filter"><b>-z</b> icmp,srt[,<i>filter</i>]</dt>
<dd>

<p>Compute total ICMP echo requests, replies, loss, and percent loss, as well as minimum, maximum, mean, median and sample standard deviation SRT statistics typical of what ping provides.</p>

<p>Example: <span style="white-space: nowrap;"><b>-z icmp,srt,ip.src==1.2.3.4</b></span> will collect ICMP SRT statistics for ICMP echo request packets originating from a specific host.</p>

<p>This option can be used multiple times on the command line.</p>

</dd>
<dt id="z-icmpv6-srt-filter"><b>-z</b> icmpv6,srt[,<i>filter</i>]</dt>
<dd>

<p>Compute total ICMPv6 echo requests, replies, loss, and percent loss, as well as minimum, maximum, mean, median and sample standard deviation SRT statistics typical of what ping provides.</p>

<p>Example: <span style="white-space: nowrap;"><b>-z icmpv6,srt,ipv6.src==fe80::1</b></span> will collect ICMPv6 SRT statistics for ICMPv6 echo request packets originating from a specific host.</p>

<p>This option can be used multiple times on the command line.</p>

</dd>
<dt id="z-io-phs-filter"><b>-z</b> io,phs[,<i>filter</i>]</dt>
<dd>

<p>Create Protocol Hierarchy Statistics listing both number of packets and bytes. If no <i>filter</i> is specified the statistics will be calculated for all packets. If a <i>filter</i> is specified statistics will only be calculated for those packets that match the filter.</p>

<p>This option can be used multiple times on the command line.</p>

</dd>
<dt id="z-io-stat-interval-filter-filter-filter"><b>-z</b> io,stat,<i>interval</i>[,<i>filter</i>][,<i>filter</i>][,<i>filter</i>]...</dt>
<dd>

<p>Collect packet/bytes statistics for the capture in intervals of <i>interval</i> seconds. <i>Interval</i> can be specified either as a whole or fractional second and can be specified with microsecond (us) resolution. If <i>interval</i> is 0, the statistics will be calculated over all packets.</p>

<p>If no <i>filter</i> is specified the statistics will be calculated for all packets. If one or more <i>filters</i> are specified statistics will be calculated for all filters and presented with one column of statistics for each filter.</p>

<p>This option can be used multiple times on the command line.</p>

<p>Example: <b>-z io,stat,1,ip.addr==1.2.3.4</b> will generate 1 second statistics for all traffic to/from host 1.2.3.4.</p>

<p>Example: <b>-z &quot;io,stat,0.001,smb&amp;&amp;ip.addr==1.2.3.4&quot;</b> will generate 1ms statistics for all SMB packets to/from host 1.2.3.4.</p>

<p>The examples above all use the standard syntax for generating statistics which only calculates the number of packets and bytes in each interval.</p>

<p><b>io,stat</b> can also do much more statistics and calculate COUNT(), SUM(), MIN(), MAX(), AVG() and LOAD() using a slightly different filter syntax:</p>

</dd>
<dt id="z-io-stat-interval-COUNT-SUM-MIN-MAX-AVG-LOAD-field-filter">-z io,stat,<i>interval</i>,&quot;[COUNT|SUM|MIN|MAX|AVG|LOAD](<i>field</i>)<i>filter</i>&quot;</dt>
<dd>

<p>NOTE: One important thing to note here is that the filter is not optional and that the field that the calculation is based on MUST be part of the filter string or the calculation will fail.</p>

<p>So: <b>-z io,stat,0.010,AVG(smb.time)</b> does not work. Use <b>-z io,stat,0.010,AVG(smb.time)smb.time</b> instead. Also be aware that a field can exist multiple times inside the same packet and will then be counted multiple times in those packets.</p>

<p>NOTE: A second important thing to note is that the system setting for decimal separator must be set to &quot;.&quot;! If it is set to &quot;,&quot; the statistics will not be displayed per filter.</p>

<p><b>COUNT(<i>field</i>)<i>filter</i></b> - Calculates the number of times that the field <i>name</i> (not its value) appears per interval in the filtered packet list. &#39;&#39;<i>field</i>&#39;&#39; can be any display filter name.</p>

<p>Example: <b>-z io,stat,0.010,&quot;COUNT(smb.sid)smb.sid&quot;</b></p>

<p>This will count the total number of SIDs seen in each 10ms interval.</p>

<p><b>SUM(<i>field</i>)<i>filter</i></b> - Unlike COUNT, the <i>values</i> of the specified field are summed per time interval. &#39;&#39;<i>field</i>&#39;&#39; can only be a named integer, float, double or relative time field.</p>

<p>Example: <b>-z io,stat,0.010,&quot;SUM(frame.len)frame.len&quot;</b></p>

<p>Reports the total number of bytes that were transmitted bidirectionally in all the packets within a 10 millisecond interval.</p>

<p><b>MIN/MAX/AVG(<i>field</i>)<i>filter</i></b> - The minimum, maximum, or average field value in each interval is calculated. The specified field must be a named integer, float, double or relative time field. For relative time fields, the output is presented in seconds with six decimal digits of precision rounded to the nearest microsecond.</p>

<p>In the following example, the time of the first Read_AndX call, the last Read_AndX response values are displayed and the minimum, maximum, and average Read response times (SRTs) are calculated. NOTE: If the DOS command shell line continuation character, &#39;&#39;^&#39;&#39; is used, each line cannot end in a comma so it is placed at the beginning of each continuation line:</p>

<pre><code>  tshark -o tcp.desegment_tcp_streams:FALSE -n -q -r smb_reads.cap -z io,stat,0,
  &quot;MIN(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==0&quot;,
  &quot;MAX(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==1&quot;,
  &quot;MIN(smb.time)smb.time and smb.cmd==0x2e&quot;,
  &quot;MAX(smb.time)smb.time and smb.cmd==0x2e&quot;,
  &quot;AVG(smb.time)smb.time and smb.cmd==0x2e&quot;


  ======================================================================================================
  IO Statistics
  Column #0: MIN(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==0
  Column #1: MAX(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==1
  Column #2: MIN(smb.time)smb.time and smb.cmd==0x2e
  Column #3: MAX(smb.time)smb.time and smb.cmd==0x2e
  Column #4: AVG(smb.time)smb.time and smb.cmd==0x2e
                  |    Column #0   |    Column #1   |    Column #2   |    Column #3   |    Column #4   |
  Time            |       MIN      |       MAX      |       MIN      |       MAX      |       AVG      |
  000.000-                 0.000000         7.704054         0.000072         0.005539         0.000295
  ======================================================================================================</code></pre>

<p>The following command displays the average SMB Read response PDU size, the total number of read PDU bytes, the average SMB Write request PDU size, and the total number of bytes transferred in SMB Write PDUs:</p>

<pre><code>  tshark -n -q -r smb_reads_writes.cap -z io,stat,0,
  &quot;AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to&quot;,
  &quot;SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to&quot;,
  &quot;AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to&quot;,
  &quot;SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to&quot;

  =====================================================================================
  IO Statistics
  Column #0: AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to
  Column #1: SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to
  Column #2: AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to
  Column #3: SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to
                  |    Column #0   |    Column #1   |    Column #2   |    Column #3   |
  Time            |       AVG      |       SUM      |       AVG      |       SUM      |
  000.000-                    30018         28067522               72             3240
  =====================================================================================</code></pre>

<p><b>LOAD(<i>field</i>)<i>filter</i></b> - The LOAD/Queue-Depth in each interval is calculated. The specified field must be a relative time field that represents a response time. For example smb.time. For each interval the Queue-Depth for the specified protocol is calculated.</p>

<p>The following command displays the average SMB LOAD. A value of 1.0 represents one I/O in flight.</p>

<pre><code>  tshark -n -q -r smb_reads_writes.cap
  -z &quot;io,stat,0.001,LOAD(smb.time)smb.time&quot;

  ============================================================================
  IO Statistics
  Interval:   0.001000 secs
  Column #0: LOAD(smb.time)smb.time
                          |    Column #0   |
  Time                    |       LOAD     |
  0000.000000-0000.001000         1.000000
  0000.001000-0000.002000         0.741000
  0000.002000-0000.003000         0.000000
  0000.003000-0000.004000         1.000000</code></pre>

<p><b>FRAMES | BYTES[()<i>filter</i>]</b> - Displays the total number of frames or bytes. The filter field is optional but if included it must be prepended with &#39;&#39;()&#39;&#39;.</p>

<p>The following command displays five columns: the total number of frames and bytes (transferred bidirectionally) using a single comma, the same two stats using the FRAMES and BYTES subcommands, the total number of frames containing at least one SMB Read response, and the total number of bytes transmitted to the client (unidirectionally) at IP address 10.1.0.64.</p>

<pre><code>  tshark -o tcp.desegment_tcp_streams:FALSE -n -q -r smb_reads.cap -z io,stat,0,,FRAMES,BYTES,
  &quot;FRAMES()smb.cmd==0x2e and smb.response_to&quot;,&quot;BYTES()ip.dst==10.1.0.64&quot;

  =======================================================================================================================
  IO Statistics
  Column #0:
  Column #1: FRAMES
  Column #2: BYTES
  Column #3: FRAMES()smb.cmd==0x2e and smb.response_to
  Column #4: BYTES()ip.dst==10.1.0.64
                  |            Column #0            |    Column #1   |    Column #2   |    Column #3   |    Column #4   |
  Time            |     Frames     |      Bytes     |     FRAMES     |     BYTES      |     FRAMES     |     BYTES      |
  000.000-                    33576         29721685            33576         29721685              870         29004801
  =======================================================================================================================</code></pre>

</dd>
<dt id="z-mac-lte-stat-filter"><b>-z</b> mac-lte,stat[<i>,filter</i>]</dt>
<dd>

<p>This option will activate a counter for LTE MAC messages. You will get information about the maximum number of UEs/TTI, common messages and various counters for each UE that appears in the log.</p>

<p>Example: <b>-z mac-lte,stat</b>.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated for those frames that match that filter. Example: <b>-z &quot;mac-lte,stat,mac-lte.rnti</b>3000&quot;&gt; will only collect stats for UEs with an assigned RNTI whose value is more than 3000.</p>

</dd>
<dt id="z-megaco-rtd-filter"><b>-z</b> megaco,rtd[<i>,filter</i>]</dt>
<dd>

<p>Collect requests/response RTD (Response Time Delay) data for MEGACO. (This is similar to <b>-z smb,srt</b>). Data collected is the number of calls for each known MEGACO Type, MinRTD, MaxRTD and AvgRTD. Additionally you get the number of duplicate requests/responses, unresponded requests, responses, which don&#39;t match with any request. Example: <b>-z megaco,rtd</b>.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter. Example: <b>-z &quot;megaco,rtd,ip.addr==1.2.3.4&quot;</b> will only collect stats for MEGACO packets exchanged by the host at IP address 1.2.3.4 .</p>

<p>This option can be used multiple times on the command line.</p>

</dd>
<dt id="z-mgcp-rtd-filter"><b>-z</b> mgcp,rtd[<i>,filter</i>]</dt>
<dd>

<p>Collect requests/response RTD (Response Time Delay) data for MGCP. (This is similar to <b>-z smb,srt</b>). Data collected is the number of calls for each known MGCP Type, MinRTD, MaxRTD and AvgRTD. Additionally you get the number of duplicate requests/responses, unresponded requests, responses, which don&#39;t match with any request. Example: <b>-z mgcp,rtd</b>.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter. Example: <b>-z &quot;mgcp,rtd,ip.addr==1.2.3.4&quot;</b> will only collect stats for MGCP packets exchanged by the host at IP address 1.2.3.4 .</p>

</dd>
<dt id="z-proto-colinfo-filter-field"><b>-z</b> proto,colinfo,<i>filter</i>,<i>field</i></dt>
<dd>

<p>Append all <i>field</i> values for the packet to the Info column of the one-line summary output. This feature can be used to append arbitrary fields to the Info column in addition to the normal content of that column. <i>field</i> is the display-filter name of a field which value should be placed in the Info column. <i>filter</i> is a filter string that controls for which packets the field value will be presented in the info column. <i>field</i> will only be presented in the Info column for the packets which match <i>filter</i>.</p>

<p>NOTE: In order for <b>TShark</b> to be able to extract the <i>field</i> value from the packet, <i>field</i> MUST be part of the <i>filter</i> string. If not, <b>TShark</b> will not be able to extract its value.</p>

<p>For a simple example to add the &quot;nfs.fh.hash&quot; field to the Info column for all packets containing the &quot;nfs.fh.hash&quot; field, use</p>

<p><b>-z proto,colinfo,nfs.fh.hash,nfs.fh.hash</b></p>

<p>To put &quot;nfs.fh.hash&quot; in the Info column but only for packets coming from host 1.2.3.4 use:</p>

<p><b>-z &quot;proto,colinfo,nfs.fh.hash &amp;&amp; ip.src==1.2.3.4,nfs.fh.hash&quot;</b></p>

<p>This option can be used multiple times on the command line.</p>

</dd>
<dt id="z-rlc-lte-stat-filter"><b>-z</b> rlc-lte,stat[<i>,filter</i>]</dt>
<dd>

<p>This option will activate a counter for LTE RLC messages. You will get information about common messages and various counters for each UE that appears in the log.</p>

<p>Example: <b>-z rlc-lte,stat</b>.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated for those frames that match that filter. Example: <b>-z &quot;rlc-lte,stat,rlc-lte.ueid</b>3000&quot;&gt; will only collect stats for UEs with a UEId of more than 3000.</p>

</dd>
<dt id="z-rpc-programs"><b>-z</b> rpc,programs</dt>
<dd>

<p>Collect call/reply SRT data for all known ONC-RPC programs/versions. Data collected is number of calls for each protocol/version, MinSRT, MaxSRT and AvgSRT. This option can only be used once on the command line.</p>

</dd>
<dt id="z-rpc-srt-program-version-filter"><b>-z</b> rpc,srt,<i>program</i>,<i>version</i>[,<i>filter</i>]</dt>
<dd>

<p>Collect call/reply SRT (Service Response Time) data for <i>program</i>/<i>version</i>. Data collected is the number of calls for each procedure, MinSRT, MaxSRT, AvgSRT, and the total time taken for each procedure.</p>

<p>Example: <b>-z rpc,srt,100003,3</b> will collect data for NFS v3.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter.</p>

<p>Example: <b>-z rpc,srt,100003,3,nfs.fh.hash==0x12345678</b> will collect NFS v3 SRT statistics for a specific file.</p>

</dd>
<dt id="z-rtp-streams"><b>-z</b> rtp,streams</dt>
<dd>

<p>Collect statistics for all RTP streams and calculate max. delta, max. and mean jitter and packet loss percentages.</p>

</dd>
<dt id="z-scsi-srt-cmdset-filter"><b>-z</b> scsi,srt,<i>cmdset</i>[,<i>filter</i>]</dt>
<dd>

<p>Collect call/reply SRT (Service Response Time) data for SCSI commandset <i>cmdset</i>.</p>

<p>Commandsets are 0:SBC 1:SSC 5:MMC</p>

<p>Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.</p>

<p>Example: <b>-z scsi,srt,0</b> will collect data for SCSI BLOCK COMMANDS (SBC).</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter.</p>

<p>Example: <b>-z scsi,srt,0,ip.addr==1.2.3.4</b> will collect SCSI SBC SRT statistics for a specific iscsi/ifcp/fcip host.</p>

</dd>
<dt id="z-sip-stat-filter"><b>-z</b> sip,stat[<i>,filter</i>]</dt>
<dd>

<p>This option will activate a counter for SIP messages. You will get the number of occurrences of each SIP Method and of each SIP Status-Code. Additionally you also get the number of resent SIP Messages (only for SIP over UDP).</p>

<p>Example: <b>-z sip,stat</b>.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter. Example: <b>-z &quot;sip,stat,ip.addr==1.2.3.4&quot;</b> will only collect stats for SIP packets exchanged by the host at IP address 1.2.3.4 .</p>

</dd>
<dt id="z-smb-sids"><b>-z</b> smb,sids</dt>
<dd>

<p>When this feature is used <b>TShark</b> will print a report with all the discovered SID and account name mappings. Only those SIDs where the account name is known will be presented in the table.</p>

<p>For this feature to work you will need to either to enable &quot;Edit/Preferences/Protocols/SMB/Snoop SID to name mappings&quot; in the preferences or you can override the preferences by specifying <span style="white-space: nowrap;"><b>-o &quot;smb.sid_name_snooping:TRUE&quot;</b></span> on the <b>TShark</b> command line.</p>

<p>The current method used by <b>TShark</b> to find the SID-&gt;name mapping is relatively restricted with a hope of future expansion.</p>

</dd>
<dt id="z-smb-srt-filter"><b>-z</b> smb,srt[,<i>filter</i>]</dt>
<dd>

<p>Collect call/reply SRT (Service Response Time) data for SMB. Data collected is number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.</p>

<p>Example: <b>-z smb,srt</b></p>

<p>The data will be presented as separate tables for all normal SMB commands, all Transaction2 commands and all NT Transaction commands. Only those commands that are seen in the capture will have its stats displayed. Only the first command in a xAndX command chain will be used in the calculation. So for common SessionSetupAndX + TreeConnectAndX chains, only the SessionSetupAndX call will be used in the statistics. This is a flaw that might be fixed in the future.</p>

<p>This option can be used multiple times on the command line.</p>

<p>If the optional <i>filter</i> is provided, the stats will only be calculated on those calls that match that filter.</p>

<p>Example: <b>-z &quot;smb,srt,ip.addr==1.2.3.4&quot;</b> will only collect stats for SMB packets exchanged by the host at IP address 1.2.3.4 .</p>

</dd>
<dt id="capture-comment-comment">--capture-comment &lt;comment&gt;</dt>
<dd>

<p>Add a capture comment to the output file.</p>

<p>This option is only available if a new output file in pcapng format is created. Only one capture comment may be set per output file.</p>

</dd>
<dt id="disable-protocol-proto_name">--disable-protocol &lt;proto_name&gt;</dt>
<dd>

<p>Disable dissection of proto_name.</p>

</dd>
<dt id="enable-heuristic-short_name">--enable-heuristic &lt;short_name&gt;</dt>
<dd>

<p>Enable dissection of heuristic protocol.</p>

</dd>
<dt id="disable-heuristic-short_name">--disable-heuristic &lt;short_name&gt;</dt>
<dd>

<p>Disable dissection of heuristic protocol.</p>

</dd>
</dl>

</dd>
</dl>

<h1 id="CAPTURE-FILTER-SYNTAX">CAPTURE FILTER SYNTAX</h1>

<p>See the manual page of pcap-filter(7) or, if that doesn&#39;t exist, tcpdump(8), or, if that doesn&#39;t exist, <a href="https://wiki.wireshark.org/CaptureFilters">https://wiki.wireshark.org/CaptureFilters</a>.</p>

<h1 id="READ-FILTER-SYNTAX">READ FILTER SYNTAX</h1>

<p>For a complete table of protocol and protocol fields that are filterable in <b>TShark</b> see the wireshark-filter(4) manual page.</p>

<h1 id="FILES">FILES</h1>

<p>These files contains various <b>Wireshark</b> configuration values.</p>

<dl>

<dt id="Preferences">Preferences</dt>
<dd>

<p>The <i>preferences</i> files contain global (system-wide) and personal preference settings. If the system-wide preference file exists, it is read first, overriding the default settings. If the personal preferences file exists, it is read next, overriding any previous values. Note: If the command line option <b>-o</b> is used (possibly more than once), it will in turn override values from the preferences files.</p>

<p>The preferences settings are in the form <i>prefname</i><b>:</b><i>value</i>, one per line, where <i>prefname</i> is the name of the preference and <i>value</i> is the value to which it should be set; white space is allowed between <b>:</b> and <i>value</i>. A preference setting can be continued on subsequent lines by indenting the continuation lines with white space. A <b>#</b> character starts a comment that runs to the end of the line:</p>

<pre><code>  # Capture in promiscuous mode?
  # TRUE or FALSE (case-insensitive).
  capture.prom_mode: TRUE</code></pre>

<p>The global preferences file is looked for in the <i>wireshark</i> directory under the <i>share</i> subdirectory of the main installation directory (for example, <i>/usr/local/share/wireshark/preferences</i>) on UNIX-compatible systems, and in the main installation directory (for example, <i>C:\Program Files\Wireshark\preferences</i>) on Windows systems.</p>

<p>The personal preferences file is looked for in <i>$HOME/.wireshark/preferences</i> on UNIX-compatible systems and <i>%APPDATA%\Wireshark\preferences</i> (or, if %APPDATA% isn&#39;t defined, <i>%USERPROFILE%\Application Data\Wireshark\preferences</i>) on Windows systems.</p>

</dd>
<dt id="Disabled-Enabled-Protocols">Disabled (Enabled) Protocols</dt>
<dd>

<p>The <i>disabled_protos</i> files contain system-wide and personal lists of protocols that have been disabled, so that their dissectors are never called. The files contain protocol names, one per line, where the protocol name is the same name that would be used in a display filter for the protocol:</p>

<pre><code>  http
  tcp     # a comment</code></pre>

<p>The global <i>disabled_protos</i> file uses the same directory as the global preferences file.</p>

<p>The personal <i>disabled_protos</i> file uses the same directory as the personal preferences file.</p>

</dd>
<dt id="Name-Resolution-hosts">Name Resolution (hosts)</dt>
<dd>

<p>If the personal <i>hosts</i> file exists, it is used to resolve IPv4 and IPv6 addresses before any other attempts are made to resolve them. The file has the standard <i>hosts</i> file syntax; each line contains one IP address and name, separated by whitespace. The same directory as for the personal preferences file is used.</p>

<p>Capture filter name resolution is handled by libpcap on UNIX-compatible systems and WinPcap on Windows. As such the Wireshark personal <i>hosts</i> file will not be consulted for capture filter name resolution.</p>

</dd>
<dt id="Name-Resolution-subnets">Name Resolution (subnets)</dt>
<dd>

<p>If the an IPv4 address cannot be translated via name resolution (no exact match is found) then a partial match is attempted via the <i>subnets</i> file.</p>

<p>Each line of this file consists of an IPv4 address, a subnet mask length separated only by a / and a name separated by whitespace. While the address must be a full IPv4 address, any values beyond the mask length are subsequently ignored.</p>

<p>An example is:</p>

<p># Comments must be prepended by the # sign! 192.168.0.0/24 ws_test_network</p>

<p>A partially matched name will be printed as &quot;subnet-name.remaining-address&quot;. For example, &quot;192.168.0.1&quot; under the subnet above would be printed as &quot;ws_test_network.1&quot;; if the mask length above had been 16 rather than 24, the printed address would be ``ws_test_network.0.1&quot;.</p>

</dd>
<dt id="Name-Resolution-ethers">Name Resolution (ethers)</dt>
<dd>

<p>The <i>ethers</i> files are consulted to correlate 6-byte hardware addresses to names. First the personal <i>ethers</i> file is tried and if an address is not found there the global <i>ethers</i> file is tried next.</p>

<p>Each line contains one hardware address and name, separated by whitespace. The digits of the hardware address are separated by colons (:), dashes (-) or periods (.). The same separator character must be used consistently in an address. The following three lines are valid lines of an <i>ethers</i> file:</p>

<pre><code>  ff:ff:ff:ff:ff:ff          Broadcast
  c0-00-ff-ff-ff-ff          TR_broadcast
  00.00.00.00.00.00          Zero_broadcast</code></pre>

<p>The global <i>ethers</i> file is looked for in the <i>/etc</i> directory on UNIX-compatible systems, and in the main installation directory (for example, <i>C:\Program Files\Wireshark</i>) on Windows systems.</p>

<p>The personal <i>ethers</i> file is looked for in the same directory as the personal preferences file.</p>

<p>Capture filter name resolution is handled by libpcap on UNIX-compatible systems and WinPcap on Windows. As such the Wireshark personal <i>ethers</i> file will not be consulted for capture filter name resolution.</p>

</dd>
<dt id="Name-Resolution-manuf">Name Resolution (manuf)</dt>
<dd>

<p>The <i>manuf</i> file is used to match the 3-byte vendor portion of a 6-byte hardware address with the manufacturer&#39;s name; it can also contain well-known MAC addresses and address ranges specified with a netmask. The format of the file is the same as the <i>ethers</i> files, except that entries of the form:</p>

<pre><code>  00:00:0C      Cisco</code></pre>

<p>can be provided, with the 3-byte OUI and the name for a vendor, and entries such as:</p>

<pre><code>  00-00-0C-07-AC/40     All-HSRP-routers</code></pre>

<p>can be specified, with a MAC address and a mask indicating how many bits of the address must match. The above entry, for example, has 40 significant bits, or 5 bytes, and would match addresses from 00-00-0C-07-AC-00 through 00-00-0C-07-AC-FF. The mask need not be a multiple of 8.</p>

<p>The <i>manuf</i> file is looked for in the same directory as the global preferences file.</p>

</dd>
<dt id="Name-Resolution-services">Name Resolution (services)</dt>
<dd>

<p>The <i>services</i> file is used to translate port numbers into names.</p>

<p>The file has the standard <i>services</i> file syntax; each line contains one (service) name and one transport identifier separated by white space. The transport identifier includes one port number and one transport protocol name (typically tcp, udp, or sctp) separated by a /.</p>

<p>An example is:</p>

<p>mydns 5045/udp # My own Domain Name Server mydns 5045/tcp # My own Domain Name Server</p>

</dd>
<dt id="Name-Resolution-ipxnets">Name Resolution (ipxnets)</dt>
<dd>

<p>The <i>ipxnets</i> files are used to correlate 4-byte IPX network numbers to names. First the global <i>ipxnets</i> file is tried and if that address is not found there the personal one is tried next.</p>

<p>The format is the same as the <i>ethers</i> file, except that each address is four bytes instead of six. Additionally, the address can be represented as a single hexadecimal number, as is more common in the IPX world, rather than four hex octets. For example, these four lines are valid lines of an <i>ipxnets</i> file:</p>

<pre><code>  C0.A8.2C.00              HR
  c0-a8-1c-00              CEO
  00:00:BE:EF              IT_Server1
  110f                     FileServer3</code></pre>

<p>The global <i>ipxnets</i> file is looked for in the <i>/etc</i> directory on UNIX-compatible systems, and in the main installation directory (for example, <i>C:\Program Files\Wireshark</i>) on Windows systems.</p>

<p>The personal <i>ipxnets</i> file is looked for in the same directory as the personal preferences file.</p>

</dd>
</dl>

<h1 id="ENVIRONMENT-VARIABLES">ENVIRONMENT VARIABLES</h1>

<dl>

<dt id="WIRESHARK_APPDATA">WIRESHARK_APPDATA</dt>
<dd>

<p>On Windows, Wireshark normally stores all application data in %APPDATA% or %USERPROFILE%. You can override the default location by exporting this environment variable to specify an alternate location.</p>

</dd>
<dt id="WIRESHARK_DEBUG_WMEM_OVERRIDE">WIRESHARK_DEBUG_WMEM_OVERRIDE</dt>
<dd>

<p>Setting this environment variable forces the wmem framework to use the specified allocator backend for *all* allocations, regardless of which backend is normally specified by the code. This is mainly useful to developers when testing or debugging. See <i>README.wmem</i> in the source distribution for details.</p>

</dd>
<dt id="WIRESHARK_RUN_FROM_BUILD_DIRECTORY">WIRESHARK_RUN_FROM_BUILD_DIRECTORY</dt>
<dd>

<p>This environment variable causes the plugins and other data files to be loaded from the build directory (where the program was compiled) rather than from the standard locations. It has no effect when the program in question is running with root (or setuid) permissions on *NIX.</p>

</dd>
<dt id="WIRESHARK_DATA_DIR">WIRESHARK_DATA_DIR</dt>
<dd>

<p>This environment variable causes the various data files to be loaded from a directory other than the standard locations. It has no effect when the program in question is running with root (or setuid) permissions on *NIX.</p>

</dd>
<dt id="ERF_RECORDS_TO_CHECK">ERF_RECORDS_TO_CHECK</dt>
<dd>

<p>This environment variable controls the number of ERF records checked when deciding if a file really is in the ERF format. Setting this environment variable a number higher than the default (20) would make false positives less likely.</p>

</dd>
<dt id="IPFIX_RECORDS_TO_CHECK">IPFIX_RECORDS_TO_CHECK</dt>
<dd>

<p>This environment variable controls the number of IPFIX records checked when deciding if a file really is in the IPFIX format. Setting this environment variable a number higher than the default (20) would make false positives less likely.</p>

</dd>
<dt id="WIRESHARK_ABORT_ON_DISSECTOR_BUG">WIRESHARK_ABORT_ON_DISSECTOR_BUG</dt>
<dd>

<p>If this environment variable is set, <b>TShark</b> will call abort(3) when a dissector bug is encountered. abort(3) will cause the program to exit abnormally; if you are running <b>TShark</b> in a debugger, it should halt in the debugger and allow inspection of the process, and, if you are not running it in a debugger, it will, on some OSes, assuming your environment is configured correctly, generate a core dump file. This can be useful to developers attempting to troubleshoot a problem with a protocol dissector.</p>

</dd>
<dt id="WIRESHARK_ABORT_ON_TOO_MANY_ITEMS">WIRESHARK_ABORT_ON_TOO_MANY_ITEMS</dt>
<dd>

<p>If this environment variable is set, <b>TShark</b> will call abort(3) if a dissector tries to add too many items to a tree (generally this is an indication of the dissector not breaking out of a loop soon enough). abort(3) will cause the program to exit abnormally; if you are running <b>TShark</b> in a debugger, it should halt in the debugger and allow inspection of the process, and, if you are not running it in a debugger, it will, on some OSes, assuming your environment is configured correctly, generate a core dump file. This can be useful to developers attempting to troubleshoot a problem with a protocol dissector.</p>

</dd>
</dl>

<h1 id="SEE-ALSO">SEE ALSO</h1>

<p>wireshark-filter(4), wireshark(1), editcap(1), pcap(3), dumpcap(1), text2pcap(1), mergecap(1), pcap-filter(7) or tcpdump(8)</p>

<h1 id="NOTES">NOTES</h1>

<p><b>TShark</b> is part of the <b>Wireshark</b> distribution. The latest version of <b>Wireshark</b> can be found at <a href="https://www.wireshark.org">https://www.wireshark.org</a>.</p>

<p>HTML versions of the Wireshark project man pages are available at: <a href="https://www.wireshark.org/docs/man-pages">https://www.wireshark.org/docs/man-pages</a>.</p>

<h1 id="AUTHORS">AUTHORS</h1>

<p><b>TShark</b> uses the same packet dissection code that <b>Wireshark</b> does, as well as using many other modules from <b>Wireshark</b>; see the list of authors in the <b>Wireshark</b> man page for a list of authors of that code.</p>


</body>

</html>