From owner-freebsd-security Wed Nov 8 18:43:10 2000 Delivered-To: freebsd-security@freebsd.org Received: from aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (Postfix) with ESMTP id 4259B37B4C5; Wed, 8 Nov 2000 18:43:04 -0800 (PST) Received: from frankenputer (frankenputer [172.29.58.2]) by aussie.org (8.11.1/8.11.1) with SMTP id eA92gsV02821; Thu, 9 Nov 2000 13:43:00 +1100 (EST) (envelope-from casonc@netplex.aussie.org) Message-ID: <001501c049f6$c578baa0$023a1dac@dsat.net.au> From: "Chris Cason" To: "Kris Kennaway" Cc: References: <5.0.0.25.0.20001108115420.076aeeb0@marble.sentex.ca> <003c01c049f1$b24bec40$023a1dac@dsat.net.au> <20001108181234.A1768@citusc17.usc.edu> Subject: Re: IPSEC tunnels fail with -stable kernel? Date: Thu, 9 Nov 2000 13:42:49 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Manual. Everything is done using the setkey utility; I don't use GIF or >> anything else. The tunnels just *stopped* the instant I put in the new >> kernel. >Did you build world with the same sources? It may be one of the usual >class of problems with userland/kernel being out of sync. Yes, I used cvsup to grab the latest stable sources immediately before doing the build on all of the systems, and did a buildkernel, installkernel and make world as per normal. -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message