Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Nov 2001 08:07:16 -0800 (PST)
From:      "K. Greenwood" <k_greenwood1@yahoo.com>
To:        Drew Tomlinson <drew@mykitchentable.net>
Cc:        questions@freebsd.org
Subject:   Re: Resolving internal IP's through NAT.
Message-ID:  <20011111160716.844.qmail@web14106.mail.yahoo.com>
In-Reply-To: <008901c16ac6$77e41630$0301a8c0@bigdaddy>

next in thread | previous in thread | raw e-mail | index | archive | help
--- Drew Tomlinson <drew@mykitchentable.net> wrote:
> ----- Original Message -----
> From: "K. Greenwood" <k_greenwood1@yahoo.com>
> To: <freebsd-questions@FreeBSD.ORG>
> Sent: Saturday, November 10, 2001 3:18 PM
> Subject: Resolving internal IP's through NAT.
> 
> 
> > Hello.  I currently have a FreeBSD 4.2 box which
> is
> > running NAT and
> > need to have some internal systems which can be
> > accessible
> > from the other side of the network.  NAT is being
> run
> > on the
> > following xl2 (192.168.50.21) address.
> >
> > I've done some searching, but the nearest thing
> I've
> > found is this:
> >
> >
>
http://lists.openresources.com/FreeBSD/freebsd-net/msg00454.html
> 
> I was unable to open the link above and see to what
> you are referring.
> However, I run NAT and have services/machines
> available from the
> outside but do it quite differently than what you
> are attempting.  I
> don't think it can work in the way you describe but
> I am no expert by
> any means.
> 
> The way I do it is I have NAT forward requests to
> certain ports from
> the outside to ports on machines on the inside.  For
> example, my web
> server (http://www.mykitchentable.net) is on
> internal box running on
> port 80.  Connections to
> http://www.mykitchentable.net connect to my
> public IP (assigned by my ISP via DHCP) on port 80. 
> NAT sees the
> request coming in on port 80 and forwards it to my
> internal machine on
> port 80.

Hmm... thanks.  I haven't tried that.  What I
currently have is that
three networked printers need to have access from an
external network.

I made this from another message (off list).

121.141.254.1              192.168.50.1
      |                           |
      |                           |
  xl1(exter)                 xl2(exter)
121.141.254.2              192.168.50.21(aliased x3)
      |                           |
      |___________________________|
                    |
                    |
               xl0(inter) 
             121.141.254.3
                    |
                   LAN
             121.141.254.x

The networked printers are on the LAN side but need to
be resolvable
(sp?) from the xl2 side.(and yes, I know that's a
non-routeable
address, but I ain't in power).

> As another example, I have two FBSD boxes.  Say I
> wanted to be able to
> access both from the outside via Telnet. Now this is
> not a secure
> thing to do but this is just an example.  I would
> set both internal
> boxes to accept telnet connections on port 23.  Then
> I'd tell NAT that
> connections coming in on port 23 should be forwarded
> to box 1 port 23.
> To get to box two, I would tell NAT that connections
> coming in on port
> 8023 should be forwarded to box 2 port 23.

Thanks... I didn't know that I could use redirect_port
to specify
different destination IP's.  Off I go to the natd
man-page. 

Thanks for the response, and I would appreciate it if
you have
any advice, recommendations, how-to's (pointer's) send
them my
way.
 
> I actually use the NAT that is built into my ADSL
> modem/router but I
> am sure that natd has a similar function.
> 
> HTH,
> 
> Drew

Keith

__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011111160716.844.qmail>