All of lore.kernel.org
 help / color / mirror / Atom feed
From: Payal Rathod <payalrathod@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: LAN accessing DMZ
Date: Sun, 18 Jul 2004 18:53:53 +0530	[thread overview]
Message-ID: <f51b72bc040718062373640612@mail.gmail.com> (raw)

Hi,
I am trying out DMZ. But my LAN users (192.168 range) can access DMZ 
(10.10.10.x) range without any restrictions. On this firewall machines
there are 3 cards 1 for DMZ range, 1 for LAN range  and for my ISP.

I have,
$IPTABLES -P INPUT DROP
$IPTABLES -P OUTPUT ACCEPT  # Is this a Bad Idea?
$IPTABLES -P FORWARD DROP

For FORWARD I allow just,
$IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPTABLES -A FORWARD -s 192.168.0.0/16 -p tcp --dport 3128 -j ACCEPT
$IPTABLES -A FORWARD -s 192.168.0.0/16 -p tcp --dport 53 -j ACCEPT
$IPTABLES -A FORWARD -s 192.168.0.0/16 -p udp --dport 53 -j ACCEPT

$IPTABLES -A FORWARD -s 10.0/8 -p tcp -j ACCEPT
$IPTABLES -A FORWARD -s 10.0/8 -p udp -j ACCEPT
$IPTABLES -A FORWARD -d 10.10.10.2 -p tcp --dport 25 -j ACCEPT
(This I am just testing whether  I can access my DMZ port 25 from outside)

But still my LAN users can access 10.10.10.2:25 and also the webin 10000 port.
What am I missing?

Thanks a lot in advance and waiting eagerly for any answers.

With warm regards,
-Payal


             reply	other threads:[~2004-07-18 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 13:23 Payal Rathod [this message]
2004-07-18 15:10 ` LAN accessing DMZ Antony Stone
2004-07-18 16:24   ` Payal Rathod
2004-07-18 16:39     ` Antony Stone
2004-07-18 16:58       ` Payal Rathod
2004-07-18 17:12         ` Antony Stone
2004-07-18 17:39           ` Payal Rathod
2004-07-18 17:59             ` Antony Stone
2004-07-18 18:51               ` Payal Rathod
2004-07-18 19:12                 ` Antony Stone
2004-07-19 11:13                   ` Payal Rathod

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=f51b72bc040718062373640612@mail.gmail.com \
    --to=payalrathod@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.