From owner-freebsd-chat@FreeBSD.ORG Fri Jul 28 20:00:16 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 5FDE416A4DD for ; Fri, 28 Jul 2006 20:00:16 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985FA43D45 for ; Fri, 28 Jul 2006 20:00:15 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.7/8.13.7) with ESMTP id k6SK03Tb009179 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 28 Jul 2006 22:00:14 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <28745bbf0607281005t77d676a5ge7e5e8fcf1ea280e@mail.gmail.com> References: <28745bbf0607270947i6d71369fg5c1403b2d6e36219@mail.gmail.com> <980FE9AA-8300-4019-BAEE-7B7C0708526D@lassitu.de> <28745bbf0607281005t77d676a5ge7e5e8fcf1ea280e@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <007D57CF-0D72-4579-8FC8-7E66C54ACEFD@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Fri, 28 Jul 2006 22:00:03 +0200 To: Adam Egan X-Mailer: Apple Mail (2.752.2) Cc: freebsd-chat@freebsd.org 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 20:00:16 -0000 Am 28.07.2006 um 19:05 schrieb Adam Egan: >> 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. Sorry, I missed that. If you can post tcpdump traces from both the inside and the outside interface while trying to connect to port 80, there might be a chance to spot the problem. The natd config seems to be fine. Stefan -- Stefan Bethke Fon +49 170 346 0140