-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
>
> Would a patch to move the capture syntax into its own manpage and into
> the libpcap package be acceptable? If so, I'm willing to produce one.
>
> ciao
>Joerg
>
I agree. I am developing an application that uses libpcap and It
didn't make an
On Wed, May 02, 2007 at 10:53:02AM -0700, Guy Harris wrote:
> However, I'm not sure the libpcap man page is the right place, either,
> as it'll be lost amidst a bunch of details of interest only to people
> writing code that uses libpcap.
pcap-filter(4) will be it for the start then.
ciao
Jo
Joerg Mayer wrote:
Well, it's not a bug per se, but I really think that the capture syntax
manpage should be part of libpcap and not of tcpdump. I know of a few
systems that have wireshark installed but not tcpdump. Also, it is
possible to build tcpdump with older versions of libpcap where the
c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "Joerg" == Joerg Mayer <[EMAIL PROTECTED]> writes:
Joerg> Well, it's not a bug per se, but I really think that the
Joerg> capture syntax manpage should be part of libpcap and not of
Joerg> tcpdump. I know of a few systems that have w
>From a thread at wireshark-users, but this concerns libpcap.
On Tue, May 01, 2007 at 11:38:26PM -0700, Guy Harris wrote:
> Does it count as a bug if it's documented to work that way? :-)
>
> To quote the OS X 10.4.9 tcpdump man page (this isn't WinPcap-specific -
> it's common to all libpcap/Wi
