- Original Message
> From: Gerald Combs
> To: tcpdump-workers@lists.tcpdump.org
> Cc: Rob Hasselbaum
> Sent: Tue, October 5, 2010 8:14:57 PM
> Subject: Re: [tcpdump-workers] bandwidth by user or process id
>
> You can also catch events using SystemTap's netdev.transmit and
> netdev.re
- Original Message
> From: Phil Vandry
> To: Rob Hasselbaum
> Cc: tcpdump-workers@lists.tcpdump.org
> Sent: Tue, October 5, 2010 7:53:16 PM
> Subject: Re: [tcpdump-workers] bandwidth by user or process id
>
> On Mon, 4 Oct 2010 09:51:39 -0400 Rob Hasselbaum wrote:
> > Yes, it is pos
- Original Message
> From: Rob Hasselbaum
> To: tcpdump-workers@lists.tcpdump.org
> Sent: Tue, October 5, 2010 4:07:14 PM
> Subject: Re: [tcpdump-workers] bandwidth by user or process id
>
> Right, generally, the local or remote port will be different for different
> PIDs even if the I
From: Rob Hasselbaum
To: tcpdump-workers@lists.tcpdump.org
Sent: Mon, October 4, 2010 10:35:02 PM
Subject: Re: [tcpdump-workers] bandwidth by user or process id
>For typical point-to-point IP traffic, the combination of local address,
>local port, remote addr
ndwidth by user or process id
On Mon, Oct 4, 2010 at 8:49 AM, Patrick Kurz wrote:
> Dear all,
> I am looking for a solution to monitor bandwidth usage
> a) broken up by source and destination ip address
> b) broken up by either user or process (pid) which is causing the bandwidth
>
&
Dear all,
I am looking for a solution to monitor bandwidth usage
a) broken up by source and destination ip address
b) broken up by either user or process (pid) which is causing the bandwidth
I have found out how to solve a) with the pcap library.
Is it also possible to solve b) using pcap or othe
