osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

TShark, Wireshark: add some more documentation of "-i TCP@<host>:<port>". 

Add a mention of the meaning of the "TCP@<host>:<port>" syntax in the
text about the -i option.
This commit is contained in:
Guy Harris 2022-01-31 21:31:48 -08:00
parent dc16d91c37
commit 08dc06027f
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/tshark.adoc
View File

@ -599,6 +599,9 @@ of the form "\\pipe\.\*pipename*". Data read from pipes must be in
standard pcapng or pcap format. Pcapng data must have the same
endianness as the capturing host.
"TCP@<host>:<port>" causes *TShark* to attempt to connect to the
specified port on the specified host and read pcapng or pcap data.
This option can occur multiple times. When capturing from multiple
interfaces, the capture file will be saved in pcapng format.
--

5
doc/wireshark.adoc
View File

@ -406,7 +406,7 @@ Network interface names should match one of the names listed in
"*wireshark -D*" (described above); a number, as reported by
"*wireshark -D*", can also be used. If you're using UNIX, "*netstat
-i*", "*ifconfig -a*" or "*ip link*" might also work to list interface names,
although not all versions of UNIX support the *-a* flag to *ifconfig*.
although not all versions of UNIX support the *-a* option to *ifconfig*.
If no interface is specified, *Wireshark* searches the list of
interfaces, choosing the first non-loopback interface if there are any
@ -420,6 +420,9 @@ of the form "\\pipe\.\*pipename*". Data read from pipes must be in
standard pcapng or pcap format. Pcapng data must have the same
endianness as the capturing host.
"TCP@<host>:<port>" causes *Wireshark* to attempt to connect to the
specified port on the specified host and read pcapng or pcap data.
This option can occur multiple times. When capturing from multiple
interfaces, the capture file will be saved in pcapng format.
--