From owner-freebsd-questions@FreeBSD.ORG Thu Oct 16 04:19:22 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2295106568E for ; Thu, 16 Oct 2008 04:19:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id B221A8FC18 for ; Thu, 16 Oct 2008 04:19:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by QMTA01.emeryville.ca.mail.comcast.net with comcast id T7oB1a00P0b6N64A1GKNST; Thu, 16 Oct 2008 04:19:22 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA03.emeryville.ca.mail.comcast.net with comcast id TGKM1a0032P6wsM8PGKMF5; Thu, 16 Oct 2008 04:19:22 +0000 X-Authority-Analysis: v=1.0 c=1 a=Hhtsdv2kQ0QA:10 a=7q5sDk5WlpcA:10 a=QycZ5dHgAAAA:8 a=uHt_XG2qWOF7c5bA2hUA:9 a=3xxnsENx8-Bkb3epgF8A:7 a=ULfUgGqJzHsGvZncnlM5JUiYY10A:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 1814BC9419; Wed, 15 Oct 2008 21:19:21 -0700 (PDT) Date: Wed, 15 Oct 2008 21:19:21 -0700 From: Jeremy Chadwick To: Da Rock Message-ID: <20081016041921.GA99978@icarus.home.lan> References: <48F43EB1.40304@gmail.com> <20081014101733.GA47158@icarus.home.lan> <1224067248.3458.34.camel@laptop1.herveybayaustralia.com.au> <20081015111026.GA75598@icarus.home.lan> <1224116149.3458.39.camel@laptop1.herveybayaustralia.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1224116149.3458.39.camel@laptop1.herveybayaustralia.com.au> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-questions@freebsd.org Subject: Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system 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: Thu, 16 Oct 2008 04:19:23 -0000 On Thu, Oct 16, 2008 at 10:15:49AM +1000, Da Rock wrote: > > On Wed, 2008-10-15 at 04:10 -0700, Jeremy Chadwick wrote: > > On Wed, Oct 15, 2008 at 08:40:48PM +1000, Da Rock wrote: > > > > > > On Tue, 2008-10-14 at 06:46 -0400, Michael Powell wrote: > > > > Jeremy Chadwick wrote: > > > > > > > > > On Tue, Oct 14, 2008 at 04:55:11AM -0400, Michael Powell wrote: > > > > [snip] > > > > >> Next, you will want to configure your FreeBSD machine as a NAT gateway. > > > > >> In your /etc/rc.conf you will want something like gateway_enable="YES" > > > > >> and some form of firewall initialization[1]. The gateway_enable is what > > > > >> allows the forwarding of packets between your rl0 and your rl1, but the > > > > >> activation of NAT functionality is usually a function contained within a > > > > >> firewall. So conceptually, the firewall will be "in between" rl0 and rl1. > > > > >> > > > > >> There are three different firewalls you can choose from. Configuring the > > > > >> firewall is usually where the inexperienced get stuck. This subject > > > > >> material is beyond the scope of this missive, and you would do well to > > > > >> start reading in the Handbook. But essentially, when you configure NAT in > > > > >> the firewall your rl0 (connected to the ISP) will be assigned a "Public" > > > > >> IP address and the NAT function will translate between "Public" and > > > > >> "Private". > > > > > > > > With respect to "NAT", the caveat here is the assumption that your DSL/Cable > > > > modem is *not* already performing NAT. The situation you do not want to get > > > > into is having *two* NATs. The content herein is assuming that the external > > > > (rl0) interface is getting assigned a "Public" IP from the ISP. > > > > > > > > > > If this is the case wouldn't the OP set router_enable=YES instead of > > > gateway? > > > > No. router_enable causes routed(8) to run, which allows for > > announcements and withdraws of network routes via RIPv1/v2. This is > > something completely different than forwarding packets. > > > > What the OP wants is to route packets from his private LAN (e.g. > > 192.168.0.0/16) on to the Internet using NAT. That means he has to have > > a NAT gateway of some kind that forwards and translates packets. That > > means he needs gateway_enable="yes", which allows IPv4 forwarding > > to happen "through" the FreeBSD box. In layman's terms, it allows > > the FreeBSD box to be used a "Gateway" for other computers which > > are connected to it directly. > > > > Ok, then. So it would be gateway_enable, but no nat_enable? (To avoid > double nat'ing) Do you mean firewall_nat_enable, natd_enable, or ipnat_enable? :-) See /etc/defaults/rc.conf. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |