From owner-freebsd-ipfw Wed Aug 9 21:10:53 2000 Delivered-To: freebsd-ipfw@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 439AE37B84A for ; Wed, 9 Aug 2000 21:10:50 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id WAA53762; Wed, 9 Aug 2000 22:10:02 -0600 (MDT) Date: Wed, 9 Aug 2000 22:10:02 -0600 (MDT) From: Nick Rogness To: TeRrAc Cc: FreeBSD IPFW list Subject: Re: natd + IPFW In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, TeRrAc wrote: > So from all the replies I have recieved, i get the feeling that my natd > is setup correctly, and the deault rules are okie.. > I am wondering what it could be that is keeping my hosts on the inside > from pining the outside world. > Undoubtedly it is something really simple, as are most things. the only > question is what is it? To see what is causing your problems, Take the 'natd_flag' line out of rc.conf. I don't think they would be the culprit but I have never used the "-u" option so I don't know what effects that would cause, plus it would take another "possible" out of the equation. IPFIREWALL_FORWARD should not be causing the problem. Also, Try pinging from your BSD machine to the outside without the divert rule in the firewall, just to see if connectivity is working. Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message