From owner-freebsd-questions Mon Apr 30 16:20:46 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nameserver.austclear.com.au (nameserver.austclear.com.au [192.83.119.132]) by hub.freebsd.org (Postfix) with ESMTP id 659B537B422 for ; Mon, 30 Apr 2001 16:20:40 -0700 (PDT) (envelope-from ahl@austclear.com.au) Received: from tungsten.austclear.com.au (tungsten.austclear.com.au [192.168.70.1]) by nameserver.austclear.com.au (8.9.3/8.9.3) with ESMTP id JAA09765; Tue, 1 May 2001 09:20:36 +1000 (EST) Received: from tungsten (tungsten [192.168.70.1]) by tungsten.austclear.com.au (8.9.3/8.9.3) with ESMTP id JAA03188; Tue, 1 May 2001 09:20:36 +1000 (EST) Message-Id: <200104302320.JAA03188@tungsten.austclear.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: kevin Cc: freebsd-questions@FreeBSD.ORG Subject: Re: routing troubles In-Reply-To: Message from kevin of "Sun, 29 Apr 2001 17:59:38 MST." <3AECB8FA.7F7E1CF1@cco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 May 2001 09:20:36 +1000 From: Tony Landells Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG kevinm@cco.net said: > I did use natd and ipfw. From the Windows box (192.168.1.101) I can > ping the inside ip of the FreeBSD box (192.168.1.100) and the outside > ip of the FreeBSD box (209.102.16.38) but I can't ping the router > (209.102.16.33) or any other ip address beyond the > router. Well, if you can ping the outside address of the FreeBSD box, I'm assuming that the Windows box has the correct default gateway set (as in, the internal address of the FreeBSD box)? But if you can't get any further, I'm betting on a natd/ipfw problem. For a start, run natd (from the command prompt) with the "-v" option which will show you all the packets it processes. If you don't get any output, you're not giving the packets to natd for translation. If you do get output but it's not changing anything, then natd is misconfigured. The other thing worth doing is putting a "log" option on every ipfw rule that denies packets. That way, if you're doing something you want to allow and you're getting log messages you know you have ipfw misconfigured. Once you have things working properly you can always remove the "log" option to reduce the disk space required for logging. Cheers, Tony -- Tony Landells Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message