From owner-freebsd-net@FreeBSD.ORG Wed Oct 18 17:24:45 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BB9116A412 for ; Wed, 18 Oct 2006 17:24:45 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D7F143D46 for ; Wed, 18 Oct 2006 17:24:45 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin05-en2 [10.13.10.150]) by smtpout.mac.com (Xserve/8.12.11/smtpout02/MantshX 4.0) with ESMTP id k9IHOjEF014281; Wed, 18 Oct 2006 10:24:45 -0700 (PDT) Received: from [17.214.13.96] (a17-214-13-96.apple.com [17.214.13.96]) (authenticated bits=0) by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id k9IHOhMs009880; Wed, 18 Oct 2006 10:24:44 -0700 (PDT) In-Reply-To: <6170c1110610180933g10a600dbu98cd1d7aab60e987@mail.gmail.com> References: <6170c1110610180933g10a600dbu98cd1d7aab60e987@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <88D784E1-C661-4B03-B412-653CE9EF09AB@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Wed, 18 Oct 2006 10:24:42 -0700 To: Brent Marsh X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: freebsd-net@freebsd.org Subject: Re: Networking newbie X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2006 17:24:45 -0000 On Oct 18, 2006, at 9:33 AM, Brent Marsh wrote: > I've been working with FreeBSD machines on and off for several > years now. I > am looking to set up my first network. First for home, and second > for an > office environment. I want to make sure I follow 'industry > standards' so my > network will have everything that any network in corporate America > might > have, with no corners cut. Actually, it isn't hard to do significantly better than the average corporate network, even if you do cut corners. > As a total networking newbie, I'm looking for step-by-step > instructions. This is impractical without knowing the details about your network, hardware resources, services and users, etc. Given adequate information, it turns into work that people normally bill one for. :-) > I know the network topology, but don't know how to make them > 'work'. Do I > need to 'define' a domain? What is it that makes my network a > cohesive > unit? For your network to be a cohesive unit, it needs to be managed. This means that it needs a network admin responsible for the network to organize the resources available, implement and maintain the services needed by the users of the network, provide documentation and policies for these users so that they know what services are available (such as email, filesharing, Internet WWW access, printing, etc), and how to set them up or get help doing so. It's possible for a complete novice or newbie to learn how to configure and maintain a network by doing so, but you're not going to learn everything needed in a day (or even in a decade)-- working with a skilled network admin will bring most people up to speed much more rapidly via their example than self-learning. > If someone could point me to a step-by-step document, that'd be > great. The > FreeBSD handbook has all of the components (I suspect) but not the > actual > concepts of getting it all to work. Unless your office is entirely FreeBSD-based, you will need to think about and deal with other operating systems; the FreeBSD handbook is a good reference for setting up many services, but it does not discuss the care and feeding of Windows clients (or Mac clients, or Linux clients, etc). -- -Chuck