Revision history [back]
Wireshark could capture named pipe traffic between two Windows systems by sniffing on the network between the systems (with the usual issues if it's a switched Ethernet or if it's a Wi-Fi network; network named pipe traffic would appear as SMB traffic.
Wireshark can't capture named pipe traffic between two processes on the same machine. It sounds as if IO Ninja might be able to do that. It looks as if the GitHub project also can intercept named pipe traffic between two processes on a given machine (perhaps by overriding Windows API calls to write to the named pipe with calls that write to the named pipe and provide a copy on the other named pipe) and feed that to Wireshark, over another pipe, as fake TCP (or UDP?) packets.
Wireshark could capture named pipe traffic between two Windows systems by sniffing on the network between the systems (with the usual issues if it's a switched Ethernet or if it's a Wi-Fi network; network named pipe traffic would appear as SMB traffic.
Wireshark can't capture named pipe traffic between two processes on the same machine. It sounds as if IO Ninja might be able to do that. It looks as if the GitHub project also can intercept named pipe traffic between two processes on a given machine (perhaps by overriding Windows API calls to write to the named pipe with calls that write to the named pipe and provide a copy on the other named pipe) and feed that to Wireshark, over another pipe, as fake TCP (or UDP?) packets.that.