From owner-freebsd-current Tue May 25 1:50: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 6A7E614C93; Tue, 25 May 1999 01:49:58 -0700 (PDT) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id JAA03493; Tue, 25 May 1999 09:49:55 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00559; Tue, 25 May 1999 08:46:21 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905250746.IAA00559@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Nicholas J. Esborn" Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: natd as a 'routing daemon' In-reply-to: Your message of "Mon, 24 May 1999 12:00:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 May 1999 08:46:21 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just a thought... > > Might it not be logical to put natd in the 'routing daemons' section of > the boot process? That would start it before things like quota checking, > which can take a lot of time and prevent a combination worgroup server/NAT > box from providing network access, even when it could be with no > consequence. > > Also, it does seem rather like a form of routing. Natd is now started right after the firewall is loaded - as a ``divert daemon''. > Nicholas Esborn | > www.azstarnet.com | StarNet > (520) 618-RTFM | -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message