Commit Graph

20 Commits

Author SHA1 Message Date
dmiller 6e868eba03 Upgrade libpcap to 1.10.7 2026-09-17 16:36:26 +00:00
dmiller 20c3b3b945 Update libpcap to 1.10.6 2026-01-27 21:01:16 +00:00
dmiller aed27d094e Update libpcap to 1.10.5 2025-04-14 19:06:54 +00:00
dmiller 585832c41e Upgrade libpcap to 1.10.4 2023-04-28 14:37:51 +00:00
dmiller 65410fead1 Update included libpcap to 1.10.1 2022-08-31 18:39:55 +00:00
dmiller f1107301e8 Update to libpcap 1.9.1 (initial commit, no Nmap-specific patches) 2019-11-19 17:53:36 +00:00
dmiller a2442ea29f Update libpcap to 1.9.0 (no patches applied yet) 2019-03-30 03:24:44 +00:00
dmiller 3fc4a6fc95 Upgrade libpcap to 1.8.1 (Nmap-specific patches not yet applied) 2018-07-18 13:41:35 +00:00
dmiller 83b9c4c939 Disable TPACKET_V3 in included libpcap. Still broken, see #34 2015-09-15 13:31:21 +00:00
dmiller 4bbef7d69b Update libpcap to 1.7.3, partially addressing #34 2015-05-01 20:24:47 +00:00
jay d8071c0352 Updated the included libpcap to 1.5.3 2014-06-06 10:43:17 +00:00
david 5d24d23600 Update libpcap to 1.2.1. 2012-04-10 00:47:45 +00:00
luis faaca263b9 When using pcap_set_filter() on Linux, valgrind complains about a
setsockopt() call that uses a pointer to some uninitialized memory. The
error message is the following:

==22214== Syscall param socketcall.setsockopt(optval) points to
uninitialised byte(s)
==22214==    at 0x62F774A: setsockopt (syscall-template.S:82)
==22214==    by 0x4E33B85: ??? (in /usr/lib/libpcap.so.1.0.0)
==22214==    by 0x4E33D0D: ??? (in /usr/lib/libpcap.so.1.0.0)
==22214==    by 0x432253: nsock_pcap_set_filter (in /usr/local/bin/nping)
==22214==    by 0x432557: nsock_pcap_open (in /usr/local/bin/nping)
==22214==    by 0x4295FF: ProbeMode::start() (in /usr/local/bin/nping)
==22214==    by 0x40B2E1: main (in /usr/local/bin/nping)

This patch adds a simple memset() call that makes the warning dissapear.
2010-09-22 09:41:06 +00:00
david 38019ded5c o [libpcap] Added a --disable-packet-ring option to force the use of
an older, slower packet capture mechanism on Linux. Before Linux
  2.6.27, the packet ring mechanism uses different-sized kernel
  structures on 32- and 64-bit architectures, so a 32-bit program will
  not run correctly on a 64-bit kernel. The older mechanism does not
  have this flaw.
2010-05-26 20:43:09 +00:00
david 4ac98563ab Upgrade our included libpcap to 1.1.1. 2010-04-21 04:39:45 +00:00
david 9a1ec98da3 Upgrade libpcap to version 1.0.0. 2009-10-27 19:33:50 +00:00
kris c12c9871e8 Upgrading shipped libpcap from 0.9.4 to 0.9.7. Includes CHANGELOG entry 2007-08-26 00:01:14 +00:00
fyodor 5a978df29b almost done upgrading to libpcap 0.9.4 2006-08-16 22:42:58 +00:00
fyodor d9281c5d1b removed libpcap dir 2006-08-16 20:31:13 +00:00
fyodor df0dd19d10 removed conflicting libpcap spec file, really ready for 3.91 release I hope 2005-09-11 11:21:38 +00:00