From owner-freebsd-questions Sun Dec 10 21:51: 3 2000 From owner-freebsd-questions@FreeBSD.ORG Sun Dec 10 21:51:00 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from www.newsindex.com (www.newsindex.com [64.71.138.178]) by hub.freebsd.org (Postfix) with ESMTP id D042337B400 for ; Sun, 10 Dec 2000 21:51:00 -0800 (PST) Received: from localhost (speck@localhost) by www.newsindex.com (8.9.3/8.9.3) with ESMTP id VAA28015; Sun, 10 Dec 2000 21:50:49 -0800 (PST) (envelope-from speck@www.newsindex.com) Date: Sun, 10 Dec 2000 21:50:48 -0800 (PST) From: Sean Peck To: "Crist J. Clark" Cc: David Raistrick , Chris Hill , freebsd-questions@FreeBSD.ORG Subject: Re: Configuring Gateway/NAT on Freebsd In-Reply-To: <20001210213435.T96105@149.211.6.64.reflexcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speck@www.newsindex.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Dec 2000, Crist J. Clark wrote: > On Sun, Dec 10, 2000 at 11:15:06PM -0500, David Raistrick wrote: > > On Sun, 10 Dec 2000, Sean Peck wrote: > > > > > Ok, well sysctl -w throws errors, and when I do your grep they come back 0 > > > as well, dispite having NATD_ENABLED... what should the natd_interface be > > > if it is not tun0, the NIC card? > > > > Good question. You COULD use it as xl0...but having 2 ip's bound to the > > itnerface might confuse it. > > > > Is there a "natd_flags" that you can use? (checking. yes.) > > > > so natd_interface should be blank, use > > natd_flags=-a whateveritwas > > No, > > natd_interface= > > >From rc.conf(5), > > natd_interface > This is the name of the public interface on which natd > should run. It is mandatory if natd_enable is set to YES. > The interface may be given as an interface name or as an IP > address. > > natd(8) won't start unless 'natd_interface' is set. See rc.network > (sorry about the long line, but quoting code verbatim), > > # Network Address Translation daemon > # > case ${natd_enable} in > [Yy][Ee][Ss]) > if [ -n "${natd_interface}" ]; then > . > . > . > echo -n ' natd'; ${natd_program:-/sbin/natd} ${natd_flags} ${natd_ifarg} > fi > > -- > Crist J. Clark cjclark@alum.mit.edu > Hmmm Ok, I will set this to the IP.. now the other thing I noticed was that in the 3.3 rc.network that the command looked for natd_program it did not have the natd_program: /sbin/natd.. so I added a natd_program to the rc.conf that is set to the /sbin/natd. I am still perplexed as to why the I cannot reach the box from itself via the 172.16.0.1 alias... I have used ifconfig aliasing before and never had a problem... the ifconfig command runs fine and throws no errors, but I cannot reach it from itself... very odd to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message