public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Need documentation on Orange (DMZ). I'll do the work
Date: Sat, 22 Nov 2014 22:54:22 -0600	[thread overview]
Message-ID: <5471687E.3060305@dailydata.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hey all. I do not see the basics of how to set up a DMZ in one single
article, and I was thinking about writing it since I'm getting ready to
set up my first one (so I'll have screen shots). First, I want to make
sure I understand it correctly. I'm using 192.168.20.0/24 as a public IP
range (I know it is not, but for this article...)

1. red interface has a block of public IP's assigned, 192.168.20.192/27
2. orange interface has IP of private IP, 172.16.54.1/24
3. for each public IP
   Assign server to a private IP (172.16.54.x)
   Create DMZ pinhole from public IP to orange IP

Basically, if I'm understanding correctly, setting up the orange
interface is similar to setting up port forwarding into the green interface?

I'm going to start playing with this, but would prefer to not start out
with an incorrect assumption.

Also, can anyone tell me WHY we should use orange vs green? It appears
to be so well understood by so many people that it is not explained. I'd
like the article to be a total newbie document, but later cover things
like QOS and stuff.

Rod


-- 
"Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

                 reply	other threads:[~2014-11-23  4:54 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=5471687E.3060305@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=documentation@lists.ipfire.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