From owner-freebsd-chat@FreeBSD.ORG Fri Jul 28 17:05:21 2006 Return-Path: X-Original-To: freebsd-chat@freebsd.org Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E14EC16A4DE for ; Fri, 28 Jul 2006 17:05:21 +0000 (UTC) (envelope-from adam.egan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id DED2743D55 for ; Fri, 28 Jul 2006 17:05:20 +0000 (GMT) (envelope-from adam.egan@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so247074nfc for ; Fri, 28 Jul 2006 10:05:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=F70py1txaQ2VF0ZbF+y3L8zVcw4I6ccG36OnVQmxGffmInoLG71/0g7LdNtSGDlizus7b0RrggbhSicYix+Zj/CD3rjM3JEqcxnltPHnzcNJoPSi8D34x/IbXBVp6H9ezMRBN1M4Kwx7ZrGDeUQxREuRo8e1PWQcOc0x8HnshLk= Received: by 10.48.80.20 with SMTP id d20mr928847nfb; Fri, 28 Jul 2006 10:05:19 -0700 (PDT) Received: by 10.48.207.18 with HTTP; Fri, 28 Jul 2006 10:05:18 -0700 (PDT) Message-ID: <28745bbf0607281005t77d676a5ge7e5e8fcf1ea280e@mail.gmail.com> Date: Fri, 28 Jul 2006 18:05:18 +0100 From: "Adam Egan" To: freebsd-chat@freebsd.org In-Reply-To: <980FE9AA-8300-4019-BAEE-7B7C0708526D@lassitu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <28745bbf0607270947i6d71369fg5c1403b2d6e36219@mail.gmail.com> <980FE9AA-8300-4019-BAEE-7B7C0708526D@lassitu.de> Subject: Re: ipfw and natd routing problems X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 17:05:22 -0000 > natd needs to work on both incoming and ooutgoing connections. > Dropping the "in" keyword should do the trick. Hi Stefan, as I said in my original email, outgoing connections work fine, it is the incoming connections which natd is supposed to foward to other computers which doesn't work. > My only problem now is that although connections going out through natd work fine, > natd port forwarding does not work correctly. I have however altered the rule as you instructed, thank you for pointing out that error. Adam