From: "Mike" <mikeeo@msn.com>
To: netfilter@lists.netfilter.org
Subject: Re: different DMZs which is better?
Date: Mon, 13 Jan 2003 14:15:34 -0500 [thread overview]
Message-ID: <001201c2bb38$25e45980$1e01a8c0@win2k.com> (raw)
In-Reply-To: 001e01c2bb10$05d79300$9865fea9@win2k.com
I talked with my ISP and they will route me a /30 for my firewall and a /28
for the DMZ segment. The DMZ will be hosting a webfarm does anyone have a
list of things I should to the box besides filtering rules? like how I can
stop directed broadcasts etc... I am going to accept Established and New
connections in the forward chain going to the webservers and drop invalid.
Is that ok for webservers or should I also accept related? Im only going to
open up port 80 to the webservers and drop everything else.
Thanks,
Mike
----- Original Message -----
From: "Mike" <mikeeo@msn.com>
To: <netfilter@lists.netfilter.org>
Sent: Monday, January 13, 2003 9:28 AM
Subject: different DMZs which is better?
> Hey guys Im deciding how I want to implement a DMZ for my company can
anyone
> tell me the pros and cons of my DMZs below? should I got with a routable
> hosts in my DMZ and just filter out any port I don't want open or just
port
> forward over certain ports and use IP alias?
>
> Thanks,
> Mike
>
> P.S excuse the art below I know it sucks.
>
>
> cisco
> |
> |
> |
> eth0
> DMZ inet IPs(eth1)---Netfilter----private LAN (eth2)
>
>
>
> cisco
> |
> |
> |
> eth0
> DMZ private IPs(eth1)---Netfilter----private LAN (eth2)
>
>
>
>
next prev parent reply other threads:[~2003-01-13 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 14:28 different DMZs which is better? Mike
2003-01-13 14:59 ` Cedric Blancher
2003-01-13 16:05 ` Filip Sneppe
2003-01-13 16:14 ` Filip Sneppe
2003-01-14 0:10 ` Joel Newkirk
2003-01-13 19:15 ` Mike [this message]
2003-01-13 20:28 ` Athan
2003-01-14 12:26 ` Filip Sneppe
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='001201c2bb38$25e45980$1e01a8c0@win2k.com' \
--to=mikeeo@msn.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