From owner-freebsd-questions Thu Oct 22 10:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00937 for freebsd-questions-outgoing; Thu, 22 Oct 1998 10:56:48 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00928 for ; Thu, 22 Oct 1998 10:56:43 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA10577; Thu, 22 Oct 1998 10:56:07 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Oct 1998 10:56:06 -0700 (PDT) From: Doug White To: Dan Langille cc: freebsd-questions@FreeBSD.ORG Subject: Re: ipfw and natd confusion In-Reply-To: <199810202029.JAA25519@cyclops.xtra.co.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Oct 1998, Dan Langille wrote: > > 00700 deny ip from any to 192.168.0.0/16 via ed0 > > > > This rule prevents me from connecting to the outside world. For some > > reason, it doesn't allow me to, say, connect to my ISP news server. Is > > natd screwing up somewhere? > > I've found that the above rule is part of the standard rules for compling > with RFC 1918 which defines which networks should not be routed. So why > does that stop all my traffic from getting out? > > However, if I slight modify the rule, the problem goes away. Is this an > ipfw bug? No, it's ipfw doing it's job, probably; eating the local network packets. :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message