- Original Message -
From: "Harley Stenzel" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 06, 2006 12:25 PM
Subject: Re: [tcpdump-workers] Headroom
On 10/6/06, Gianluca Varenni <[EMAIL PROTECTED]> wrote:
Uhm, what's the purpose of some amount of memory put in front of the
pcap_t
s
[Attempting to confuse dup message detection]
On 10/6/06, Gianluca Varenni <[EMAIL PROTECTED]> wrote:
Uhm, what's the purpose of some amount of memory put in front of the pcap_t
structure?
Maybe I don't understand your proposal completely...
I don't want the data in front of the pcap_t struct
On 10/6/06, Gianluca Varenni <[EMAIL PROTECTED]> wrote:
Uhm, what's the purpose of some amount of memory put in front of the pcap_t
structure?
Maybe I don't understand your proposal completely...
I don't want the data in front of the pcap_t structure, I want it in
front of the body of the pack
- Original Message -
From: "Harley Stenzel" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 06, 2006 10:46 AM
Subject: [tcpdump-workers] Headroom
Greetings--
Has the idea of headroom for libpcap-based stack applications been
discussed before? The idea is to have a known amount of empt
I want to monitor a Gigabit Multimode(SX) Fiber link. If use a Network
Tap then:
- Using one SX NIC: Can Libpcap capture packets from TX and RX NIC's
connector?
- Have I to use 2 different NICs to connect the fibers to the RX
connectors and don't use the TX ones? ¿Configuring the N
Greetings--
Has the idea of headroom for libpcap-based stack applications been
discussed before? The idea is to have a known amount of empty/usable
space in front of the buffer given to the application by the
pcap_dispatch callback, pcap_next(), or pcap_next_ex().
It looks like it'd be a ((pcap
