From owner-freebsd-ipfw Wed Jan 24 8: 8:38 2001 Delivered-To: freebsd-ipfw@freebsd.org Received: from new-dns.whc.net (new-dns.whc.net [204.90.111.214]) by hub.freebsd.org (Postfix) with ESMTP id 6FB8137B401 for ; Wed, 24 Jan 2001 08:08:21 -0800 (PST) Received: from null ([206.249.222.250]) by smtp.whc.net (8.11.2/8.10.1/kbp) with SMTP id for ; Wed, 24 Jan 2001 09:07:17 -0700 (MST) Reply-To: From: "Carlos Andrade" To: Subject: RE: ipfw problems with 4.2 upgrade Date: Wed, 24 Jan 2001 09:03:28 -0700 Message-ID: <001001c0861f$30c37d40$fadef9ce@rjstech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010123205455.W10761@rfx-216-196-73-168.users.reflex> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Jan 23, 2001 at 12:58:59PM -0700, Carlos Andrade wrote: > > IPFIREWALL is set in my kernel, I re-built it thinking that was the > > problems. I still get the errors at start up : > > > > ipfw: getsockopt(I{_FW_ADD)): Protocol not available > > Show the dmesg(8). > -- > Crist J. Clark cjclark@alum.mit.edu Okay, lots of info but here is the important stuff : IP packet filtering initialized, divert enabled, rule-based forwarding disabled (WHAT?), default to deny, logging limited to 50 packets/entries by default. Everything but the rule-based forwarding being disabled sounds right. Hmm this is a bad thing. No clue where to look other than rc.conf. -Carlos Andrade ---- Carlos A. Andrade IS Manager RJS Technologies 915.845.5228 ext 13 915.845.2119 fax carlos@rjstech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message