From: Sandy Harris <sandy@storm.ca>
To: netfilter@lists.samba.org
Subject: Re: Lowest spec processor that netfilter will run on
Date: Thu, 06 Jun 2002 23:11:20 -0700 [thread overview]
Message-ID: <3D004E88.3760FABE@storm.ca> (raw)
In-Reply-To: 001201c20dd0$314a3260$020aa8c0@matttm9svd8lrh
Matthew Hellman wrote:
>
> I can't speak for non x86 processors, but I have mine running on a Pentium
> 60 mhz with 64MB ram....runs pretty well although I personally wouldn't
> consider going with anything less.
I ran a firewall for a year or two using a 486/66
with 24 megs, using ipchains, on a 2.2 Mbps ADSL
link. The only problem was keeping log size under
control on a 170 meg drive.
There are some numbers for related things at:
http://www.freeswan.org/freeswan_snaps/NEW-SNAP/doc/performance.html
next prev parent reply other threads:[~2002-06-07 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 23:47 Lowest spec processor that netfilter will run on John Crowhurst
2002-06-07 3:05 ` Matthew Hellman
2002-06-07 6:11 ` Sandy Harris [this message]
2002-06-07 3:45 ` Matthew Hellman
2002-06-07 4:42 ` George Georgalis
2002-06-07 7:05 ` Stewart Thompson
2002-06-07 17:38 ` Stuart W. Card
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=3D004E88.3760FABE@storm.ca \
--to=sandy@storm.ca \
--cc=netfilter@lists.samba.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