From owner-freebsd-current Mon Sep 18 1: 9:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.66]) by hub.freebsd.org (Postfix) with ESMTP id 18C8837B423 for ; Mon, 18 Sep 2000 01:08:45 -0700 (PDT) Received: from jarrow.dev.nanoteq.co.za (jarrow [196.37.91.33]) by oskar.nanoteq.co.za (8.9.3/8.9.0) with ESMTP id KAA06384; Mon, 18 Sep 2000 10:09:49 +0200 (SAT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000916202011C.sakane@ydc.co.jp> Date: Mon, 18 Sep 2000 10:05:53 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: snap-users@kame.net Subject: RE: (KAME-snap 3327) Re: Panic on current (12 Sept) Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... Without starting the racoon daemon and doing a secure connect everything works fine without a problem. If I start racoon, do a tunnel connection and then run daily, the machine panics .. Reinier On 16-Sep-00 Shoichi 'Ne' Sakane wrote: >> I'm running a current machine of 12 Sept although this problem >> also occured on a current of a few days earlier ... >> >> This only happens when using the IPv6 IPSec code during the day, >> it is readily reproduceable. >> >> If during the day I load the racoon daemon and load keys and >> establish a IPSec tunnel connection everything works fine till >> 2:00 am when the daily script runs OR if I run the daily script >> by hand ... I generated the following dump and backtrace ... >> >> It seems to crash in a makedev routine using FOREACH list macro's. >> >> The problem doesn't seem to be with the list or the makedev function >> in kern_conf.c. It seems to me that something in the kernel >> corrupts the static list dev_hash when using the IPSec code. >> >> Summary - when ising IPSec ... machine panics during daily >> script execution. > > I think IPsec is not relative to this issue. To make sure, > does your machine run healthy without IPsec ? > Please try the following. > case 1) with option IPSEC, but no SPD entry. > case 2) without option IPSEC ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 18-Sep-00 Time: 10:04:59 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message