neulab/tldr huggingface dataset:
read_format:file_format tells TShark to use the given file format to read in the file (the file given in the -r command option). Providing no file_format argument, or an invalid one, will produce a file of available file formats to use.
-y|--linktype  <capture link type>
Set the data link type to use while capturing packets. The values reported by -L are the values that can be used.
This option can occur multiple times. If used before the first occurrence of the -i option, it sets the default capture link type. If used after an -i option, it sets the capture link type for the interface specified by the last -i option occurring before this option. If the capture link type is not set specifically, the default capture link type is used if provided.
-Y|--display-filter  <displaY filter>
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.
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.
-M  <auto session reset>
Automatically reset internal session when reached to specified number of packets. for example,
tshark -M 100000
will reset session every 100000 packets.
This feature does not support -2 two-pass analysis
-z  <statistics>
Get TShark to collect various types of statistics and display the result after finishing reading the capture file. Use the -q option if you’re reading a capture file and only want the statistics printed, not any per-packet information.
Note that the -z proto option is different - it doesn’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 -q option, as that option would suppress the printing of the regular packet summary output, and must also not use the -V option, as that would cause packet detail information rather than packet summary information to be printed.
Some of the currently implemented statistics are:
-z help
Display all possible values for -z.
-z afp,srt[,filter]
Show Apple Filing Protocol service response time statistics.
-z camel,srt
-z conv,type[,filter]
Create a table that lists all conversations that could be seen in the capture. type specifies the conversation endpoint types for which we want to generate the statistics; currently the supported ones are:
"bluetooth"  Bluetooth addresses "eth"   Ethernet addresses "fc"    Fibre Channel addresses "fddi"  FDDI addresses "ip"    IPv4 addresses "ipv6"  IPv6 addresses "ipx"   IPX addresses "jxta"  JXTA message addresses "ncp"   NCP connections "rsvp"  RSVP connections "sctp"  SCTP addresses "tcp"   TCP/IP socket pairs  Both IPv4 and IPv6 are supported "tr"    Token Ring addresses "usb"   USB addresses "udp"   UDP/IP socket pairs  Both IPv4 and IPv6 are supported "wlan"  IEEE 802.11 addresses
If the optional filter is specified, only those packets that match the filter will be used in the calculations.
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.
-z dcerpc,srt,uuid,major.minor[,filter]
Collect call/reply SRT (Service Response Time) data for DCERPC interface uuid, version major.minor. Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
Example: -z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0 will collect data for the CIFS SAMR Interface.
This option can be used multiple times on the command line.
If the optional filter is provided, the stats will only be calculated on those calls that match that filter.
Example: -z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4 will collect SAMR SRT statistics for a specific host.
-z dhcp,stat[,filter]
Show DHCP (BOOTP) statistics.
-z diameter,avp[,cmd.code,field,field,...]
This option enables extraction of most important diameter fields from large capture files. Exactly one text line for each diameter message with matched diameter.cmd.code will be printed.
Empty diameter command code or '' can be specified to mach any *diameter.cmd.code
Example: -z diameter,avp  extract default field set from diameter messages.
Example: -z diameter,avp,280  extract default field set from diameter DWR messages.
Example: -z diameter,avp,272  extract default field set from diameter CC messages.
Extract most important fields from diameter CC messages:
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
Following fields will be printed out for each diameter message:
"frame"        Frame number. "time"         Unix time of the frame arrival. "src"          Source address. "srcport"      Source port. "dst"          Destination address. "dstport"      Destination port. "proto"        Constant string 'diameter', which can be used for post processing of tshark output. E.g. grep/sed/awk. "msgnr"        seq. number of diameter message within the frame. E.g. '2' for the third diameter message in the same frame. "is_request"   '0' if message is a request, '1' if message is an answer. "cmd"          diameter.cmd_code, E.g. '272' for credit control messages. "req_frame"    Number of frame where matched request was found or '0'. "ans_frame"    Number of frame where matched answer was found or '0'. "resp_time"    response time in seconds, '0' in case if matched Request/Answer is not found in trace. E.g. in the begin or end of capture.
-z diameter,avp option is much faster than -V -T text or -T pdml options.
-z diameter,avp option is more powerful than -T field and -z proto,colinfo options.
Multiple diameter messages in one frame are supported.
Several fields with same name within one diameter message are supported, e.g. diameter.Subscription-Id-Data or diameter.Rating-Group.
Note: tshark -q option is recommended to suppress default TShark output.
-z dns,tree[,filter]
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.
-z endpoints,type[,filter]
Create a table that lists all endpoints that could be seen in the capture. type specifies the endpoint types for which we want to generate the statistics; currently the supported ones are:
-z expert[,error|,warn|,note|,chat|,comment][,filter]
Collects information about all expert info, and will display them in order, grouped by severity.
Example: -z expert,sip will show expert items of all severity for frames that match the sip protocol.
Example: -z "expert,note,tcp" will only collect expert items for frames that include the tcp protocol, with a severity of note or higher.
-z flow,name,mode,[filter]
Displays the flow of data between two nodes. Output is the same as ASCII format saved from GUI.
name specifies the flow name. It can be one of:
any      All frames icmp     ICMP icmpv6   ICMPv6 lbm_uim  UIM tcp      TCP
mode specifies the address type. It can be one of:
standard   Any address network    Network address
Example: -z flow,tcp,network will show data flow for all TCP frames
-z follow,prot,mode,filter[,range]
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.
prot specifies the transport protocol. It can be one of:
tcp   TCP udp   UDP tls   TLS or SSL http2 HTTP/2 streams quic  QUIC streams
mode specifies the output mode. It can be one of:
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 yaml   YAML format
Since the output in ascii or ebcdic mode may contain newlines, the length of each section of output plus a newline precedes each section of output.
filter specifies the stream to be displayed. UDP/TCP streams are selected with either the stream index or IP address plus port pairs. TLS streams are selected with the stream index. HTTP/2 streams are selected by combination of UDP/TCP and HTTP/2 streams indices. For example:
ip-addr0:port0,ip-addr1:port1 stream-index stream-index,substream-index
range optionally specifies which "chunks" of the stream should be displayed.
Example: -z "follow,tcp,hex,1" will display the contents of the second TCP stream (the first is stream 0) in "hex" format.
=================================================================== 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  ...".... ........ 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
Example: -z "follow,tcp,ascii,200.57.7.197:32891,200.57.7.198:2906" will display the contents of a TCP stream between 200.57.7.197 port 32891 and 200.57.7.98 port 2906.
=================================================================== Follow: tcp,ascii Filter: (omitted for readability) Node 0: 200.57.7.197:32891 Node 1: 200.57.7.198:2906 38 ..."..... ................ 4 ....
Example: -z "follow,http2,hex,0,1" will display the contents of a HTTP/2 stream on the first TCP session (index 0) with HTTP/2 Stream ID 1.
=================================================================== Follow: http2,hex Filter: tcp.stream eq 0 and http2.streamid eq 1 Node 0: 172.16.5.1:49178 Node 1: 172.16.5.10:8443 00000000  00 00 2c 01 05 00 00 00  01 82 04 8b 63 c1 ac 2a  ..,..... ....c..* 00000010  27 1d 9d 57 ae a9 bf 87  41 8c 0b a2 5c 2e 2e da  '..W.... A...\... 00000020  e1 05 c7 9a 69 9f 7a 88  25 b6 50 c3 ab b6 25 c3  ....i.z. %.P...%. 00000030  53 03 2a 2f 2a                                    S.*/* 00000000  00 00 22 01 04 00 00 00  01 88 5f 87 35 23 98 ac  .."..... .._.5#.. 00000010  57 54 df 61 96 c3 61 be  94 03 8a 61 2c 6a 08 2f  WT.a..a. ...a,j./ 00000020  34 a0 5b b8 21 5c 0b ea  62 d1 bf                 4.[.!\.. b.. 0000002B  00 40 00 00 00 00 00 00  01 89 50 4e 47 0d 0a 1a  .@...... ..PNG...
QUIC streams can be selected through -z "follow,quic,hex,3,0", the first number indicates the QUIC connection number whereas the second number selects the QUIC Stream ID.
-z h225,counter[,filter]
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.
Example: -z h225,counter.
If the optional filter is provided, the stats will only be calculated on those calls that match that filter. Example: use -z "h225,counter,ip.addr==1.2.3.4" to only collect stats for H.225 packets exchanged by the host at IP address 1.2.3.4 .
-z h225,srt[,filter]
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.
Example: tshark -z h225,srt
Example: -z "h225,srt,ip.addr==1.2.3.4" will only collect stats for ITU-T H.225 RAS packets exchanged by the host at IP address 1.2.3.4 .
-z hosts[,ip][,ipv4][,ipv6]
Dump any collected IPv4 and/or IPv6 addresses in "hosts" format. Both IPv4 and IPv6 addresses are dumped by default. "ip" argument will dump only ipv4 addresses.
Addresses are collected from a number of sources, including standard "hosts" files and captured traffic.
-z hpfeeds,tree[,filter]
Calculate statistics for HPFEEDS traffic such as publish per channel, and opcode distribution.
-z http,stat,
Calculate the HTTP statistics distribution. Displayed values are the HTTP status codes and the HTTP request methods.
-z http,tree
Calculate the HTTP packet distribution. Displayed values are the HTTP request modes and the HTTP status codes.
-z http_ref,tree
Calculate the HTTP requests by referer. Displayed values are the referring URI.
-z http_req,tree
Calculate the HTTP requests by server. Displayed values are the server name and the URI path.
-z http_srv,tree
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.
-z icmp,srt[,filter]
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.
Example: -z icmp,srt,ip.src==1.2.3.4 will collect ICMP SRT statistics for ICMP echo request packets originating from a specific host.
-z icmpv6,srt[,filter]
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.
Example: -z icmpv6,srt,ipv6.src==fe80::1 will collect ICMPv6 SRT statistics for ICMPv6 echo request packets originating from a specific host.
-z io,phs[,filter]
Create Protocol Hierarchy Statistics listing both number of packets and bytes. If no filter is specified the statistics will be calculated for all packets. If a filter is specified statistics will only be calculated for those packets that match the filter.
-z io,stat,interval[,filter][,filter][,filter]...
Collect packet/bytes statistics for the capture in intervals of interval seconds. Interval can be specified either as a whole or fractional second and can be specified with microsecond (us) resolution. If interval is 0, the statistics will be calculated over all packets.
If no filter is specified the statistics will be calculated for all packets. If one or more filters are specified statistics will be calculated for all filters and presented with one column of statistics for each filter.
Example: -z io,stat,1,ip.addr==1.2.3.4 will generate 1 second statistics for all traffic to/from host 1.2.3.4.
Example: -z "io,stat,0.001,smb&&ip.addr==1.2.3.4" will generate 1ms statistics for all SMB packets to/from host 1.2.3.4.
The examples above all use the standard syntax for generating statistics which only calculates the number of packets and bytes in each interval.
io,stat can also do much more statistics and calculate COUNT(), SUM(), MIN(), MAX(), AVG() and LOAD() using a slightly different filter syntax:
-z io,stat,interval,"COUNT|SUM|MIN|MAX|AVG|LOAD(field)filter"
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.
So: -z io,stat,0.010,AVG(smb.time) does not work. Use -z io,stat,0.010,AVG(smb.time)smb.time 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.
Note A second important thing to note is that the system setting for decimal separator must be set to "."! If it is set to "," the statistics will not be displayed per filter.
COUNT - Calculates the number of times that the field name (not its value) appears per interval in the filtered packet list. ''field'' can be any display filter name.
Example: -z io,stat,0.010,"COUNT(smb.sid)smb.sid"
This will count the total number of SIDs seen in each 10ms interval.
SUM - Unlike COUNT, the values of the specified field are summed per time interval. ''field'' can only be a named integer, float, double or relative time field.
Example: tshark -z io,stat,0.010,"SUM(frame.len)frame.len"
Reports the total number of bytes that were transmitted bidirectionally in all the packets within a 10 millisecond interval.
MIN/MAX/AVG - 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.
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, ''^'' is used, each line cannot end in a comma so it is placed at the beginning of each continuation line:
tshark -o tcp.desegment_tcp_streams:FALSE -n -q -r smb_reads.cap -z io,stat,0, "MIN(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==0", "MAX(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==1", "MIN(smb.time)smb.time and smb.cmd==0x2e", "MAX(smb.time)smb.time and smb.cmd==0x2e", "AVG(smb.time)smb.time and smb.cmd==0x2e"
====================================================================================================== 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 ======================================================================================================
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:
tshark -n -q -r smb_reads_writes.cap -z io,stat,0, "AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to", "SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to", "AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to", "SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to"
===================================================================================== 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 =====================================================================================
LOAD - 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.
The following command displays the average SMB LOAD. A value of 1.0 represents one I/O in flight.
tshark -n -q -r smb_reads_writes.cap -z "io,stat,0.001,LOAD(smb.time)smb.time"
============================================================================ 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
FRAMES | BYTES[()filter] - Displays the total number of frames or bytes. The filter field is optional but if included it must be prepended with ''()''.
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.
tshark -o tcp.desegment_tcp_streams:FALSE -n -q -r smb_reads.cap -z io,stat,0,,FRAMES,BYTES, "FRAMES()smb.cmd==0x2e and smb.response_to","BYTES()ip.dst==10.1.0.64"
======================================================================================================================= 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 =======================================================================================================================
-z mac-lte,stat[,filter]
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.
Example: tshark -z mac-lte,stat.
If the optional filter is provided, the stats will only be calculated for those frames that match that filter. Example: -z "mac-lte,stat,mac-lte.rnti>3000" will only collect stats for UEs with an assigned RNTI whose value is more than 3000.
-z megaco,rtd[,filter]
Collect requests/response RTD (Response Time Delay) data for MEGACO. (This is similar to -z smb,srt). 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’t match with any request. Example: -z megaco,rtd.
If the optional filter is provided, the stats will only be calculated on those calls that match that filter. Example: -z "megaco,rtd,ip.addr==1.2.3.4" will only collect stats for MEGACO packets exchanged by the host at IP address 1.2.3.4 .
-z mgcp,rtd[,filter]
Collect requests/response RTD (Response Time Delay) data for MGCP. (This is similar to -z smb,srt). 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’t match with any request. Example: -z mgcp,rtd.
If the optional filter is provided, the stats will only be calculated on those calls that match that filter. Example: -z "mgcp,rtd,ip.addr==1.2.3.4" will only collect stats for MGCP packets exchanged by the host at IP address 1.2.3.4 .
-z credentials
Collect credentials (username/passwords) from packets. The report includes the packet number, the protocol that had that credential, the username and the password. For protocols just using one single field as authentication, this is provided as a password and a placeholder in place of the user.
-z proto,colinfo,filter,field
Append all field 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. field is the display-filter name of a field which value should be placed in the Info column. filter is a filter string that controls for which packets the field value will be presented in the info column. field will only be presented in the Info column for the packets which match filter.
Note In order for TShark to be able to extract the field value from the packet, field MUST be part of the filter string. If not, TShark will not be able to extract its value.
For a simple example to add the "nfs.fh.hash" field to the Info column for all packets containing the "nfs.fh.hash" field, use
-z proto,colinfo,nfs.fh.hash,nfs.fh.hash
To put "nfs.fh.hash" in the Info column but only for packets coming from host 1.2.3.4 use:
-z "proto,colinfo,nfs.fh.hash && ip.src==1.2.3.4,nfs.fh.hash"
-z rlc-lte,stat[,filter]
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.
Example: tshark -z rlc-lte,stat.
If the optional filter is provided, the stats will only be calculated for those frames that match that filter. Example: -z "rlc-lte,stat,rlc-lte.ueid>3000" will only collect stats for UEs with a UEId of more than 3000.
-z rpc,programs
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.
-z rpc,srt,program,version[,filter]
Collect call/reply SRT (Service Response Time) data for program/version. Data collected is the number of calls for each procedure, MinSRT, MaxSRT, AvgSRT, and the total time taken for each procedure.
Example: tshark -z rpc,srt,100003,3 will collect data for NFS v3.
Example: -z rpc,srt,100003,3,nfs.fh.hash==0x12345678 will collect NFS v3 SRT statistics for a specific file.
-z rtp,streams
Collect statistics for all RTP streams and calculate max. delta, max. and mean jitter and packet loss percentages.
-z scsi,srt,cmdset[,filter]
Collect call/reply SRT (Service Response Time) data for SCSI commandset cmdset.
Commandsets are 0:SBC   1:SSC  5:MMC
Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
Example: -z scsi,srt,0 will collect data for SCSI BLOCK COMMANDS (SBC).
Example: -z scsi,srt,0,ip.addr==1.2.3.4 will collect SCSI SBC SRT statistics for a specific iscsi/ifcp/fcip host.
-z sip,stat[,filter]
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).
Example: -z sip,stat.
If the optional filter is provided, the stats will only be calculated on those calls that match that filter. Example: -z "sip,stat,ip.addr==1.2.3.4" will only collect stats for SIP packets exchanged by the host at IP address 1.2.3.4 .
-z smb,sids
When this feature is used TShark 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.
For this feature to work you will need to either to enable "Edit/Preferences/Protocols/SMB/Snoop SID to name mappings" in the preferences or you can override the preferences by specifying -o "smb.sid_name_snooping:TRUE" on the TShark command line.
The current method used by TShark to find the SID→name mapping is relatively restricted with a hope of future expansion.
-z smb,srt[,filter]
Collect call/reply SRT (Service Response Time) data for SMB. Data collected is number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
Example: -z smb,srt
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.
Example: -z "smb,srt,ip.addr==1.2.3.4" will only collect stats for SMB packets exchanged by the host at IP address 1.2.3.4 .
--capture-comment <comment>
Add a capture comment to the output file, if supported by the output file format.
This option may be specified multiple times. Note that Wireshark currently only displays the first comment of a capture file.
--list-time-stamp-types
List time stamp types supported for the interface. If no time stamp type can be set, no time stamp types are listed.
--time-stamp-type <type>
Change the interface’s timestamp method.
--color
Enable coloring of packets according to standard Wireshark color filters. On Windows colors are limited to the standard console character attribute colors. Other platforms require a terminal that handles 24-bit "true color" terminal escape sequences. See https://gitlab.com/wireshark/wireshark/-/wikis/ColoringRules for more information on configuring color filters.
--no-duplicate-keys
If a key appears multiple times in an object, only write it a single time with as value a json array containing all the separate values. (Only works with -T json)
--elastic-mapping-filter <protocol>,<protocol>,...
When generating the ElasticSearch mapping file, only put the specified protocols in it, to avoid a huge mapping file that can choke some software (such as Kibana). The option takes a list of wanted protocol abbreviations, separated by comma.
Example: ip,udp,dns puts only those three protocols in the mapping file.
--export-objects <protocol>,<destdir>
Export all objects within a protocol into directory destdir. The available values for protocol can be listed with --export-objects help.
The objects are directly saved in the given directory. Filenames are dependent on the dissector, but typically it is named after the basename of a file. Duplicate files are not overwritten, instead an increasing number is appended before the file extension.
This interface is subject to change, adding the possibility to filter on files.
--enable-protocol <proto_name>
Enable dissection of proto_name.
--disable-protocol <proto_name>
Disable dissection of proto_name.
--enable-heuristic <short_name>
Enable dissection of heuristic protocol.
--disable-heuristic <short_name>
Disable dissection of heuristic protocol.
See the manual page of pcap-filter(7) or, if that doesn’t exist, tcpdump(8), or, if that doesn’t exist, https://gitlab.com/wireshark/wireshark/-/wikis/CaptureFilters.
For a complete table of protocol and protocol fields that are filterable in TShark see the wireshark-filter(4) manual page.
These files contains various Wireshark configuration values.
The preferences 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 -o is used (possibly more than once), it will in turn override values from the preferences files.
The preferences settings are in the form prefname:value, one per line, where prefname is the name of the preference and value is the value to which it should be set; white space is allowed between : and value. A preference setting can be continued on subsequent lines by indenting the continuation lines with white space. A # character starts a comment that runs to the end of the line:
# Capture in promiscuous mode? # TRUE or FALSE (case-insensitive). capture.prom_mode: TRUE
The global preferences file is looked for in the wireshark directory under the share subdirectory of the main installation directory (for example, /usr/local/share/wireshark/preferences) on UNIX-compatible systems, and in the main installation directory (for example, C:\Program Files\Wireshark\preferences) on Windows systems.
The personal preferences file is looked for in $XDG_CONFIG_HOME/wireshark/preferences (or, if $XDG_CONFIG_HOME/wireshark does not exist while $HOME/.wireshark is present, $HOME/.wireshark/preferences) on UNIX-compatible systems and %APPDATA%\Wireshark\preferences (or, if %APPDATA% isn’t defined, %USERPROFILE%\Application Data\Wireshark\preferences) on Windows systems.
Disabled (Enabled) Protocols
The disabled_protos 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:
http tcp     # a comment
The global disabled_protos file uses the same directory as the global preferences file.
The personal disabled_protos file uses the same directory as the personal preferences file.
Name Resolution (hosts)
If the personal hosts 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 hosts file syntax; each line contains one IP address and name, separated by whitespace. The same directory as for the personal preferences file is used.
Capture filter name resolution is handled by libpcap on UNIX-compatible systems and Npcap or WinPcap on Windows. As such the Wireshark personal hosts file will not be consulted for capture filter name resolution.
Name Resolution (subnets)
If an IPv4 address cannot be translated via name resolution (no exact match is found) then a partial match is attempted via the subnets file.
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.
# Comments must be prepended by the # sign! 192.168.0.0/24 ws_test_network
A partially matched name will be printed as "subnet-name.remaining-address". For example, "192.168.0.1" under the subnet above would be printed as "ws_test_network.1"; if the mask length above had been 16 rather than 24, the printed address would be ``ws_test_network.0.1".
Name Resolution (ethers)
The ethers files are consulted to correlate 6-byte hardware addresses to names. First the personal ethers file is tried and if an address is not found there the global ethers file is tried next.
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 ethers file:
ff:ff:ff:ff:ff:ff          Broadcast c0-00-ff-ff-ff-ff          TR_broadcast 00.00.00.00.00.00          Zero_broadcast
The global ethers file is looked for in the /etc directory on UNIX-compatible systems, and in the main installation directory (for example, C:\Program Files\Wireshark) on Windows systems.
The personal ethers file is looked for in the same directory as the personal preferences file.
Capture filter name resolution is handled by libpcap on UNIX-compatible systems and Npcap or WinPcap on Windows. As such the Wireshark personal ethers file will not be consulted for capture filter name resolution.
Name Resolution (manuf)
The manuf file is used to match the 3-byte vendor portion of a 6-byte hardware address with the manufacturer’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 ethers files, except that entries of the form:
00:00:0C      Cisco
can be provided, with the 3-byte OUI and the name for a vendor, and entries such as:
00-00-0C-07-AC/40     All-HSRP-routers
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.
The manuf file is looked for in the same directory as the global preferences file.
Name Resolution (services)
The services file is used to translate port numbers into names.
The file has the standard services 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 /.
mydns       5045/udp     # My own Domain Name Server mydns       5045/tcp     # My own Domain Name Server
Name Resolution (ipxnets)
The ipxnets files are used to correlate 4-byte IPX network numbers to names. First the global ipxnets file is tried and if that address is not found there the personal one is tried next.
The format is the same as the ethers 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 ipxnets file:
C0.A8.2C.00              HR c0-a8-1c-00              CEO 00:00:BE:EF              IT_Server1 110f                     FileServer3
The global ipxnets file is looked for in the /etc directory on UNIX-compatible systems, and in the main installation directory (for example, C:\Program Files\Wireshark) on Windows systems.
The personal ipxnets file is looked for in the same directory as the personal preferences file.
TShark uses UTF-8 to represent strings internally. In some cases the output might not be valid. For example, a dissector might generate invalid UTF-8 character sequences. Programs reading TShark output should expect UTF-8 and be prepared for invalid output.
If TShark detects that it is writing to a TTY on UNIX or Linux and the locale does not support UTF-8, output will be re-encoded to match the current locale.
If TShark detects that it is writing to the console on Windows, dissection output will be encoded as UTF-16LE. Other output will be UTF-8. If extended characters don’t display properly in your terminal you might try setting your console code page to UTF-8 (chcp 65001) and using a modern terminal application if possible.
WIRESHARK_CONFIG_DIR
This environment variable overrides the location of personal configuration files. It defaults to $XDG_CONFIG_HOME/wireshark (or $HOME/.wireshark if the former is missing while the latter exists). On Windows, %APPDATA%\Wireshark is used instead. Available since Wireshark 3.0.
WIRESHARK_DEBUG_WMEM_OVERRIDE
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 README.wmem in the source distribution for details.
WIRESHARK_RUN_FROM_BUILD_DIRECTORY
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.
WIRESHARK_DATA_DIR
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.
ERF_RECORDS_TO_CHECK
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.
IPFIX_RECORDS_TO_CHECK
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.
WIRESHARK_ABORT_ON_DISSECTOR_BUG
If this environment variable is set, TShark will call abort(3) when a dissector bug is encountered. abort(3) will cause the program to exit abnormally; if you are running TShark 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.
WIRESHARK_ABORT_ON_TOO_MANY_ITEMS
If this environment variable is set, TShark 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 TShark 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.
WIRESHARK_LOG_LEVEL
This environment variable controls the verbosity of diagnostic messages to the console. From less verbose to most verbose levels can be critical, warning, message, info, debug or noisy. Levels above the current level are also active. Levels critical and error are always active.
WIRESHARK_LOG_FATAL
Sets the fatal log level. Fatal log levels cause the program to abort. This level can be set to Error, critical or warning. Error is always fatal and is the default.
WIRESHARK_LOG_DOMAINS
This environment variable selects which log domains are active. The filter is given as a case-insensitive comma separated list. If set only the included domains will be enabled. The default domain is always considered to be enabled. Domain filter lists can be preceded by '!' to invert the sense of the match.
WIRESHARK_LOG_DEBUG
List of domains with debug log level. This sets the level of the provided log domains and takes precedence over the active domains filter. If preceded by '!' this disables the debug level instead.
WIRESHARK_LOG_NOISY
Same as above but for noisy log level instead.
wireshark-filter(4), wireshark(1), editcap(1), pcap(3), dumpcap(1), text2pcap(1), mergecap(1), pcap-filter(7) or tcpdump(8)
This is the manual page for TShark 3.6.0. TShark is part of the Wireshark distribution. The latest version of Wireshark can be found at https://www.wireshark.org.
HTML versions of the Wireshark project man pages are available at https://www.wireshark.org/docs/man-pages.
TShark uses the same packet dissection code that Wireshark does, as well as using many other modules from Wireshark; see the list of authors in the Wireshark man page for a list of authors of that code.
CHROMA(1)                                                              CHROMA(1)
chroma - general purpose syntax highlighting program
chroma [options] files ...
This manual page documents briefly the chroma command.
–help  Show context-sensitive help.
–list  List lexers, styles and formatters.
–unbuffered Do not buffer output.
–trace Trace lexer states as they are traversed.
–check Do not format, check for tokenization errors instead.
–filename=FILENAME Filename to use for selecting a lexer when reading from stdin.
-l, –lexer=autodetect Lexer to use when formatting.
-s, –style=swapoff Style to use for formatting.
-f, –formatter=terminal Formatter to use.
–html  Enable HTML mode (equivalent to `–formatter html').
–html-prefix=PREFIX HTML CSS class prefix.
–html-styles Output HTML CSS styles.
–html-only Output HTML fragment.
–html-inline-styles Output HTML with inline styles (no classes).
–html-tab-width=8 Set the HTML tab width.
–html-lines Include line numbers in output.
–html-lines-table Split line numbers and code in a HTML table
–html-lines-style=HTML-LINES-STYLE Style for line numbers.
–html-highlight=N[:M][,...] Highlight these lines.
–html-highlight-style=HTML-HIGHLIGHT-STYLE Style used for highlighting lines.
–html-base-line=1 Base line number.
–version Show application version.
See GitHub Issues: <https://github.com/alecthomas/chroma/issues>
GIT-ROOT(1)                        Git Extras                        GIT-ROOT(1)
git-root - show path of root
git root OPTIONS
print the path for the root directory of git repo
-r, --relative
show the relative path from root directory to current directory
$ cd .../git-extras/bin $ git root -r bin/ $ git root /home/.../git-extras $ cd `git root` $ pwd /home/.../git-extras # then we can $ git add . && git commit
Written by spacewander <spacewanderlzx@gmail.com>
ESPEAK(1)                    General Commands Manual                   ESPEAK(1)
espeak - A multi-lingual software speech synthesizer.
espeak [options] [<words>]
espeak is a software speech synthesizer for English, and some other languages.
-h     Show summary of options.
--version Prints the espeak library version and the location of the espeak voice data.
-f <text file> Text file to speak
--stdin Read text input from stdin instead of a file
If neither -f nor --stdin, <words> are spoken, or if none then text is spoken from stdin, each line separately.
-q     Quiet, don't produce any speech (may be useful with -x)
-a <integer> Amplitude, 0 to 200, default is 100
-g <integer> Word gap. Pause between words, units of 10mS at the default speed
-k <integer> Indicate capital letters with: 1=sound, 2=the word "capitals", higher values = a pitch increase (try -k20).
-l <integer> Line length. If not zero (which is the default), consider lines less than this length as and-of-clause
-p <integer> Pitch adjustment, 0 to 99, default is 50
-s <integer> Speed in words per minute, default is 160
-v <voice name> Use voice file of this name from espeak-data/voices
-w <wave file name> Write output to this WAV file, rather than speaking it directly
-b     Input text encoding, 1=UTF8, 2=8 bit, 4=16 bit
-m     Indicates that the text contains SSML (Speech Synthesis Markup Language) tags or other XML tags. Those SSML tags which are supported are interpreted. Other tags, including HTML, are ignored, except that some HTML tags such as <hr> <h2> and <li> ensure a break in the speech.
-x     Write phoneme mnemonics to stdout
-X     Write phonemes mnemonics and translation trace to stdout. If rules files have been built with --compile=debug, line numbers will also be displayed.
-z     No final sentence pause at the end of the text
--stdout Write speech output to stdout
--compile=voicename Compile the pronunciation rules and dictionary in the current directory. =<voice name> is optional and specifies which language
--compile=debug Compile the pronunciation rules and dictionary in the current directory as above, but include line numbers, that get shown when -X is used.
--ipa  Write phonemes to stdout using International Phonetic Alphabet. --ipa=1 Use ties, --ipa=2 Use ZWJ, --ipa=3 Separate with _
--path=<path> Specifies the directory containing the espeak-data directory
--pho  Write mbrola phoneme data (.pho) to stdout or to the file in --phonout
--phonout=<filename> Write output from -x -X commands and mbrola phoneme data to this file
--punct="<characters>" Speak the names of punctuation characters during speaking. If =<characters> is omitted, all punctuation is spoken.
--voices[=<language code>] Lists the available voices. If =<language code> is present then only those voices which are suitable for that language are listed.
--voices=<directory> lists the voices in the specified subdirectory.
eSpeak was written by Jonathan Duddington <jonsd@jsd.clara.co.uk>. The webpage for this package can be found at http://espeak.sourceforge.net/.
This manual page was written by Luke Yelavich <themuso@ubuntu.com>, for the Ubuntu project (but may be used by others).
MMLS(1)                      General Commands Manual                     MMLS(1)
mmls - Display the partition layout of a volume system  (partition tables)
mmls [-t mmtype ] [-o offset ] [ -i imgtype ] [-b dev_sector_size] [-BrvV] [-aAmM] image [images]
mmls displays the layout of the partitions in a volume system, which include partition tables and disk labels.
-t mmtype Specify the media management type.  Use '-t list' to list the supported types.  If not given, autodetection methods are used.
-o offset Specify the offset into the image where the volume containing the partition system starts.  The relative offset of the partition system will be added to this value.
-b dev_sector_size The size, in bytes, of the underlying device sectors.  If not given, the value in the image format is used (if it exists) or 512-bytes is assumed.