Wireshark mailing list archives
Re: Rev 38350 Capture Options Changes - Named Pipe?
From: "Colin O'Flynn" <coflynn () newae com>
Date: Wed, 10 Aug 2011 18:31:39 -0300
Maybe an button which will add a named pipe to the list of interfaces.
If this added the pipe to a preference file that would be even better, as it would persist between Wireshark sessions. It might help pipes feel more loved, and not like a hack added on. Regards, -Colin -----Original Message----- From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Michael Tüxen Sent: August 10, 2011 5:50 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe? On Aug 10, 2011, at 10:44 PM, Guy Harris wrote:
On Aug 10, 2011, at 1:33 PM, Michael Tüxen wrote:Use the command line options... There is currently no way to specify a
named
pipe in the GUI. I think there was no way to do this in Wireshark 1.6, or am I missing something?The general convention in Wireshark-the-project (i.e., Wireshark, TShark,
and dumpcap) is that if the "network interface" you specify isn't a network interface (i.e., an attempt to open it with libpcap fails), and it's a named pipe, it's opened as a pipe connected to a program writing a pcap (or pcap-ng?) capture file.
I.e., in the GUI, you'd specify it by, for example, giving "/tmp/pipe" (or
whatever the named pipe path is) as the name of the "network interface" from which to capture in the Capture Options dialog. Hi Guy, I was aware of this in the context of the -i arguments, but not that it could be specified in the GUI. We need to find a way to do this. Maybe an button which will add a named pipe to the list of interfaces. I'll talk to Irene when she's available again to bring back the capability to specify named pipes in the GUI. Best regards Michael
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Rev 38350 Capture Options Changes - Named Pipe?, (continued)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Jakub Zawadzki (Aug 10)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Joerg Mayer (Aug 10)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Michael Tüxen (Aug 11)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Joerg Mayer (Aug 11)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Michael Tüxen (Aug 11)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Guy Harris (Aug 11)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Michael Tüxen (Aug 11)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Joerg Mayer (Aug 12)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Guy Harris (Aug 12)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Michael Tüxen (Aug 11)
- Re: Rev 38350 Capture Options Changes - Named Pipe? Colin O'Flynn (Aug 10)