From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: david@edeca.net, netfilter@lists.netfilter.org
Subject: RE: Firewall Script Help
Date: Mon, 8 Mar 2004 20:34:16 -0800 [thread overview]
Message-ID: <200403090434.i294YHfG021288@server5.bandwidthco.com> (raw)
In-Reply-To: <200403081849.49587.lists@edeca.net>
As David said "Opinion". Not all of us believe that to be the case.
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of David Cannings
Sent: Monday, March 08, 2004 10:50 AM
To: netfilter@lists.netfilter.org
Subject: Re: Firewall Script Help
On Monday 08 March 2004 18:47, Christopher Davis wrote:
> I am trying to block incoming traffic on the INPUT chain with reserved
> ip's. I am still able to connect to the server from a reserved ip.
> Below is my entire script if someone would like to review and comment
> -- all coments welcome! This is for a webserver -- port 80 and ssh
> port 22 only. I have not yet included the logging option so those
> options are commented out at this point...
Just a quick point, it is (in my opinion at least) far easier to read your
firewall rules if they're output from iptables itself. Following through
the script is harder.
# iptables -L -v
David
next prev parent reply other threads:[~2004-03-09 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:47 Firewall Script Help Christopher Davis
2004-03-08 18:49 ` David Cannings
2004-03-08 19:19 ` Christopher Davis
2004-03-08 20:12 ` David Cannings
2004-03-08 20:32 ` Antony Stone
2004-03-09 4:34 ` Mark E. Donaldson [this message]
2004-03-08 18:51 ` Aldo S. Lagana
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 21:14 cldavis
2004-03-08 22:06 ` Antony Stone
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=200403090434.i294YHfG021288@server5.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=david@edeca.net \
--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