From owner-freebsd-newbies@FreeBSD.ORG Wed Dec 15 16:24:17 2004 Return-Path: Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9599516A4CE for ; Wed, 15 Dec 2004 16:24:17 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F33243D54 for ; Wed, 15 Dec 2004 16:24:17 +0000 (GMT) (envelope-from geekout@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so128786wri for ; Wed, 15 Dec 2004 08:24:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=qYVH7XXtgBRjqceS8wRC9N3tHVy6fExWpMlq50PluLUl0zVbRBuJcnyjb36fbmxppTCbqv4y4NCCce7rm7vvsxeRNlDMCJVRJtS9NJ8TA8ikZDqR+tPIqsPthyJ/pjFD371ie6s9hwceFfZD6IagSBz1zkrmBzp0bsoXwyTHzOg= Received: by 10.54.56.47 with SMTP id e47mr68587wra; Wed, 15 Dec 2004 08:24:16 -0800 (PST) Received: by 10.54.46.34 with HTTP; Wed, 15 Dec 2004 08:24:16 -0800 (PST) Message-ID: <6e01203b041215082450e6f894@mail.gmail.com> Date: Wed, 15 Dec 2004 09:24:16 -0700 From: Tyler Gee To: David Adam In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41BDC787.40000@daleco.biz> cc: "R. Scott Kennan" cc: freebsd-newbies@freebsd.org Subject: Re: Home Network, step by step? X-BeenThere: freebsd-newbies@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tyler Gee List-Id: Gathering place for new users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 16:24:17 -0000 I would also recommend going with pf. As David said, the documentation is fantastic, it can do a myriad of things and is (IMO) quickly going to become the standard. The pf documentation includes three common scenarios, one of which is a home network with port forwarding, so you shouldn't have problems. Also, check out bsdforums.org and just do a search and you will find a lot of things. -wtgee On Wed, 15 Dec 2004 09:11:32 +0800 (WST), David Adam wrote: > On Tue, 14 Dec 2004, R. Scott Kennan wrote: > > > One other thing I don't understand is why I'm being told to install > > the firewall in this context; are firewalls more than just an > > intrusion countermeasure? Do they do any 'lifting' on a network beyond > > blocking unauthorised transfers? > > They do now. > > Partly in response to cleverer security threats, and partly as a > convergence between routing and firewalling, most modern firewalls - like > ipf and pf in FreeBSD - are now not so much firewalls, but packet filters. > They have the ability to inspect and modify any packets going in any > direction on various interfaces. This makes them an invaluable tool on > routers in any environment (except, perhaps, Internet core routers, but > they're another case entirely). > > By the way, someone up the thread a bit recommended you start running > IPFW (IPFIREWALL). While I'm not currently in a position to give you > instructions as detailed as James did, I would recommend you start with > either ipf or pf. IPFW is much older and is somewhat less well maintained, > the documentation in particular. > > >From the Handbook's IPFW Chapter... > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html > > "The IPFW stateless rule syntax is empowered with technically > sophisticated selection capabilities which far surpasses the knowledge > level of the customary firewall installer. IPFW is targeted at the > professional user or the advanced technical computer hobbyist who have > advanced packet selection requirements." > > (Proper use of freebsd-newbies@ approaching!) > > I've had superb results with pf (although for full effect, it will require > a kernel rebuild). The pf documentation at OpenBSD is very well written > and easy to follow. Setting up NAT can be a somewhat daunting task > (personally, I do it at home with Windows' ICS, which is an absolute > no-brainer) - however, once you get it working it is extremely useful. > > Best of luck! (I really should get back to work - if I can get my system > at home logged on to the 'net I'll try and run you through the basics of > setting it up if you still need it.) > > Cheers, > > David Adam > --- > zanchey@ucc.gu.uwa.edu.au > Medicine: And you thought hacking computers was complex. > > _______________________________________________ > freebsd-newbies@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-newbies > To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org" >