Date: Fri, 4 May 2001 10:12:59 +0300 From: Ruslan Ermilov <ru@FreeBSD.ORG> To: Nick Rogness <nick@rogness.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/rc.network and natd_enable Message-ID: <20010504101259.A58642@sunbay.com> In-Reply-To: <Pine.BSF.4.21.0105031700370.14970-100000@cody.jharris.com>; from nick@rogness.net on Thu, May 03, 2001 at 05:17:17PM -0500 References: <Pine.BSF.4.21.0105031700370.14970-100000@cody.jharris.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 03, 2001 at 05:17:17PM -0500, Nick Rogness wrote:
>
> In 4.2-STABLE, /etc/rc.network has entries to turn on natd. However, natd
> does not get enabled if you don't specify natd_interface. WHat if you you
> have setup stored in a configuration file and do not wish to supply an
> interface flag in /etc/rc.conf? Well, natd does not turn on!
>
> Would it make more sense to do something like (psuedo-ish code):
>
> if (natd_enable = YES)
>
> if (natd_interface defined)
> natd -n $natd_interface $natd_flags
> elif (natd_flags defined)
> natd $natd_flags
> fi
> fi
>
>
> It would allow for people to not specify a natd_interface but still be
> able to run natd out of rc.conf. What does everyone think of this?
>
> I guess you pay the penalty if someone doesn't setup the flags properly
> but I guess you could write that off as a config error anyways.
>
${natd_interface} is required to set up the ``divert natd'' rule
from /etc/rc.firewall.
Cheers,
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010504101259.A58642>