Date: Tue, 13 Aug 2002 13:31:17 -0700 From: "Crist J. Clark" <crist.clark@attbi.com> To: Julian Elischer <julian@elischer.org> Cc: Julian Elischer <julian@vicor.com>, net@FreeBSD.ORG Subject: Re: Racoon question Message-ID: <20020813203117.GD5009@blossom.cjclark.org> In-Reply-To: <Pine.BSF.4.21.0208122240080.13960-100000@InterJet.elischer.org> References: <20020813052619.GD1675@blossom.cjclark.org> <Pine.BSF.4.21.0208122240080.13960-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 12, 2002 at 10:42:42PM -0700, Julian Elischer wrote:
[snip]
> > This actually is not the problem. IKE/IPsec implementations have to be
> > smart enough to handle the negotiations "OOB."
>
> So how does racoon talk "OOB"? does it add it's own SA?
> how does it stop it's own packets from being thrown away at the
> far end when they are not encrypted correctly for the transport layer
> ipsec?
I believe racoon(8) does it by forcing a "bypass" policy on the socket
it opens for the ISAKMP negotiations.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020813203117.GD5009>