From owner-freebsd-current  Fri Mar  3 22:23: 4 2000
Delivered-To: freebsd-current@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id 0EB5A37B5E0
	for <current@freebsd.org>; Fri,  3 Mar 2000 22:23:00 -0800 (PST)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id PAA12486;
	Sat, 4 Mar 2000 15:22:48 +0900 (JST)
To: "Louis A. Mamakos" <louie@TransSys.COM>
Cc: current@freebsd.org
In-reply-to: louie's message of Fri, 03 Mar 2000 19:47:27 EST.
      <200003040047.TAA02376@whizzo.transsys.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: IPSec in 4.0-current questions..
From: itojun@iijlab.net
Date: Sat, 04 Mar 2000 15:22:48 +0900
Message-ID: <12484.952150968@coconut.itojun.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>I've been messing about with IPSEC in 4.0-current, and have observed some
>unexpected behavior.  Is there someone I can swap some email with off
>the list to determine if what I'm seeing is a bug, or I'm just confused?
>It has to do with security policy specifications and what SAID is being
>selected when a TCP connection is being opened.

	could you try sending details to snap-users@kame.net (KAME users
	mailing list, you may want to subscribe it - see www.kam.enet).

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message