From: Steven M Campbell <Netfilter@SCampbell.net>
To: iptables <netfilter@lists.netfilter.org>
Subject: Re: Iptables logs on High bandwidth traffic network
Date: Wed, 04 May 2005 13:18:23 -0400 [thread overview]
Message-ID: <427903DF.5030707@SCampbell.net> (raw)
In-Reply-To: <4278C3DE.7010403@au-kbc.org>
bharathi wrote:
>Hi all,
> I am planning to implement iptables log feature on a server
>machine(Dual xeon processor,Intel e100 cards,80GB SCSI and 2GB RAM)
>which is running in bridge mode (On RH 7.3).The average traffic on this
>machine is vary from 40-60Mbps.Hence I require some suggestion for some
>my questions like,
>
>1) On this High traffic the kernel will be stable/crash ?
>2) What would be the CPU Load and the server is able to do this job
>without any pain ?
>3) Up to how much traffic the iptables/kernel can able to handle without
>any issue and what should I do additionally if I need the
> iptable-log should handle this much traffic?
>
>
>Advance thanks for your suggestion and pointers.
>
>bharthix.
>
>
>
Along with other advice offered, you may wish to take a look at argus
and ntop which are packages that collect nice summary information from
ethernet traffic. They may be appropos to your goal.
next prev parent reply other threads:[~2005-05-04 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 12:45 Iptables logs on High bandwidth traffic network bharathi
2005-05-04 15:59 ` Taylor, Grant
2005-05-04 22:40 ` Mogens Valentin
2005-05-04 23:13 ` Taylor, Grant
2005-05-05 6:59 ` Jozsef Kadlecsik
2005-05-05 7:24 ` Taylor, Grant
2005-05-05 8:15 ` Jozsef Kadlecsik
2005-05-05 11:24 ` Mogens Valentin
2005-05-05 11:59 ` Jozsef Kadlecsik
2005-05-05 9:37 ` Mogens Valentin
2005-05-05 10:07 ` Jozsef Kadlecsik
2005-05-04 16:39 ` Jason Opperisano
2005-05-04 17:18 ` Steven M Campbell [this message]
2005-05-04 20:37 ` Jozsef Kadlecsik
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=427903DF.5030707@SCampbell.net \
--to=netfilter@scampbell.net \
--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