From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Payal Rathod <payal-netfilter@scriptkitchen.com>
Cc: Netfilter ML <netfilter@lists.netfilter.org>
Subject: Re: server in DMZ
Date: Wed, 01 Sep 2004 23:54:55 -0400 [thread overview]
Message-ID: <1094097295.2037.161.camel@localhost> (raw)
In-Reply-To: <20040902035116.GA12345@tranquility.scriptkitchen.com>
On Wed, 2004-09-01 at 23:51, Payal Rathod wrote:
> On Wed, Sep 01, 2004 at 11:24:41PM -0400, Jason Opperisano wrote:
> > i can simplify it to:
> >
> > -A FORWARD -p tcp -s 1.2.3.4 -d 10.10.10.3 --dport 80 -j ACCEPT
>
> Ok easy enough I guess :)
>
> > > it will block access from my local LAN also via. the squid proxy and yes
> > > the gateway (squid proxy) machine does have 3 cards.
> >
> > yes--you're probably right that it would break access from the local LAN
> > in your current configuration
>
> So, what do I do for such a case?
>
> -Payal
I think you have confused the issues. Do not put the source match in
the PREROUTING rule (thus your squid access from the local LAN will not
break). Do put the source match in the FORWARD rule. That will
restrict outside access to only 1.2.3.4. I assume there is already a
FORWARD rule that allows access from the LAN. Hope this helps - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-09-02 3:54 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
2004-09-02 3:24 ` Jason Opperisano
2004-09-02 3:51 ` Payal Rathod
2004-09-02 3:54 ` John A. Sullivan III [this message]
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=1094097295.2037.161.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=netfilter@lists.netfilter.org \
--cc=payal-netfilter@scriptkitchen.com \
/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.