From owner-freebsd-questions Thu May 6 11:18:29 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id E91491587B for ; Thu, 6 May 1999 11:18:27 -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 LAA17812; Thu, 6 May 1999 11:18:24 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 6 May 1999 11:18:24 -0700 (PDT) From: Doug White To: Kevin Bogac Cc: freebsd-questions@FreeBSD.ORG Subject: Re: natd question In-Reply-To: <001c01be9766$cf4979f0$0701a8c0@ibm.net> 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, 5 May 1999, Kevin Bogac wrote: > I cannot get natd to work. I have searched through all of the > information I can find and my configuration seems correct. If I enable > natd the interface blocks traffic. I'm getting a line in the system > messages that says "/kernel: IP packet filtering initialized, divert > disabled, rule-based forwarding disabled, logging disabled". I built > the kernel with the two additional options. Did I miss something? Does > the default rc.firewall work? You need to build a kernel with these options: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPDIVERT #divert sockets The ipfw KLD doesn't ship with divert turned on, which you need to make natd work. 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