From owner-freebsd-questions@FreeBSD.ORG Thu Oct 16 00:13: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 3FCA81065688 for ; Thu, 16 Oct 2008 00:13:22 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from mail.unitedinsong.com.au (202-172-126-254.cpe.qld-1.comcen.com.au [202.172.126.254]) by mx1.freebsd.org (Postfix) with ESMTP id DD64A8FC0A for ; Thu, 16 Oct 2008 00:13:21 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.185] (unknown [192.168.0.185]) by mail.unitedinsong.com.au (Postfix) with ESMTP id E1F344056 for ; Thu, 16 Oct 2008 10:13:30 +1000 (EST) From: Da Rock To: freebsd-questions@freebsd.org In-Reply-To: <20081015111026.GA75598@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> Content-Type: text/plain Date: Thu, 16 Oct 2008 10:15:49 +1000 Message-Id: <1224116149.3458.39.camel@laptop1.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit 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 00:13:22 -0000 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)