From owner-freebsd-questions@FreeBSD.ORG Tue Nov 1 17:49:02 2005 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 A3CAB16A41F for ; Tue, 1 Nov 2005 17:49:02 +0000 (GMT) (envelope-from jwm-freebsd@sentinelchicken.net) Received: from dukecmmtar02.coxmail.com (dukecmmtar02.coxmail.com [68.99.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A9A943D45 for ; Tue, 1 Nov 2005 17:49:01 +0000 (GMT) (envelope-from jwm-freebsd@sentinelchicken.net) Received: from sentinelchicken.net ([70.183.13.213]) by dukecmmtar02.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20051101174925.PPEF1549.dukecmmtar02.coxmail.com@sentinelchicken.net> for ; Tue, 1 Nov 2005 12:49:25 -0500 Received: (qmail 91562 invoked by uid 1000); 1 Nov 2005 17:49:00 -0000 Date: Tue, 1 Nov 2005 12:49:00 -0500 From: Jason Morgan To: FreeBSD Questions Message-ID: <20051101174900.GB91422@sentinelchicken.net> References: <20051101171540.GA91080@sentinelchicken.net> <20051101183716.44ebc62b@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051101183716.44ebc62b@localhost> User-Agent: Mutt/1.4.2.1i Subject: Re: Quick Routing Question 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: Tue, 01 Nov 2005 17:49:02 -0000 On Tue, Nov 01, 2005 at 06:37:16PM +0100, Fabian Keil wrote: > Jason Morgan wrote: > > > On Tue, Nov 01, 2005 at 11:24:59AM -0500, Steve Bertrand wrote: > > > > And again, tcpdump is a very good tool. The -i switch tells it what > > > interface to listen on, so if the wireless side of the router works > > > but you can't ping across to the cabled side, then apply the cabled > > > interface to the -i switch and you'll be able to see if traffic is > > > making that far, and if it is, if it's even attempting to go back. > > > > Ok, it looks like it was an issue with the default settings on the > > Linksys (and is still somewhat of an issue). I can now connect to > > systems in each of the two subnets and I also have routing to the > > outside world from both subnets. My only remaining issue is getting > > to the web app setup for the Linksys - I can only do it from a local > > address (meaning a 192.168.1.x address). The Linksys refuses > > connections from my 10.0.0.x subnet. Is this a NAT issue? > > Do you have NAT enabled between 192.168.1.0 and 10.0.0.0? > If you do, the Linksys shouldn't see any 10.0.0.x addresses. > > If you don't, this is probably a security measure. > Perhaps the Linksys supports a white list to > allow access from non-local addresses. I never explicity set the FreeBSD machine to enable NAT between these subnets. Should I do so? Do I just add another natd_interface to rc.conf? Right now, the NAT related entries in rc.conf on the gateway look like this: natd_enable="YES" natd_interface="xl0" #public interface natd_flags="-dynamic -m" Thanks again, Jason > > Fabian > -- > http://www.fabiankeil.de/