From owner-freebsd-stable  Mon May 24 12: 0:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from cepheus.azstarnet.com (cepheus.azstarnet.com [169.197.56.195])
	by hub.freebsd.org (Postfix) with ESMTP
	id 748CD153ED; Mon, 24 May 1999 12:00:46 -0700 (PDT)
	(envelope-from nje@azstarnet.com)
Received: from black-hole (black-hole.azstarnet.com [169.197.53.211])
	by cepheus.azstarnet.com (8.9.3/8.9.3) with SMTP id LAA18322;
	Mon, 24 May 1999 11:55:48 -0700 (MST)
X-Sent-via: StarNet http://www.azstarnet.com/
Date: Mon, 24 May 1999 12:00:45 -0700 (MST)
From: "Nicholas J. Esborn" <nje@azstarnet.com>
X-Sender: nje@black-hole
To: current@freebsd.org, stable@freebsd.org
Subject: natd as a 'routing daemon'
Message-ID: <Pine.GSO.3.96.990524120014.19101C-100000@black-hole>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@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.

  Nicholas Esborn |
www.azstarnet.com | StarNet
   (520) 618-RTFM |



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message