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: Thu, 02 Sep 2004 00:21:33 -0400 [thread overview]
Message-ID: <1094098893.2102.165.camel@localhost> (raw)
In-Reply-To: <20040902040821.GA12641@tranquility.scriptkitchen.com>
On Thu, 2004-09-02 at 00:08, Payal Rathod wrote:
> On Wed, Sep 01, 2004 at 11:54:55PM -0400, John A. Sullivan III wrote:
>
> > 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
>
> So, you mean I keep the PREROUTING rule as before and make
> -A FORWARD -d 10.10.10.3 -p tcp -m tcp --dport 80 -j ACCEPT
> to
> -A FORWARD -s 5.6.7.8 -d 10.10.10.3 -p tcp -m tcp --dport 80 -j ACCEPT
>
> But will this not forward requests from my squid proxy server too?
>
> -Payal
That's right - I keep forgetting that you are using Squid. As I
mentioned, I'm a little rusty on Squid configuration. How is the
traffic getting to Squid. If I recall correctly, I usually do it with a
REDIRECT. That means there needs to be a rule to allow the traffic to
Squid (it sounds like there already is one because access is working).
However, at that point, doesn't the Squid ACL list take over? If I
recall, there is a section in the Squid configuration file where one
specifies which addresses are allowed what access - 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 4:21 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
2004-09-02 4:08 ` Payal Rathod
2004-09-02 4:21 ` John A. Sullivan III [this message]
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=1094098893.2102.165.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox