On Tuesday, February 14, 2012 9:17 PM, Michael Richardson wrote:
>
>That's a significant jump in functionality.
>I don't think 2.4 had any memory mapped functionality at all.
>
>If 2.6.18 has any (redhat likes to backport all sorts of things), the
>question becomes... does it work? 2.6.18 is 5 y
andelman.ca [mailto:m...@sandelman.ca]
Sent: Tuesday, February 14, 2012 3:57 PM
To: tcpdump-workers@lists.tcpdump.org
Cc: Moshe Matitya
Subject: Re: [tcpdump-workers] libpcap causing segmentation fault
Whose libpcap 1.2.1 are you using?
I assume that it is one that you built. On RHEL 3.8 were you using
On Tuesday, February 14, 2012 3:40 PM, ri...@happyleptic.org wrote:
>
>Calling pcap_loop() after it returned something else than 0?
No, pcap_loop() is called only once.
Moshe
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
We are running an application using libpcap 1.2.1, on CentOS 5.6 (64-bit), on a
machine with a 10 gigabit NIC. We have been using this application for several
years, using previous versions of libpcap, previous versions of Linux, and
other NIC's, without any problems. Also, the current version
