Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Jul 2002 22:33:33 -0700
From:      "Crist J. Clark" <crist.clark@attbi.com>
To:        Naga Suresh B <torvalds@addr.com>
Cc:        freebsd-ipfw@FreeBSD.ORG
Subject:   Re: problem with portforwarding
Message-ID:  <20020730053333.GA89241@blossom.cjclark.org>
In-Reply-To: <004d01c232d3$352683c0$9600a8c0@blraddrcom>
References:  <004d01c232d3$352683c0$9600a8c0@blraddrcom>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
[-security snipped, this has nothing to do with -security. It is
probably better for -questions than -ipfw too, but I'll not change
that.]

On Wed, Jul 24, 2002 at 11:00:20AM +0530, Naga Suresh B wrote:
> Hai,
> 
>               We are facing a problem in configuring the portforwarding on
> our gateway. We are having a gateway with two network cards one with
> external ip(xxx.xxx.xxx.170) and another one with internal
> ip(192.168.0.200). We Created an alias ip for another external
> ip(xxx.xxx.xxx.172) and we had done portforwarding  443 to another internal
> ip (192.168.0.203) on another fbsd machine. We added the following line in
> the natd.conf on 192.168.0.200
> redirect_port tcp 192.168.0.203:443 xxx.xxx.xxx.172:443
> redirect_port tcp 192.168.0.203:22 xxx.xxx.xxx.172:22
> We are running ipfw on the 192.168.0.200.  We are running httpd on both the
> machines. After doing portforwarding when we are trying to access the
> application from outside xxx.xxx.xxx.172 is working fine. But we are not
> able to access the application on 172  from inside with public ip and we are
> able to access the application with 192.168.0.203. Also the name does not
> resolve for the IP xxx.xxx.xxx.172 from the internal network where as the
> same thing happens from outside. How do we solve this? Please Give the
> solution as early as possible and plz help us.

This is a FAQ,

  http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-questions/20020224.freebsd-questions

There are a number of ways to solve this. The two most common are two
invoke another natd(8) on the internal interface or to properly
configure DNS to resolve to different IPs for the same hostname
depending on which network the query comes. Your DNS issue is
completely separate and has nothing to do with NAT.
-- 
Crist J. Clark                     |     cjclark@alum.mit.edu
                                   |     cjclark@jhu.edu
http://people.freebsd.org/~cjc/    |     cjc@freebsd.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ipfw" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20020730053333.GA89241>