From: Mike Wright <mike.wright@mailinator.com>
To: netfilter@vger.kernel.org
Subject: Re: Verify rules
Date: Thu, 26 Mar 2009 16:35:37 -0700 [thread overview]
Message-ID: <49CC1149.3020604@mailinator.com> (raw)
In-Reply-To: <0d6001c9ae55$10b9e040$322da0c0$@net>
Scott Miller wrote:
> I was wondering if I could get someone to verify my rules. What I am trying
> to do to start with, is make only certain ports available on my outgoing
> mail server - essentially blocking all other ports not listed. I have the
> below on my server in an inactive state because when I activate it, it locks
> it completely down.
>
> Could someone please take a look at my rules and share with me what I did
> wrong? Here is my entire config file:
>
>
> -----------------------------
>
> *mangle
> :PREROUTING ACCEPT [6:948]
> :INPUT ACCEPT [6:948]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [7:3269]
> :POSTROUTING ACCEPT [7:3269]
> COMMIT
> *nat
> :OUTPUT ACCEPT [0:0]
> :PREROUTING ACCEPT [0:0]
> :POSTROUTING ACCEPT [0:0]
> COMMIT
> *filter
> :FORWARD ACCEPT [0:0]
> :INPUT ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> # HTTP
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 80 --state NEW -j
> ACCEPT
> # SSH
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 22 --state NEW -j
> ACCEPT
> # DNS
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 53 --state NEW -j
> ACCEPT
> # TIME
> -A INPUT -p udp -m udp -m state NEW,ESTABLISHED --dport 123 --state NEW -j
> ACCEPT
> # WEBMIN
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 10000 --state NEW -j
> ACCEPT
> # SMTP
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 25 --state NEW -j
> ACCEPT
> # POP3
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 110 --state NEW -j
> ACCEPT
> # IMAP
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 993 --state NEW -j
> ACCEPT
> # RSYNC-TCP
> -A INPUT -p tcp -m tcp -m state NEW,ESTABLISHED --dport 873 --state NEW -j
> ACCEPT
> # RSYNC-UDP
> -A INPUT -p udp -m udp -m state NEW,ESTABLISHED --dport 873 --state NEW -j
> ACCEPT
> # DENY ALL OTHERS
> -A INPUT -i eth0 -j REJECT --reject-with icmp-net-unreachable
> COMMIT
>
> --------------------------
Hi Scott,
No expert here but I'll give this a try. This is very basic but
hopefully may provide some ideas.
You say you want to run a server so that means you should lock down
everything you specifically don't want to serve. That's accomplished by
setting the INPUT chain's default policy to DROP.
#> iptables -P INPUT DROP
Let the network gossip
#> iptables -A INPUT -p icmp -m icmp --icmp-type any -j ACCEPT
We have to be able to talk to ourselves...
#> iptables -A INPUT -i lo -j ACCEPT
...and carry on a conversation.
#> iptables -A INPUT -m state --state ESTABLISHED,RELATED --j ACCEPT
With regard to unwanted traffic: UDP is stateless so we'll let the
default DROP policy discard that. TCP is stateful so we may or may not
want to let the default DROP policy apply. If we decide against
dropping unwanted TCP traffic we may want to cleanly terminate those
connections by resetting them
#> iptables -A INPUT -p tcp -j REJECT --reject-with tcp-reset
We're ready. Let's open for business and allow NEW customers
(this one is shopping for SMTP)
#> iptables -A INPUT -p tcp --dport 25 --state NEW -j ACCEPT
(this one is shopping for HTTP)
#> iptables -A INPUT -p tcp --dport 80 --state NEW -j ACCEPT
Hope that is enough to get you going :m)
next prev parent reply other threads:[~2009-03-26 23:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:24 Identifiying and modifying packets aragonx
2009-03-26 19:23 ` Kristian Evensen
2009-03-26 19:43 ` aragonx
2009-03-26 20:45 ` Kristian Evensen
2009-03-26 20:54 ` Verify rules Scott Miller
2009-03-26 23:35 ` Mike Wright [this message]
2009-03-27 8:05 ` Mart Frauenlob
2009-03-27 17:15 ` Scott Miller
2009-03-27 18:49 ` Mike Wright
2009-03-27 18:58 ` Mike Wright
2009-03-27 19:49 ` Scott Miller
2009-03-27 19:55 ` Mike Wright
2009-03-27 20:12 ` Scott Miller
2009-03-27 22:49 ` Mart Frauenlob
2009-03-27 19:56 ` Mike Wright
2009-03-27 19:25 ` Rob Sterenborg
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=49CC1149.3020604@mailinator.com \
--to=mike.wright@mailinator.com \
--cc=netfilter@vger.kernel.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