From: Joy Latten <latten@austin.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, paul.moore@hp.com,
vyekkirala@TrustedCS.com
Subject: Re: when having to acquire an SA, ipsec drops the packet
Date: Tue, 06 Mar 2007 11:14:46 -0600 [thread overview]
Message-ID: <1173201286.3085.80.camel@faith.austin.ibm.com> (raw)
In-Reply-To: <Line.LNX.4.64.0703052216490.18579@d.namei>
On Mon, 2007-03-05 at 22:21 -0500, James Morris wrote:
> On Mon, 5 Mar 2007, Joy Latten wrote:
>
> > 5. Around the time the set of SAs for OUT direction are to be
> > inserted into SAD, I see another ACQUIRE happening.
> >
> > I have not yet figured out where this second ACQUIRE comes from
> > and why it happens. As long as the minimal SA or set of valid outgoing
> > SAs exist in SAD, an ACQUIRE should not happen.
>
> I saw something similar to this some time ago when testing various
> failure modes, and discused it with Herbert.
>
> IIRC, there's a larval SA which is not torn down properly by Racoon once
> the full SA is established, and the larval SA keeps resending until it
> times out.
>
Ok, good to know.
I thought a bit more about this last night but am not
sure best way to fix it. Perhaps a way to keep larval
SA around until all SAs resulting from xfrm_vec[xfrm_nr]
are established... oh well, just thinking out loud... :-)
Joy
next prev parent reply other threads:[~2007-03-06 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 1:47 when having to acquire an SA, ipsec drops the packet Joy Latten
2007-03-06 3:21 ` James Morris
2007-03-06 17:14 ` Joy Latten [this message]
2007-03-06 19:40 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2007-02-07 16:33 Joy Latten
2007-02-01 22:51 Joy Latten
2007-02-01 23:44 ` James Morris
2007-02-02 15:30 ` Paul Moore
2007-02-05 4:53 ` David Miller
2007-02-05 16:33 ` James Morris
2007-02-05 20:34 ` James Morris
2007-02-05 21:07 ` David Miller
2007-02-05 20:49 ` Venkat Yekkirala
2007-02-05 21:11 ` David Miller
2007-02-05 20:53 ` Joy Latten
2007-02-05 21:13 ` David Miller
2007-02-05 20:52 ` Joy Latten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1173201286.3085.80.camel@faith.austin.ibm.com \
--to=latten@austin.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=vyekkirala@TrustedCS.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).