From: "Pete Davis" <peted@springisd.org>
To: "netfilter@lists.netfilter.org", netfilter@lists.netfilter.org, ,
Subject: Connection or process limit
Date: Fri, 11 Oct 2002 14:24:45 -0500 [thread overview]
Message-ID: <sda6df30.020@hiway.springisd.org> (raw)
I am trying to find out the capacity of my iptables firewall. Is there
a limit for the state table in terms of connections it can track? How
about a Linux limit on processes, etc.? We have a DS3 at 15mb/s and I
want to make sure my box can handle it before I continue on my project.
Currently, I have a 500mhz Intel box with 256mb of memory and
server-class Intel 10/100 NICs. It seems this should be able to handle
it if I tweak the kernel configs properly.
This box is going to be acting more as a screening router than a
firewall (it is a bridging + iptables firewall... no IP on the box).
The rule set will be minimal as I just want to screen out obvious bad
traffic from getting to the network OUTSIDE my firewall (from the
internet). The main firewall does a great job for the internal stuff
but I want to help the external stuff as much as possible without
interfering with legitimate traffic.
Any comments, helpful hints, words of experience...?
reply other threads:[~2002-10-11 19:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sda6df30.020@hiway.springisd.org \
--to=peted@springisd.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.