From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: user defined chains
Date: Mon, 12 Jul 2004 20:55:15 +0100 [thread overview]
Message-ID: <200407122055.15961.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <f51b72bc040712114970f47399@mail.gmail.com>
On Monday 12 July 2004 7:49 pm, Payal Rathod wrote:
> Hi,
> If I want to design a firewall for a network on a high end machine
> with lot of RAM and swap, is there any real use of user defined
> chains? I find them difficult so I would like to use only the built-in
> chains. Is that ok?
Yes.
Antony.
(Okay, for a fuller answer, use user-defined chains if you want to, don't use
them if you prefer - it makes no difference to netfilter so long as you can
understand the rules enough to get them to do what you want them to.)
--
Users don't know what they want until they see what they get.
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-07-12 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 18:49 user defined chains Payal Rathod
2004-07-12 19:51 ` John A. Sullivan III
2004-07-12 20:02 ` Antony Stone
2004-07-12 19:55 ` Antony Stone [this message]
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=200407122055.15961.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