Guy,
you were 100% right.
I think the routine usb_cleanup_linux_mmap(pcap_t* handle) should be
modified as follows:
diff --git a/pcap-usb-linux.c b/pcap-usb-linux.c
index 3d7cb2c..9ad8953 100644
--- a/pcap-usb-linux.c
+++ b/pcap-usb-linux.c
@@ -835,6 +835,9 @@ usb_cleanup_linux_mmap(pcap_t* h
On Jul 10, 2009, at 3:35 PM, Gianluca Varenni wrote:
I just discovered an interesting leak with the libpcap 1.0 or the
current top-of-tree.
On Fedora 10, kernel 2.6.27.5 or 2.6.27.12, there is a memory leak
by which a simple program like this one will eventually use all the
memory on the
Hi all.
I just discovered an interesting leak with the libpcap 1.0 or the current
top-of-tree.
On Fedora 10, kernel 2.6.27.5 or 2.6.27.12, there is a memory leak by which
a simple program like this one will eventually use all the memory on the
system (as reported by top) and eventually the a
pcap_next() and pcap_next_ex() rely on the packet data pointer handed
to their pcap_dispatch() callback still pointing to the same packet
data after the callback returns.
If the packet data is being read into a buffer with read()/getmsg()/
recvfrom()/etc., that works.
If, however, the pack
On Jul 10, 2009, at 2:16 AM, Varjonen Samu wrote:
diff -N -r -u --strip-trailing-cr tcpdump-orig/configure.in tcpdump/
configure.in
--- tcpdump-orig/configure.in 2009-05-20 11:29:46.0 +0300
+++ tcpdump/configure.in2009-05-17 13:13:13.0 +0300
@@ -158,7 +158,7 @@
--di
On Jul 10, 2009, at 2:16 AM, Varjonen Samu wrote:
+/* supports only hex print, modified from print_int64 in print-
nfs.c */
+static void
+hip_print_int64_hex (const u_int32_t *dp, int hostorder)
+{
+#ifdef INT64_FORMAT
+u_int64_t res;
+
+ if (hostorder)
+ res = ((u_
Hi,
Here is a patch providing the dissection of HIP control packets for Tcpdump.
Host Identity Protocol (HIP) allows consenting hosts to securely
establish and maintain shared IP-layer state, allowing separation of the
identifier and locator roles of IP addresses, thereby enabling
continuity
On Fri, Jul 10, 2009 at 07:48:05PM +0200, ml ml wrote:
> Hello List,
>
> i would like to capture traffic with tcpdump and analyze them
> afterwards. I am especially intrested what eats up my bandwith. Are
> there some tools that can analyze my dump like this?
>
Load it into wireshark and graph b
Hello List,
i would like to capture traffic with tcpdump and analyze them
afterwards. I am especially intrested what eats up my bandwith. Are
there some tools that can analyze my dump like this?
Cheers,
Mario
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
