From owner-freebsd-net@FreeBSD.ORG Wed Sep 29 08:15:22 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E646D16A4CE for ; Wed, 29 Sep 2004 08:15:22 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 221BD43D1F for ; Wed, 29 Sep 2004 08:15:21 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (shuttle.wide.toshiba.co.jp [3ffe:501:100f::35]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id BB2201525D; Wed, 29 Sep 2004 17:14:59 +0900 (JST) Date: Wed, 29 Sep 2004 17:14:56 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: snap-users@kame.net In-Reply-To: References: User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: (KAME-snap 8815) Re: Weird memory exhaustion with FreeBSD 4.10-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 08:15:23 -0000 >>>>> On Wed, 29 Sep 2004 10:59:32 +0300 (EEST), >>>>> Pekka Savola said: >> Okay. Now I think I figure out the problem. Those host routes were >> created not deliberately, so the kernel will eventually need a fix to >> this. >> >> But if you are in a hurry and/or cannot replace the kernel soon, I >> think setting net.inet6.ip6.rtexpire to 0 can be a workaround (with >> this you even do not have to reboot the kernel - though rebooting may >> also help if you can). > Warning: this freezed the system immediately [all network connectivity > broke, and I had to do a quick reset]. Maybe I should have set it up > at reboot before the system was in a 'bad' shape.. Sorry for the trouble, but could you be more specific on "freeze"? Does it mean the kernel hanged (you could not type anything from the keyboard, etc)? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp