Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "bino-psn" <bino@indoakses-online.com>
To: netfilter@lists.netfilter.org
Subject: Re: per-connection byte counts
Date: Mon, 19 Jan 2004 07:50:54 +0700	[thread overview]
Message-ID: <002001c3de26$4b970da0$0300a8c0@indoaksesbno> (raw)
In-Reply-To: 200401190031.50360.Antony@Soft-Solutions.co.uk

----- Original Message -----
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Monday, January 19, 2004 7:31 AM
Subject: Re: per-connection byte counts


> If this package provides the information you need, why not just run it on
the
> netfilter machine?   What's the need for a separate box?

No problem Sir.
I just want to split the Monitoring-function from the Packet-Forwarding
function.
I just don't want a fail of one function savere the other.
I never mix complex function in a single box, unless they need tobe.
my small corporate network is build from a bunch of used classic pentium
class PC, with small RAM .. and WISP-Dist in it.
Let's say that the network is in a peak state ... super high traffic. It
will eat more CPU of the monitoring function. I don't want this to kick-down
the packet-forward function. That why I put it in another box.

Sincerely
-bino-



  reply	other threads:[~2004-01-19  0:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-18 14:09 per-connection byte counts Adam Rice
2004-01-18 14:44 ` [despammed] " Andreas Kretschmer
2004-01-18 15:07   ` Antony Stone
2004-01-18 20:16 ` Carlos Carvalho
2004-01-19  0:14   ` bino-psn
2004-01-19  0:31     ` Antony Stone
2004-01-19  0:50       ` bino-psn [this message]
2004-01-19 23:59         ` Ted Kaczmarek
2004-01-19 14:27 ` Nuno Miguel Pais Fernandes
2004-01-20 22:12   ` Adam Rice
2004-01-27  1:56     ` Harald Welte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002001c3de26$4b970da0$0300a8c0@indoaksesbno' \
    --to=bino@indoakses-online.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox