From: James Marcinek <jmarc1@jemconsult.biz>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: 2 basic iptables questions
Date: Tue, 25 Jul 2006 17:55:34 -0400 [thread overview]
Message-ID: <44C69356.5000602@jemconsult.biz> (raw)
In-Reply-To: <20060725212039.59780.qmail@web60024.mail.yahoo.com>
Peter,
Here's my take on it:
1) The /etc/sysconfig/iptables file is where your rules are contained
(once you build them). I myself write a shell script that contains my
rules, then run the script which builds them. I then do a service
iptables save command, which will save the rules currently in
/etc/sysconfig/iptables. I believe a backup of
/etc/sysconfig/iptables.save is also created.
Peter wrote:
> Hi,
>
> Two questions:
>
> 1) I understand the basics of the iptables command but I am having
> trouble grasping how the various "scripts" go together. I have a
> CentOS (Red Hat) box set up and there is an init script
> /etc/init.d/iptables. There is also a support script
> /etc/sysconfig/iptables-config. I know also that 'service iptables
> save' saves a ruleset file of the current ruleset inside
> /etc/sysconfig/iptables. My question is therefore "Where do I place my
> main (and documented) ruleset file?". I envision a file solely
> containing a multitude of iptables commands but many files I find on
> the net contain other commands as well.
>
> 2) I have inherited an iptables firewall and I'm trying to grok its
> ruleset. Here are the beginning lines of the output of 'cat
> /etc/sysconfig/iptables':
>
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> :log_and_drop - [0:0]
> :service_chain - [0:0]
> [0:0] -A INPUT -d 127.0.0.1 -j ACCEPT
> [0:0] -A INPUT -s 127.0.0.1 -j ACCEPT
> [0:0] -A INPUT -i lo -j ACCEPT
> [0:0] -A INPUT -j service_chain
> [0:0] -A log_and_drop -j LOG --log-prefix "FWSERVER (Blocked
> Connection)"
> [0:0] -A log_and_drop -j REJECT --reject-with icmp-port-unreachable
> [0:0] -A service_chain -p icmp -j ACCEPT
> [0:0] -A service_chain -p icmp -j log_and_drop
> .
> .
> .
> { many more '[0:0] -A service_chain' lines }
> COMMIT
>
> My question here is how is the last rule ever matched? If ICMP is seen
> it will be accepted and the evaluation stops. What is the meaning of
> this line? My guess is that it is there to log and then block unwanted
> traffic (via the log_and_drop chain) but I do not see how it works.
> The ruleset is full of these line patterns.
I can't help you here. I would actually like to know more about the
logging; however your guess looks correct. The one rule looks like it
would be evaluated first then accepted. Unless the logging facility has
special workings...
I typically drop everything, then open what I want. Since ICMP is
dropped, do you really need to monitor it?
>
> Peter
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
next prev parent reply other threads:[~2006-07-25 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 21:20 2 basic iptables questions Peter
2006-07-25 21:55 ` James Marcinek [this message]
2006-07-25 22:08 ` Gary W. Smith
2006-07-25 21:59 ` Gary W. Smith
2006-07-25 22:09 ` Peter
2006-07-26 19:03 ` Martijn Lievaart
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=44C69356.5000602@jemconsult.biz \
--to=jmarc1@jemconsult.biz \
--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