Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: iptables <netfilter@lists.netfilter.org>
Subject: Re: ruleset
Date: Tue, 20 Jul 2004 16:37:13 +0100	[thread overview]
Message-ID: <200407201637.13100.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <HAEOIFPIBBBLGLHOMLLIAEMFCEAA.bclark@eccotours.biz>

On Tuesday 20 July 2004 3:58 pm, Brent Clark wrote:

> Hi all
>
> Below is a copied and pasted ruleset.
> Anyone care to have a look, it would really be appreciated.

<snip...>

> # Allow for resolving of  DNS and lookup from  gate
>
> /sbin/iptables -A OUTPUT -o eth0 -p udp --dport 53 -m state --state NEW -j
> ACCEPT
> /sbin/iptables -A INPUT -i eth1 -p udp --sport 53 -m state --state NEW -j
> ACCEPT
> /sbin/iptables -A FORWARD -p udp --sport 53 -m state --state NEW -j ACCEPT

Is your firewall running a DNS server?   If so, you want the INPUT rule.   If 
not (ie: you are passing DNS requests through to somewhere else), you want 
the FORWARD rule.   I'd be surprised if you really want both.

Why do you specify source port 53 in the FORWARD rule instead of destination 
port 53?   The reply packets are already taken care of by the 
ESTABLISHED,RELATED rule.

> # Allow access gate from 192.168.111.0/255.255.255.0
>
> /sbin/iptables -A INPUT -i eth1 -p all -s 192.168.111.0/24 -j ACCEPT

You want *all* machines on 192.68.111.0./24 to have access to *all* services 
on the firewall??

> /sbin/iptables -A FORWARD -p all -s 192.168.111.0/24 -d 192.168.111.0/24 -j
> ACCEPT

This one makes no sense.   Packets from one subnet to another machine on the 
same subnet do not go through the firewall.

> # Allow access to port 80(http) and 443(https) to the gate
>
> /sbin/iptables -A INPUT -i eth1 -s 192.168.111.0/24 -p tcp -m
> multiport --dport 80,443 -m state --state NEW -j ACCEPT

You are running an http/s server on the firewall???

> #/sbin/iptables -A INPUT -p tcp -m tcp --dport 21 -j ACCEPT

You are running an FTP server on the firewall as well as HTTP, HTTPS and 
perhaps DNS???   Something makes me think you don't know about good security 
practice saying "don't run uneccessary (some people say "any") services on 
your firewall, as a compromise of one service can lead to a compromise of the 
firewall".

Regards,

Antony.

-- 
"It would appear we have reached the limits of what it is possible to achieve 
with computer technology, although one should be careful with such 
statements; they tend to sound pretty silly in five years."

 - John von Neumann (1949)

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-07-20 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 14:58 ruleset Brent Clark
2004-07-20 15:37 ` Antony Stone [this message]
2004-07-20 16:02   ` ruleset Brent Clark
2004-07-20 16:13     ` ruleset Antony Stone
2004-07-20 16:31       ` ruleset Brent Clark
  -- strict thread matches above, loose matches on Subject: below --
2004-08-10  7:22 Ruleset Brent Clark
2004-08-10  8:27 ` Ruleset Antony Stone
2004-08-10  8:45   ` Ruleset Antony Stone
2004-08-10  9:15     ` Ruleset Brent Clark

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=200407201637.13100.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