I created a pipe "\.\pipe\wireshark" with VB.net and tried to add and open it in Wireshark, but get "The capture session on "\.pipe\wireshark"could not be started due to error on pipe open: The system cannot find the file specified. (error 2). I've test the pipe with command line pipe tool(NamedPipeClient.exe) and VB.net pipe client tool I created, and "\.\pipe\wireshark" pipe can be connected and works fine with both tools. Why Wireshark 2.0.1 cannot open a named pipe? Thanks, Josh asked 11 Jan '16, 17:20  josh117 |
One Answer:
I figured it out. Wireshark 2.0.1 is fine. I should use NamedPipeServerStream("wireshark", PipeDirection.Out) instead of NamedPipeServerStream("\\.\pipe\wireshark", PipeDirection.Out) in my code. answered 12 Jan '16, 10:15 josh117 edited 12 Jan '16, 10:17 |
Are you sure that it is a specific issue of 2.0.1 or you simply haven't tried with any other Wireshark version? Because I have tested it (but not with VB!) with other versions of Wireshark before and it worked, and Wireshark's extcap mechanism also relies on named pipes, so it should work.
What method exactly have you used to tell Wireshark that it should read from the named pipe?