Since I'm unfortunate enough to be on a bandwidth cap I like to monitor
where my bandwidth is going so I can shut down anything that's guzzling
loads of bandwidth. I do this through simple IPTABLES rules, as it
gives a nice breakdown of what's using what.
Unfortunately, as freenet just claims
Hi,
I like to monitor
where my bandwidth is going... I do this through
simple
IPTABLES rules,
One way to do this might be to run freenet under its
own user account (I tweaked the start-freenet.sh
script to su to user freenet when starting the node)
and use iptables' owner match support to
The Freenet I'm running on my Windows machine says it is version 00.5.2.8
(March 14, 2004). How does build 5078 compare with that?
thanks
-Original Message-
From: Toad [mailto:[EMAIL PROTECTED]
Sent: Monday, May 03, 2004 4:30 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:
On Fri, 30 Apr 2004 23:34:08 +1000, Cameron GArnham wrote:
Heare is a dump of the freenet dir:
:
-rw-r--r--1 garnham garnham 5715853312 Apr 30 23:17 freenet.log
:
System:
OS debian testing
currently the log is 5.7GB there MUST be a cap!.
Please have a look at logrotate
On Wed, 05 May 2004 00:00:40 +1200, Phillip Hutchings wrote:
Since I'm unfortunate enough to be on a bandwidth cap I like to monitor
where my bandwidth is going so I can shut down anything that's guzzling
loads of bandwidth. I do this through simple IPTABLES rules, as it
gives a nice
On 5/05/2004, at 6:56 AM, Ole Tange wrote:
On Wed, 05 May 2004 00:00:40 +1200, Phillip Hutchings wrote:
Since I'm unfortunate enough to be on a bandwidth cap I like to
monitor
where my bandwidth is going so I can shut down anything that's
guzzling
loads of bandwidth. I do this through simple
Hi,
On Tuesday 04 May 2004 06:33, Paul Schauble wrote:
The Freenet I'm running on my Windows machine says it is version 00.5.2.8
(March 14, 2004). How does build 5078 compare with that?
Open the fproxy start page and see what build it says at the top. You'll need
to upgrade to 5078 because
I checked on that before posting to the list, and the module is only
valid in the OUTPUT chain. Since Freenet sends data both ways it's not
much use for this.
I use this -m owner match, it works well and is sufficient. There is no
point in limiting the input rate (well, at least in most
