> Speaking of radio headers for 802.11 and link[M:N], I'm not sure a
> filter that tests those is necessarily useful - should the link[M:N]
> filters just test the 802.11 header and payload, and skip radio headers
> for the Prism, AVS, and radiotap headers? That way the same link[M:N]
> filter
-BEGIN PGP SIGNED MESSAGE-
> "Guy" == Guy Harris <[EMAIL PROTECTED]> writes:
Guy> Michael Richardson wrote:
>> I would like to plan a 3.9 branch and release for April. I would
>> propose branching on April 10, with the release around April 25.
>> How does that sound?
-BEGIN PGP SIGNED MESSAGE-
> "Guy" == Guy Harris <[EMAIL PROTECTED]> writes:
>> I'd like to make sure that libpcap 0.9.1-096 compiles on NetBSD
>> 1.6. It appears that the test for fddipad says
>> defined(__NetBSD__), but that member must have been introduced in
>> a
-BEGIN PGP SIGNED MESSAGE-
> "GSE" == GSE GCSM writes:
GSE> I'm finalizing a small patch to pcap-dlpi.c for HP-UX systems
GSE> and I have two questions:
GSE> 1) What is the preferred format for patches?
unidiff.
GSE> 2) The main website says 0.9.0 went alpha toda
Michael Richardson wrote:
I would like to plan a 3.9 branch and release for April.
I would propose branching on April 10, with the release around April 25.
How does that sound?
It sounds reasonable.
(It turns out I might be able to get gencode.c to handle radiotap -
*all* filter expressions other
Brown, Mark C (GSE GCSM) wrote:
I'm finalizing a small patch to pcap-dlpi.c for HP-UX systems and I have
two questions:
1) What is the preferred format for patches?
Context or unified diff, probably.
2) The main website says 0.9.0 went alpha today (the link to the source
is broken btw). What is th
Michael Richardson wrote:
I'd like to make sure that libpcap 0.9.1-096 compiles on NetBSD 1.6.
It appears that the test for fddipad says defined(__NetBSD__),
but that member must have been introduced in a post-1.6 version of
NetBSD.
Actually, the problem appears to be that PCAP_FDDIPAD is defined i
Greetings,
I'm finalizing a small patch to pcap-dlpi.c for HP-UX systems and I have
two questions:
1) What is the preferred format for patches?
2) The main website says 0.9.0 went alpha today (the link to the source
is broken btw). What is the normal delay before formal release?
Thanks!
Rega
-BEGIN PGP SIGNED MESSAGE-
I'd like to make sure that libpcap 0.9.1-096 compiles on NetBSD 1.6.
It appears that the test for fddipad says defined(__NetBSD__),
but that member must have been introduced in a post-1.6 version of
NetBSD.
Can we fix this to depend upon a NetBSD version macro
gilbert HOYEK wrote:
2-in pcap-linux.c only pcap-open-live and pcap-platform-finddevs contains
#ifdef HAVE_DAG_API . so do i have to make similar code (#if def
HAVE_SEPTEL_API ...) to only these two funtions in pcap-linux.c ?
Yes.
3- pcap-linux.c contains #include pcap-int.h with contains at
On Tue, Apr 05, 2005 at 10:36:59AM -0700, Shyam Kumar wrote:
|
| [1] Data Representation is handled by tcpdump code only or both by
| tcpdump code & libpcap code??
if by data-representation you mean dissecting protocols then this
is done by tcpdump;
| [2] which *.c & *.h files deals with data r
1-Exactly Mr Harris , i'm having my capture on a Linux based machine
... so if you can give some more info i would be gratefull .
if you dont mind i would like to get answers for the following :
2-in pcap-linux.c only pcap-open-live and pcap-platform-finddevs contains
#ifdef HAVE_DAG_API . so
12 matches
Mail list logo
