From owner-freebsd-questions Mon Apr 23 20:38:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from grumpy.dyndns.org (user-24-214-76-217.knology.net [24.214.76.217]) by hub.freebsd.org (Postfix) with ESMTP id 33E2937B43E for ; Mon, 23 Apr 2001 20:38:31 -0700 (PDT) (envelope-from dkelly@grumpy.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.3/8.11.3) with ESMTP id f3O3cK304978; Mon, 23 Apr 2001 22:38:20 -0500 (CDT) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200104240338.f3O3cK304978@grumpy.dyndns.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Nick Rogness Cc: Brad , freebsd-questions@FreeBSD.ORG From: David Kelly Subject: Re: IPFW Protocol not available ? In-reply-to: Message from Nick Rogness of "Sun, 22 Apr 2001 23:55:45 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Apr 2001 22:38:20 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Rogness writes: > On Sun, 22 Apr 2001, Brad wrote: > > > Hi there, > > > > I just recompiled my kernel and rebooted with the following option on > > Version 4.2: > > > > options IPFIREWALL_VERBOSE_LIMIT=10 > > > > When I attempt to pass ipfw a command, I get a "Protocol Not Available" > > error? Does anyone know why this might be happening? > > You forgot a statement in your kernel: > > options IPFIREWALL Or you could add "firewall_enable=YES" in /etc/rc.conf, or you could manually type: # kldload ipfw -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message