From: "Ed Street" <blacknet@simplyaquatics.com>
To: 'Antony Stone' <Antony@Soft-Solutions.co.uk>, netfilter@lists.samba.org
Subject: RE: Most stable firewall distro
Date: Wed, 3 Jul 2002 19:06:21 -0400 [thread overview]
Message-ID: <004a01c222e6$3f032b70$0a01a8c0@ed> (raw)
In-Reply-To: <20020703223403.RTWE295.mta03-svc.ntlworld.com@there>
Hello,
The correct choice to go with would be debian. You can do a minimal
install from a business card cd and have everything you need. For those
of you that's interested contact me off list for the details and the
script/iso file (approx 41 megs)
Ed
-----Original Message-----
From: netfilter-admin@lists.samba.org
[mailto:netfilter-admin@lists.samba.org] On Behalf Of Antony Stone
Sent: Wednesday, July 03, 2002 6:34 PM
To: netfilter@lists.samba.org
Subject: Re: Most stable firewall distro
On Wednesday 03 July 2002 11:23 pm, riffraff wrote:
> ---------- Original Message ----------------------------------
> From: "Miguel Laborde" <miguel.laborde@canada.com>
> Date: Wed, 3 Jul 2002 18:22:38 -0400
>
> >Hello all,
> > I have a question here for those of you who use iptables heavily
in a
> >production environment. Right now I am about to replace a older
Mandrake
> >(release 7.2) with an updated linux firewall however before I go
ahead and
> >do that, I'm interested in knowing what you people consider the most
> > stable distribution for a linux firewall.
> > I realize that the underlying OS and iptables software is common
across
> > all distributions however some distributions apply patches which
others
> > don't, and as result might be better suitable as a firewall.
> >
> >
> > Thanks for your time,
> > Miguel
>
> I just used redhat 7.0 (I think, it's been a while), and removed
everything
> that was completely unnecessary, then compiled a whole new kernel (I
had
> to; I'm using the bridge-netfilter patch). So, it isn't much of a
redhat
> anymore, just uses redhat paths and rpm.
I agree with this approach. A firewall shouldn't really be any
recognisable
distro, because distros basically differ in all the add-ons they include
around the kernel, nearly all of which you should not have on a
firewall.
And, as suggested above, you really ought to compile your own kernel for
a
firewall, too, so it contains what you want and doesn't contain what you
don't want, therefore you start from ftp://ftp.kernel.org and 'make
config'
(or whichever variation of that you prefer).
The 'distro' I would really like to see people use for firewalls is
Linux
From Scratch, because this is expressly designed to contain only the
tools
you choose for a specific job, and not a whole bunch that someone else
thought might come in handy one day.....
Not the easiest thing to play with though, admittedly.
http://www.linuxfromscratch.org
Antony.
next prev parent reply other threads:[~2002-07-03 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 22:23 Most stable firewall distro riffraff
2002-07-03 22:34 ` Antony Stone
2002-07-03 23:06 ` Ed Street [this message]
2002-07-03 23:16 ` Steve Fink
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 1:15 George Vieira
2002-07-04 0:58 George Vieira
2002-07-04 1:06 ` Ed Street
2002-07-03 23:22 George Vieira
2002-07-04 0:56 ` leolistas
2002-07-04 12:02 ` George Georgalis
2002-07-03 22:22 Miguel Laborde
2002-07-04 0:44 ` leolistas
2002-07-04 5:37 ` Patrick Schaaf
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='004a01c222e6$3f032b70$0a01a8c0@ed' \
--to=blacknet@simplyaquatics.com \
--cc=Antony@Soft-Solutions.co.uk \
--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 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.