From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Maxium concurrent connections with IPTables
Date: Mon, 2 Aug 2004 20:01:49 +0100 [thread overview]
Message-ID: <200408022001.49637.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <564DE4477544D411AD2C00508BDF0B6A22073275@usahm018.exmi01.exch.eds.com>
On Monday 02 August 2004 7:15 pm, Small, Jim wrote:
> I'm curious, what is the maximum number of concurrent connections possible
> with IPTables using connection tracking for udp and for tcp? (using latest
> 2.4 kernel and 2.6 kernel)
Depends on the amount of memory in your machine, and the setting of
/proc/sys/net/ipv4/ip_conntrack/max
Each connection uses about 300 bytes (see output of dmesg for the exact size
for your particular system), therefore a system with 1Gbyte RAM could support
about 3.5 million connections.
> I'm currently taking a Cisco firewall class and they're claiming that PIX
> which supports 500,000 concurrent connections with the appliance version
> and 1,000,000 with the blade version vastly exceeds the capabilities of all
> general purpose O/S'.
I've never tested a fierwall with >256Mbytes RAM, and I'd be hard pushed to
think of a way to effectively test >1 million connections too (sure, you
could use a Windows machine infected with a worm, but that would test
half-open connections with nothing on the other end, not real connections
passing data).
Regards,
Antony.
--
90% of networking problems are routing problems.
9 of the remaining 10% are routing problems in the other direction.
The remaining 1% might be something else, but check the routing anyway.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-08-02 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 18:15 Maxium concurrent connections with IPTables Small, Jim
2004-08-02 19:01 ` Antony Stone [this message]
2004-08-02 19:14 ` Antony Stone
2004-08-03 7:46 ` 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=200408022001.49637.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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