All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Collodel <dave@crawlspaceradio.com>
To: netfilter@lists.netfilter.org
Subject: [Fwd: Re: DMZ trouble!]
Date: 09 Jan 2003 10:34:28 -0500	[thread overview]
Message-ID: <1042126468.1331.10.camel@jimmy> (raw)

I wasn't sure how much of it would affect what would cause the problems,
so I included the whole thing minus some stuff like the module loading. 

I built this script based on a couple others I found through Google.
I've not yet figured out enough of IPTables to lock down the servers as
tightly as I'd like without breaking everything. I'm still relying on
local ipchains on each server to keep them safe until I get my head
around IPTables well enough.

Anyway, I'll definitely take all your advice under consideration. At
least now I've got an idea of what I need to do. I don't fully get how
the DNAT and SNAT work, but at least I've got a direction to be looking.

Thanks a lot for your help. :)

On Thu, 2003-01-09 at 02:58, Joel Newkirk wrote:
> On Thursday 09 January 2003 12:34 am, David Collodel wrote:
> 
> {Very heavily snipped}
> 

<snipped most>

> > # 3.2 PREROUTING chain
> 
> > # 3.2.3 DMZ DNAT
> > #
> >
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> > --dport 80 -j DNAT --to-destination $DMZ_HTTP_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> > --dport 22 -j DNAT --to-destination $DMZ_HTTP_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> > --dport 443 -j DNAT --to-destination $DMZ_HTTP_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> > --dport 8000 -j DNAT --to-destination $DMZ_HTTP_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> > --dport 8001 -j DNAT --to-destination $DMZ_HTTP_IP
> >
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> > 53 -j DNAT --to-destination $DMZ_DNS_IP
> > $IPTABLES -t nat -A PREROUTING -p UDP -i $EXT_IFACE -d $DNS_IP --dport
> > 53 -j DNAT --to-destination $DMZ_DNS_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> > 443 -j DNAT --to-destination $DMZ_DNS_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> > 22 -j DNAT --to-destination $DMZ_DNS_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> > 25 -j DNAT --to-destination $DMZ_DNS_IP
> > $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> > 995 -j DNAT --to-destination $DMZ_DNS_IP
> 
> Hmmm.  Well, this is the answer to your 'real' question.  I don't see ANY 
> rules in PREROUTING to DNAT connections from the LAN. Those would be 
> addressed -d $DNS_IP, but would be -i $LAN_IFACE.
> 
> You should seriously reconsider what communications the firewall box 
> itself requires, and what traffic the LAN is allowed to conduct.
> 
> j

-- 
David Collodel <dave@crawlspaceradio.com>



                 reply	other threads:[~2003-01-09 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1042126468.1331.10.camel@jimmy \
    --to=dave@crawlspaceradio.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.