Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Oct 1998 22:50:01 -0700 (PDT)
From:      Loren Daniel Koss <loren@boingo.pciway.com>
To:        Dan Langille <junkmale@xtra.co.nz>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: NATD & IPFW..
Message-ID:  <Pine.BSF.3.95q.981022224709.470A-100000@boingo.pciway.com>
In-Reply-To: <199810230412.RAA19188@cyclops.xtra.co.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
Okay, I got it to work.  It looks like I *didn't* have IPDIVERT optioned
like I thought I did.  Strange..  There is a file named LINT in the
i386/conf file and for some strange reason I thought it was using it.
Nope.  I added it to my new KERNAL def file and voila everything
works..  Going out..  Now I gotta figure out how to make my web server
that now has a 192.168.1.x address get access from the outside.

I tried natd -redirect_address 206.0.98.200 192.168.1.200, but that seemed
to fail.  Will I have to alias every address in the 206.0.98.x domain to
ep0 so that it listens to it?

Sorry about being such a newbie to all this..  Thanks for all your help!

-Loren

On Fri, 23 Oct 1998, Dan Langille wrote:

> On 22 Oct 98, at 20:13, Loren Daniel Koss wrote:
> 
> > Now, here's my new network topology:
> > 
> > 206.0.98.1 <-- Router
> > |
> > 206.0.98.10 <-- EP0
> > 
> > 192.168.1.1 <--EP1
> > |
> > |
> > -------Rest of Network - All 192.168.1.x ---------
> > 
> > Okay, without doing much, machines cacn ping 206.0.98.10, 192.168.1.1, and
> > other 192.168.1.x machines just fine.  The BSD box can get to the internet
> > just fine, as well.
> > 
> > Question is how do I masquerade the 192.168.1.x network out to the world
> > through the 206.0.98.10 address.
> 
> You really don't have to worry about it.  natd will take care of it for 
> you.  See below for how to install that.
> 
> > Also, I run a webserver on one of the machines.  How is that going to work
> > properly?  I host about 7 sites on it with seven unique addresses.  I was
> > thinking of hosting them all on one address with different ports and
> > somehow using NATD to route an address to the proper port on that machine.
> 
> You can use the redirect bit on natd.  It's quite easy.  I've done it.  
> See http://www.freebsddiary.com/freebsd/http.htm because I think that's 
> what you want.
> 
> > I also noticed when it boots it says "IP Filtering Enabled, Divert
> > Disabled, logging disabled."  Is that normal?  I have the IPDIVERT option
> > turned on in the kernal.
> 
> No, I don't think so.  Mine says Divert enabled.  It sounds like you 
> haven't specified that diverting of packets is to be done.  See below.
> 
> > What I need:
> > STEP BY STEP INSTRUCTION (ie natd -n ep0 then ipfw blah blah blah).
> 
> It's close to step by step.  The following should help.  The information 
> is there but in several sites.
> 
> http://www.freebsddiary.com/freebsd/natd.htm
> http://www.freebsddiary.com/freebsd/dns.htm
> http://www.freebsddiary.com/freebsd/filtering.htm
> http://www.freebsddiary.com/freebsd/natd2.htm
> 
> Of prime importance is your natd setup.  Be sure to read the Running natd 
> section at the bottom of http://www.freebsd.org/cgi/man.cgi?natd (also 
> known as "man natd").
> 
> --
> Dan Langille
> DVL Software Limited
> The FreeBSD Diary - my [mis]adventures
> http://www.FreeBSDDiary.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?Pine.BSF.3.95q.981022224709.470A-100000>