Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Dec 2000 20:20:51 -0800 (PST)
From:      Sean Peck <speck@newsindex.com>
To:        David Raistrick <keen@damoe.wireless-isp.net>
Cc:        Chris Hill <chris@monochrome.org>, freebsd-questions@FreeBSD.ORG
Subject:   Re: Configuring Gateway/NAT on Freebsd
Message-ID:  <Pine.BSF.4.10.10012102018270.14499-100000@www.newsindex.com>
In-Reply-To: <Pine.BSF.4.21.0012102311190.61629-100000@damoe.wireless-isp.net>

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


On Sun, 10 Dec 2000, 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.

ok
 
> Is there a "natd_flags" that you can use? (checking. yes.)
> 
> so natd_interface should be blank, use 
> natd_flags=-a whateveritwas
> 
  Ok, will try this
 
> and you DO have gateway_enable=yes   in the rc.conf?

	Yes I do
 
> and after a reboot sysctl -a  still shows net.inet.ip.forwarding=0  ??
> 
> odd.
> 
> su to root and manually set it.

 Yes, root can set it manually, but with :

natd_enabled="YES" and gate_enabled="YES" on bootup the sysctl shows a 0
for forwarding... 

The interesting thing I am still having though is dispite the ifconfig
alias for 172.16.0.1 being on, the box is not answering to the IP... nor
can any other machine on my network succesfully find it... NO errors are
being thrown ... even after manually setting it at command line, I still
cannot hit the box via the 172.16.0.1 ip...

Sean



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.4.10.10012102018270.14499-100000>