From owner-freebsd-questions Tue Jan 4 21:22:29 2000 Delivered-To: freebsd-questions@freebsd.org Received: from linum.cofc.edu (linum.cofc.edu [153.9.35.19]) by hub.freebsd.org (Postfix) with ESMTP id 4088115241 for ; Tue, 4 Jan 2000 21:22:26 -0800 (PST) (envelope-from astrand@linum.cofc.edu) Received: (from astrand@localhost) by linum.cofc.edu (8.9.3/8.9.3) id AAA00669; Wed, 5 Jan 2000 00:22:25 -0500 (EST) (envelope-from astrand) To: freebsd-questions@freebsd.org Subject: [Allan Strand ] natd coexisting with rpc.statd+nfs From: Allan Strand Date: 05 Jan 2000 00:22:24 -0500 Message-ID: <864sctqei7.fsf@linum.cofc.edu> Lines: 33 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm exploring different LAN configurations and one possibility >requires a firewall (running natd/ipfw to connect the LAN to a >semi-protected network) to also act as an NFS server to a couple of >machines on the LAN. >I can see that this might present security problems, yet I am curious >as to its general feasibility. >I've tried to set it up, but have run into a situation where rpc.statd >hangs on the boot. Haven't even made it to the NFS server portion. >Can anyone provide some suggestions? >THX, >A. Sorry, I forgot some information: 1) all machines involved are tracking 3.3-stable 2) I am able to nfs mount disks among other machines on the LAN 3) natd/ipfw seem to work fine to provide NAT 4) to start, I have been using the "open" firewall setting in rc.firewall (plan to restrict when I settle in the appropriate config) A. -- Allan E. Strand stranda@cofc.edu, http://linum.cofc.edu Department of Biology Phone: (843) 953-8085 College of Charleston Fax: (843) 953-5453 Charleston, SC 29424 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message