Date: Fri, 15 Feb 2002 15:12:20 -0500 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: "Ian" <freebsd@damnhippie.dyndns.org>, "freebsd-stable" <freebsd-stable@FreeBSD.ORG> Subject: Re: Suggestion on natd rc scripts Message-ID: <002f01c1b65d$13834bb0$1200a8c0@gsicomp.on.ca> References: <B892AA6F.A2AF%freebsd@damnhippie.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Suggestion 1: > > Set natd_interface to nothing by default, and let rc.network > > start natd even if natd_interface isn't set. > > > > Suggestion 2: > > All who dare touch rc.conf should always thoroughly check > > the defaults and the relevant rc.* files or prepare being > > locked out from their computer and suffer terribly ;) > > > > Does any of this make sense to you? > > > > -Richard > > I ran into exactly this same situation a couple weeks ago, and was outraged > by the fact that 1) fxp0 was hard-coded in a defaults file, and 2) the rc > files won't start natd without the interface being specified on the command > line. Well, *something* needs to be hard-coded in the defaults file. What do you suggest? > I'm a big fan of keeping all related parms in the same place. I'd rather > specify the interface in my natd config file, all I want in rc.conf is > natd_enable=yes and natd_flags set to read my config file. > > I therefore heartily endorse suggestion 1. But you're ignoring the class of users who just use natd for NAT. If you don't have any port forwarding or special rules, then you don't need a nat configuration file. All you need to do is this: natd_enable="yes" natd_interface="ed0" And you're set. May I suggest this? 3) Add a natd_conf option to rc.conf. If natd_conf is set, then ignore natd_interface. This will let uber power-users do this: natd_enable="yes" natd_conf="/etc/natd.conf" And still preserve "historic" behaviour: natd_enable="yes" natd_interface="ed0" -- Matt Emmerton 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?002f01c1b65d$13834bb0$1200a8c0>