From owner-freebsd-ipfw Fri Jan 19 10:40:11 2001 Delivered-To: freebsd-ipfw@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 4E60937B402 for ; Fri, 19 Jan 2001 10:39:54 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0JIdli07445; Fri, 19 Jan 2001 10:39:47 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101191839.f0JIdli07445@iguana.aciri.org> Subject: Re: upgrading to 4.2 was a bad idea In-Reply-To: <000001c08245$f7c34de0$fadef9ce@rjstech.com> from Carlos Andrade at "Jan 19, 2001 11:30:58 am" To: carlos@rjstech.com Date: Fri, 19 Jan 2001 10:39:47 -0800 (PST) Cc: ipfw@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there is no bug in the system. The errors that people mentioned were just due to those people not doing the upgrade properly -- i.e. misalignment between the header files used by the kernel and those used by userland programs in /usr/include/*/ (specifically netinet/) cheers luigi > Ipfw was giving the same errors that people have mentioned on this list. I > have not seen any other debate on this anywhere. The FreeBSD web site has > nothing on this. Any ideas why this happened and how it can be fixed? > ipfw: getsockopt(I{_FW_ADD)): Protocol not available > > ---- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message