Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Mar 1999 11:36:52 -0600 (CST)
From:      Phillip Salzman <natdissue@gamefish.pcola.gulf.net>
To:        Tanguy de Courson <tanguy@itninc.net>
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: natd Issues
Message-ID:  <Pine.BSF.4.05.9903171059110.14605-100000@gamefish.pcola.gulf.net>
In-Reply-To: <199903171651.IAA00963@mail.itnnet.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Yes.

Everything seems to work on the 2.2 machine except redirect_address
(well, it routes packets.)  The 3.1 machine just sits there.  I have it
setup like:

(3.1 box's setup)

	de0 (external interface) -> Outside World
	       /|\
		|
	tx0 (10.0.0.1)	<-  10.0.0.2

I can ping 192.168.0.1 from 192.168.0.2.  I can also telnet to it, etc.
sysctl's net.inet.ip.forwarding is actived (1).  It just isn't routing
the packets.  IPFIREWALL_DEFAULT_TO_ACCEPT is also in the kernel.

All i'm really interested in is getting redirect_address functioning.
This is the config file (for 2.2.8-STABLE):

------------------
	# natd config
	use_sockets	yes
	same_ports	yes
	log	yes
	alias_address 204.214.18.2
	redirect_address 10.0.0.192 204.214.18.2
------------------

Is there something i'm missing for redirect_address?  When I kill &&
restart it, nothing works at all.

The kernel config has this information in it:

------------------
	options         IPFIREWALL
	options         IPFIREWALL_DEFAULT_TO_ACCEPT
	options         IPDIVERT
------------------

On Wed, 17 Mar 1999, Tanguy de Courson wrote:

> did you compile IPDIVERT and IPFIREWALL into your kernel?
> 
> At 09:10 AM 03/17/1999 -0600, you wrote:
> >I just have a couple of questions about some natd problems we're
> >having while setting up a rather large ADSL customer to use it.
> >
> >We have to use the redirect_address feature to alias IPs into their
> >internal network.  It doesn't seem to work at all.  The computer stops
> >transmitting packets.  This machine is 2.2.8-STABLE.
> >
> >I setup a test lab here at the office, but the only machine I could find
> >for it was running 3.1-STABLE.  This one won't even route packets.
> >
> >Are these known problems?  Is anyone working on them?  
> >
> >I compiled the natd sources from 2.2.8-STABLE in 3.1-STABLE, but still 
> >had no luck.  Do you think this is related to the IPDIVERT for divert
> >sockets?
> >
> >Any help you can offer will be great.  Thanks!
> >
> >
> >
> >To Unsubscribe: send mail to majordomo@FreeBSD.org
> >with "unsubscribe freebsd-stable" in the body of the message
> > 
> -----------------------------------------------------------
> Tanguy 'Ripper' de Courson - Internet Programmer ('Perl') at ITN
> myneid - fool 'o fools, gnome 'o gnomes
> "schalin666: Okay. I guess I should allow a human's right to a higher
> education, so long as it doesn't ruin my pornography income"
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" 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.4.05.9903171059110.14605-100000>