From owner-freebsd-net@FreeBSD.ORG Fri Sep 9 04:09:37 2005 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 CA57116A41F for ; Fri, 9 Sep 2005 04:09:37 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7229643D45 for ; Fri, 9 Sep 2005 04:09:37 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id B93B75D28; Fri, 9 Sep 2005 00:09:36 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24702-02; Fri, 9 Sep 2005 00:09:35 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 689625C84; Fri, 9 Sep 2005 00:09:35 -0400 (EDT) Message-ID: <43210B01.4040801@mac.com> Date: Fri, 09 Sep 2005 00:09:37 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephen Moore References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-net@freebsd.org Subject: Re: NAT over multiple subnets 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: Fri, 09 Sep 2005 04:09:37 -0000 Stephen Moore wrote: [ ...chaining multiple NATs... ] > Any response appreciated. The simplest way to deal with that is to add interfaces to the machine running natd and put one NIC on each distinct subnet. You can also use supernetting to combine a 192.168.1.0/24 subnet and a 192.168.2.0/24 subnet by giving your natd box a /22 netmask instead. You might also need to set up a route pointing to the 192.168.1.0/24 subnet on the natd box, so it knows where to send the traffic. -- -Chuck