Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Payal Rathod <payal-netfilter@scriptkitchen.com>
To: Netfilter ML <netfilter@lists.netfilter.org>
Subject: Re: server in DMZ
Date: Wed, 1 Sep 2004 23:17:55 -0400	[thread overview]
Message-ID: <20040902031755.GA11485@tranquility.scriptkitchen.com> (raw)
In-Reply-To: <1094094296.1824.96.camel@wolfpack.ljm.dom>

On Wed, Sep 01, 2004 at 11:04:56PM -0400, Jason Opperisano wrote:
> i assume the squid proxy can already fetch content from the web server
> in the DMZ for your LAN--if this is not the case; please post your
> current rules:

Yes, it can access the DMZ using public IP right now. Now I want something
very simple, I want to allow only the client to access the machine.

> iptables -A FORWARD -i $extIf -o $dmzIf -p tcp --syn \
>   -s 1.2.3.4 --sport 1024:65535 -d 10.10.10.3 --dport 80 \
>   -j ACCEPT

Can you make this a bit simpler? I am not too worried about security of 
designs (no need for VPN). I just want only the client's IP to access it.
Right now I have,
-A PREROUTING -d 5.6.7.8 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.10.10.3

5.6.7.8 is my external IP of the DMZ machine.

I am afraid if I give it as,
-A PREROUTING -s 1.2.3.4 -d 5.6.7.8 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.10.10.3

it will block access from my local LAN also via. the squid proxy and yes 
the gateway (squid proxy) machine does have 3 cards.

With warm regards,
-Payal


  reply	other threads:[~2004-09-02  3:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02  2:50 server in DMZ Payal Rathod
2004-09-02  3:04 ` Jason Opperisano
2004-09-02  3:17   ` Payal Rathod [this message]
2004-09-02  3:24     ` Jason Opperisano
2004-09-02  3:51       ` Payal Rathod
2004-09-02  3:54         ` John A. Sullivan III
2004-09-02  4:08           ` Payal Rathod
2004-09-02  4:21             ` John A. Sullivan III
2004-09-02 13:13             ` Jason Opperisano
2004-09-02 19:04               ` Payal Rathod
2004-09-02 19:17                 ` Jason Opperisano
2004-09-02  3:05 ` John A. Sullivan III

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=20040902031755.GA11485@tranquility.scriptkitchen.com \
    --to=payal-netfilter@scriptkitchen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox