 | 1 | initial version |
If you mean "find all the {TCP,UDP,SCTP?} ports that are open on the machine running Wireshark", no, Wireshark has no mechanism to do that. On UN*Xes, netstat -a will produce output from which you can determine what ports are open - you might have output that looks something like
tcp4 0 0 *.666 *.* LISTEN
tcp6 0 0 *.666 *.* LISTEN
indicating that the machine has TCP port 666 open for both IPv4 and IPv6 or
udp6 0 0 *.666 *.*
udp4 0 0 *.666 *.*
indicating that the machine has UDP port 666 open for both IPv4 and IPv6.
If you mean "find all the {TCP,UDP,SCTP?} ports that are open a machine other than the machine running Wireshark", no, Wireshark has no mechanism to do that; that requires actively probing the other machine, and Wireshark is just a passive sniffer. Nmap is one tool that can be used for this purpose.
If you mean "find all the ports that Wireshark itself is holding open", no, Wireshark has no mechanism to report that.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.