From owner-freebsd-hackers  Tue Feb  9 11:43:20 1999
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA27090
          for freebsd-hackers-outgoing; Tue, 9 Feb 1999 11:43:20 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from helen.CS.Berkeley.EDU (helen.CS.Berkeley.EDU [128.32.131.251])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27085
          for <freebsd-hackers@freebsd.org>; Tue, 9 Feb 1999 11:43:19 -0800 (PST)
          (envelope-from jmacd@helen.CS.Berkeley.EDU)
Received: (from jmacd@localhost)
	by helen.CS.Berkeley.EDU (8.9.1a/8.9.1) id LAA05978;
	Tue, 9 Feb 1999 11:43:19 -0800 (PST)
Message-ID: <19990209114319.30878@helen.CS.Berkeley.EDU>
Date: Tue, 9 Feb 1999 11:43:19 -0800
From: Josh MacDonald <jmacd@CS.Berkeley.EDU>
To: freebsd-hackers@FreeBSD.ORG
Subject: natd and rc.firewall
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I recently followed the directions in the natd man page, I'm trying
to set up IP masquerading.  I noticed that natd is started in the 3rd
network startup phase, yet rc.firewall runs from the first.  This means
that everything inbetween the firewall startup and natd has no network
access, yet this is when many utilities try to run.  I had to move natd
to start before running rc.firewall, and it seems to work now.  Someone
who understands this stuff might want to take a look.

-josh

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