From owner-freebsd-questions@FreeBSD.ORG Tue Nov 16 06:07:43 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECEA616A4CE for ; Tue, 16 Nov 2004 06:07:43 +0000 (GMT) Received: from sxm.trinetworks.com (sxm.trinetworks.com [64.73.235.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB01343D45 for ; Tue, 16 Nov 2004 06:07:43 +0000 (GMT) (envelope-from freebsd@trinetworks.com) Received: from sxm.trinetworks.com (localhost.trinetworks.com [127.0.0.1]) by sxm.trinetworks.com (8.12.10/8.12.10) with ESMTP id iAG6EXtb044615; Mon, 15 Nov 2004 22:14:33 -0800 (PST) (envelope-from freebsd@trinetworks.com) Received: (from nobody@localhost) by sxm.trinetworks.com (8.12.10/8.12.10/Submit) id iAG6EVT4044614; Mon, 15 Nov 2004 22:14:31 -0800 (PST) (envelope-from freebsd@trinetworks.com) X-Authentication-Warning: sxm.trinetworks.com: nobody set sender to freebsd@trinetworks.com using -f Received: from 24-25-209-32.san.rr.com ([24.25.209.32]) (SquirrelMail authenticated user freebsd); by mail.trinetworks.com with HTTP; Mon, 15 Nov 2004 22:14:31 -0800 (PST) Message-ID: <1733.24.25.209.32.1100585671.squirrel@24.25.209.32> In-Reply-To: <20041116031937.GA32097@xor.obsecurity.org> References: <200411160054.39582.giulianocm@uol.com.br> <20041116031937.GA32097@xor.obsecurity.org> Date: Mon, 15 Nov 2004 22:14:31 -0800 (PST) From: "Matthew T. Lager" To: "Kris Kennaway" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: Giuliano Cardozo Medalha cc: freebsd-questions@freebsd.org Subject: Re: MPSAFE - Warning X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 06:07:44 -0000 I too receive this error. I require the use of KAME IPSEC. Basiclly, services such as IPV6 and IPSEC require the kernel to be GIANT locked, which is incompatable with MPSAFE. 5.3 forces MPSAFE to 0 if the system is GIANT locked, hence the warning. I backed down to 5.2.1 and ran IPSEC with no problems. I actually did experience many issues with my IPSEC tunnel in 5.3. I beleive a GIANT FREE IPV6/IPSEC implementation is a requirement for the 5.4 release, hopefully we see it soon in the -STABLE tree, keep an eye on freebsd.org/releng as it is listed as a project in the TODO list (at least for IPSEC)... Matthew T. Lager > On Tue, Nov 16, 2004 at 12:54:39AM -0200, Giuliano Cardozo Medalha wrote: >> Hi, >> >> I got some messages for my customized kernel, using IPsec and IPv6: >> >> WARNING: MPSAFE network stack disabled, expect reduced performance. >> >> My kernel have the following option: >> >> options NET_WITH_GIANT >> >> How is possible to correct this warning > > Wait for a later release, or disable IPv6 :-) > > IPv6 is not yet MP-safe. > > Kris >