All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: hamals@infinito.it
Cc: netfilter@lists.netfilter.org
Subject: Re: web server in DMZ
Date: Tue, 28 Sep 2004 06:40:32 -0400	[thread overview]
Message-ID: <1096368031.2050.13.camel@localhost> (raw)
In-Reply-To: <web-6416739@infinito.it>

On Tue, 2004-09-28 at 06:21, hamals@infinito.it wrote:
> I have a big problem
> 
> I have a web server in my DMZ, I reach it with his 
> internal IP 192.168.1.10 from my internal LAN, but I can't 
> reach them with his public IP.
> 
> I did a DNAT and from internet everythings is ok, my web 
> server is working in right by DNAT.
> 
> Where is the problem?
<snip>
There could be several causes.  Did you remember to bind the public
address to the public firewall NIC so that it responds to ARP requests?

For example, if the firewall is at 1.1.1.2 and you want the web server
to be at 1.1.1.3 then do

ip add address 1.1.1.3/24(or whatever the mask bit count is) dev eth0(or
whatever the device name is) brd +

You can find a short slide show on using the ip command at
http://iscs.sourceforge.net 

Good luck - 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 



  reply	other threads:[~2004-09-28 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 10:21 web server in DMZ hamals
2004-09-28 10:40 ` John A. Sullivan III [this message]
2004-09-28 14:17 ` Jason Opperisano
2004-09-28 14:44   ` hamals
2004-09-28 15:03     ` Jason Opperisano
2004-09-28 15:14       ` Marek Dohojda
2004-09-29  9:35         ` hamals
2004-09-28 14:27 ` Jose Maria Lopez

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=1096368031.2050.13.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=hamals@infinito.it \
    --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.