From owner-freebsd-questions@FreeBSD.ORG Sat May 20 17:10:22 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8424B16A427 for ; Sat, 20 May 2006 17:10:22 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA66343D48 for ; Sat, 20 May 2006 17:10:21 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.6/8.13.6) with ESMTP id k4KHABEB054333; Sat, 20 May 2006 10:10:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.6/8.13.6/Submit) id k4KHABpq054332; Sat, 20 May 2006 10:10:11 -0700 (PDT) (envelope-from sgk) Date: Sat, 20 May 2006 10:10:11 -0700 From: Steve Kargl To: Chuck Swiger Message-ID: <20060520171011.GB54239@troutmask.apl.washington.edu> References: <20060519224819.GA48412@troutmask.apl.washington.edu> <6.0.0.22.2.20060519175424.02689218@mail.computinginnovations.com> <20060520160842.GA53996@troutmask.apl.washington.edu> <446F44D1.6040104@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <446F44D1.6040104@mac.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-questions@freebsd.org Subject: Re: Setting up NIS questions? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2006 17:10:22 -0000 On Sat, May 20, 2006 at 12:33:21PM -0400, Chuck Swiger wrote: > Steve Kargl wrote: > >I can't even get NIS set up with ypinit. It unconditionally > >uses /bin/hostname, which will grab the FQDN of the system. > >You have given me an idea. I can change rc.conf to set hostname > >to the name I've given 192.168.0.10, put that on bge0, put > >the IP address associated with the FQDN on bge1, and reboot. > >This might permit NIS to come up. Though this seems like a hack, > >because when someone connects to the seem via the FQDN, > >/bin/hostname will give the wrong answer. > > Associating the ypdomain with the FQDN from the DNS is convenient, and a > convention that many follow, but it is not required, by any means. The > O'Reilly "Managing NIS and NFS" book is a fine reference on this sort of > thing, BTW, and is probably available online in PDF form if you look. Thanks for the pointer. I'll go looking for this book. > Nevertheless, YP/NIS predates many of the more convoluted network > designs that people set up nowadays, and was intended for machines which > have a single identity even if they have multiple NICs-- Sun used to > assign the same MAC address to all NICs on one machine, to ensure that > people respected collision domains. I don't see how this is convoluted. In fact, I would be inclined to claim that it is the defacto method for setting up an internal computational cluster s <---> node1 internet <-F-> FQDN|master <---> w <---> node2 t <---> node3 where swt = switch. > It is not normally desirable to set up a YP/NIS master server on > a machine which is multihomed in the sense of doing NAT or needing > a firewall to separate internal from external, and obvious a > firewall machine running zero or the minimal necessary services is > a lot more secure.... Note that <-F-> actually has at least one firewall. Only people in the apl.washington.edu domain can get to FQDN. I was hoping to use NIS to simplify the propagation of info (eg., passwd, hosts, etc.) from master to the nodes. Propagating the info by hand isn't too bad because I only have five nodes represently. However, I hope to grow an additional 11 nodes. -- Steve