From owner-freebsd-stable@FreeBSD.ORG Fri Apr 28 14:57:50 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90CA216A414 for ; Fri, 28 Apr 2006 14:57:50 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout06-04.prod.mesa1.secureserver.net (smtpout06-01.prod.mesa1.secureserver.net [64.202.165.224]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B3B143D5C for ; Fri, 28 Apr 2006 14:57:50 +0000 (GMT) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 16656 invoked from network); 28 Apr 2006 14:57:49 -0000 Received: from unknown (24.144.77.138) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 28 Apr 2006 14:57:49 -0000 Message-ID: <44522D6C.3000107@seclark.us> Date: Fri, 28 Apr 2006 10:57:48 -0400 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Fast IPSEC issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 14:57:50 -0000 Hello List, I am running throughput test between to Athlon 64 X2 with Stable 6.x 386 mode. I have 100 vpns and 100 gre tunnels. The gres go thru the vpns. I am using nttcp to do the the thruput testing. When I use FAST_IPSEC I get better performance than standard ipsec but I also get a lot of the following messages: Apr 28 10:44:48 J301001 kernel: gre45: gre_output: recursively called too many t imes(2) Apr 28 10:44:54 J301001 kernel: gre58: gre_output: recursively called too many t imes(2) Apr 28 10:44:54 J301001 kernel: gre95: gre_output: recursively called too many t imes(2) Apr 28 10:44:58 J301001 kernel: gre80: gre_output: recursively called too many t imes(2) Apr 28 10:44:59 J301001 kernel: gre67: gre_output: recursively called too many t imes(2) Apr 28 10:45:04 J301001 kernel: gre73: gre_output: recursively called too many t imes(2) Apr 28 10:45:08 J301001 kernel: gre64: gre_output: recursively called too many t imes(2) Apr 28 10:45:19 J301001 kernel: gre20: gre_output: recursively called too many t imes(2) Apr 28 10:45:19 J301001 kernel: gre54: gre_output: recursively called too many t imes(2) Apr 28 10:45:24 J301001 kernel: gre72: gre_output: recursively called too many t imes(2) Apr 28 10:45:28 J301001 kernel: gre14: gre_output: recursively called too many t imes(2) Apr 28 10:45:28 J301001 kernel: gre50: gre_output: recursively called too many t imes(2) Apr 28 10:47:24 J301001 kernel: gre4: gre_output: recursively called too many ti mes(2) Any ideas why this might be happening with FAST_IPSEC? Should I go back to the standard kame ipsec? Thanks for your insight, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson)