Wireshark can sniff named pipes, as described in this article :
Before pipes, Wireshark could read the captured packets to display
either from a file (which had been previously created) or for a
network interface (in real time). Since pipes are supported, Wireshark
can also read packets from another application, and shows them in real
There are some limitations that you should be aware of:
- This only works with the de facto standard libpcap format version 2.4, as described in Development/LibpcapFileFormat. Some other formats may work in theory, but this has not been tested.
- Capturing from a pipe is inconvenient, because you have to set up the pipe and put a file header into the pipe before you can start the
capture. A few patches have been mailed to the development list that
could solve this, so if you find the approach inconvenient, try the
- The named pipe is not listed in the drop-down interface selection, and must be typed into the interface box. On Windows, it must be typed
slowly (or pasted).
After trying it out, or finding out which are the mentioned patches, or getting in touch with the author of the above article, there is still left the problem of knowing the name of the pipe, which is miraculously solved (again) by the sysinternals utility PipeList :
What you might also find surprising is that it's possible to obtain a
directory listing of the named pipes defined on a system. This fact is
not documented, nor is it possible to do this using the Win32 API.
Another solution might be the commercial product I/O Ninja ($30, trial available).