[TriLUG] IPTables throughput limitations?
rvestal at trilug.org
Thu Apr 22 08:54:32 EDT 2004
Don't know if this helps, but...
The TriLUG firewall used at meetings used to be a pentium 90, 40MB RAM, 2GB
HDD, 2 10Mb PCMCIA NICS running Debian stable with iptables as the masq
firewall. I also had Squid proxy on it and DHCPD. Before the PCMCIA slots
died, we would have anywhere from 30-70 folks on it, depending on the
meeting, and the notebook handled it fine. Logs showed very little cpu
utilization, very few collisions, etc.
We used it at InstallFests for FTP installs as well as outside traffic. No
Alas, she burned herself up (PCMCIA slots) and has been retired. <*sniff*>
We beat the crap out of it and right up to it's retirement, it worked fine.
So my thought? Works fine. :)
Side Note - the first firewall I was involved with was a pentium 233MMX
desktop, 64MB RAM, 2GB HDD, 2 10Mb 3Com NICs running RedHat 6.2, ipchains,
and pmfirewall. Worked fine too. (still in my office at work!)
----- Original Message -----
From: "Jeff Bollinger" <jeff01 at email.unc.edu>
To: <trilug at trilug.org>
Sent: Wednesday, April 21, 2004 9:08 AM
Subject: [TriLUG] IPTables throughput limitations?
> I have found a few threads online about this, but can anyone speak to
> the throughput limitations of an IPTables firewall/router (i.e., linux
> box + iptables + 2 NICs)? I know it depends on the strength of the
> hardware and the complexity of the rulesets, but what are some of the
> larger throughputs you've seen pass through a strictly IPTables firewall?
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
More information about the TriLUG