Re: [tcpdump-workers] Windows Named Pipes as capture interfaces

2005-05-17 Thread Gcom, Inc.
At 02:31 AM 5/17/2005, you wrote: Gcom, Inc. wrote: We are considering adding support in libpcap to use a windows named pipe as a capture interface. The other end of the windows named pipe would present a libpcap file-format stream of data, so relatively little would need to be done in libpcap

Re: [tcpdump-workers] preperation for 3.9 branch

2005-05-17 Thread Hannes Gredler
On Mon, May 16, 2005 at 11:20:20AM -0700, Guy Harris wrote: | Gianluca Varenni wrote: | | >Is there any new plan for the release of libpcap 0.9? | | At this point, I don't have anything additional planned for tcpdump | (other than perhaps grabbing some more capture files from the Ethereal | Web

Re: [tcpdump-workers] Windows Named Pipes as capture interfaces

2005-05-17 Thread mcr
-BEGIN PGP SIGNED MESSAGE- > "Gcom," == Gcom, Inc <[EMAIL PROTECTED]> writes: Gcom> We are considering adding support in libpcap to use a windows Gcom> named pipe as a capture interface. The other end of the Gcom> windows named pipe would present a libpcap file-format str

Re: [tcpdump-workers] Windows Named Pipes as capture interfaces

2005-05-17 Thread Guy Harris
Gcom, Inc. wrote: We are considering adding support in libpcap to use a windows named pipe as a capture interface. The other end of the windows named pipe would present a libpcap file-format stream of data, so relatively little would need to be done in libpcap to make this work. If we were to