From owner-freebsd-stable Fri Feb 15 12:12:38 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id 2DE7737B416 for ; Fri, 15 Feb 2002 12:12:23 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.128.21]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020215201222.FKYJ7643.tomts6-srv.bellnexxia.net@xena.gsicomp.on.ca>; Fri, 15 Feb 2002 15:12:22 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id g1FK0qi83681; Fri, 15 Feb 2002 15:00:52 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <002f01c1b65d$13834bb0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Ian" , "freebsd-stable" References: Subject: Re: Suggestion on natd rc scripts Date: Fri, 15 Feb 2002 15:12:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > 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