Wireshark · Ethereal-dev: Re: [Ethereal-dev] Tethereal and support for pipes (windows)

["Oolan Zimmer" <ethereal@xxxxxxxx>]

> I have the same problem if I try to use named pipes (windows). I have an
app
> that creates a named pipe (\\.\pipe\foo) and writes some packets in
libpcap
> format onto it.
>
> tethereal -r \\.\pipe\foo fails telling me "The file \\.\pipe\foo doesn't
> exist".
>
> Windump works perfectly with these pipes, as well ("windump -r
> \\.\pipe\foo").
>
>
> Do you have any idea what the problem could be?

The win32 libpcap portion of wiretap explicitly checks for S_FIFO on the
filename and fails if stat turns it up.

We got around this problem by modifying libpcap/winpcap to add a "named
pipe" capture type.  Calling pcap_open or pcap_open_live on an interface
named pipe://<machinename>/<pipename> or pipe://<pipename> would get turned
into a named pipe capture on a windows machine or an offline capture on a
unix machine.

We announced that we'd completed the addition on the libpcap workers list,
but it got swept under in the effort to get the next version done.  If such
an addition will prove useful to the community, we'd be more than happy to
submit diffs;  just tell us who to send them to and which format.

Regards,
Oolan Zimmer
Gcom, Inc.
ethereal@xxxxxxxx