From owner-freebsd-questions@FreeBSD.ORG Mon Feb 13 14:21:33 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6284E16A420 for ; Mon, 13 Feb 2006 14:21:33 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DA2143D64 for ; Mon, 13 Feb 2006 14:21:32 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 16030 invoked from network); 14 Feb 2006 01:21:32 +1100 Received: from 203-217-43-43.dyn.chime.net.au (HELO ?192.168.13.3?) (203.217.43.43) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Feb 2006 01:21:32 +1100 Message-ID: <43F095E6.2070901@meijome.net> Date: Tue, 14 Feb 2006 01:21:26 +1100 From: Norberto Meijome User-Agent: Thunderbird 1.5 (X11/20060206) MIME-Version: 1.0 To: Brian Bobowski References: <43F0935B.4020901@gmail.com> In-Reply-To: <43F0935B.4020901@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD User Questions List Subject: Re: Firewall/Web server difficulties 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: Mon, 13 Feb 2006 14:21:33 -0000 Brian Bobowski wrote: > All right. I've got my firewall up and running, and my workstation can > get almost anywhere it needs to just fine. you dont' say if you are using ipfw, ipf , pf.... > I can access it by directly referencing the private-interface IP, but if > my workstation tries to get to the public-interface IP, nothing happens. > Can't even ping it. ICMP and port 80 TCP should both be allowed from > anywhere... but they're not getting through. (Assuming all your rules are ok...) AFAIK, you can't access the external interface of a NAT'ed system from the LAN side. Simply use a DNS inside that resolves the name you try to access to the internal interface instead of the external. this is FAQ, i think... > (So far as I can tell, it's > not just me who's unable to access these.) meaning others in your LAN? or others in the WAN? > Does NAT simply not allow for servers to be running on the machine that > performs it? I know it's not ideal, but I don't have the room to install > another machine even if that were in my budget. I've set up NAT and IPFW > per the directions in the handbook, and aside from that one difficulty, > everything seems to be working. > > Please reply off the list. CCing the list for the benefit of everyone else :) Beto