[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mldonkey-users] Re: Idea: limiting the port rnage mldonkey uses
From: |
Goswin Brederlow |
Subject: |
Re: [Mldonkey-users] Re: Idea: limiting the port rnage mldonkey uses |
Date: |
01 Mar 2003 08:11:30 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code) |
Nacho Ruiz <address@hidden> writes:
> Thanks for the reply Carl,
>
> On jue, 20 feb 2003, address@hidden wrote:
> > Thu, Feb 20, 2003 at 06:13:07PM +0100, Nacho Ruiz wrote:
> > > And there is any way to monitor the traffic in K/s ?
> > >
> >
> > The short answer is to use the mldonkey monitor itself.
> > It isn't entirely accurate, but it does give a feel for the raw
> > upload and download traffic.
> >
>
> which monitor? vd command?
>
> > A second way to do this (Linux) is to use iptraf. It will also
> > show miscellaneous traffic (like mldonkey queue chatter).
> >
> > A third is to count raw packets and bytes using iptables
> > chain counters. This is the technique advocated in the
> > previous email. If you send all of the edonkey traffic
> > (matched by port, or by packet owner) to a dummy iptables chain,
> > the chain will do all of the work by keeping an internal count.
> >
>
> I tried this, but the internal count isn't accumulative? I want to know
> the actual transfer rate, to pass the results to, i.e., mrtg.
Use the example scripts provided with mrtg to account iptables rules.
MfG
Goswin