From: Patrick McHardy <kaber@trash.net>
To: Paul Moore <paul.moore@centrify.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: port bound SAs
Date: Wed, 28 Jan 2009 19:03:01 +0100 [thread overview]
Message-ID: <49809DD5.6080104@trash.net> (raw)
In-Reply-To: <BB7E16A14DE689469A181EC770AFBF4D02A77722@exch-one.centrify.com>
Paul Moore wrote:
> So where did we get to on this?
>
> My main question is - do you agree this is incorrect behavior of the
> overall system (racoon, pfkey, xfrm, ip) without trying to say which bit
> is to blame?
No, so far everything seems fine. The SAs don't have a port selector,
no reqid is specified => Linux is allowed to reuse them.
next prev parent reply other threads:[~2009-01-28 18:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F82446300569AC408EF6BC9E358737947EC12368@exch-one.centrify.com>
2009-01-26 19:21 ` port bound SAs Paul Moore
2009-01-27 6:20 ` David Miller
2009-01-27 10:26 ` Patrick McHardy
2009-01-27 16:46 ` Paul Moore
2009-01-27 17:01 ` Patrick McHardy
2009-01-27 17:05 ` Paul Moore
2009-01-27 17:12 ` Patrick McHardy
2009-01-27 17:13 ` Paul Moore
2009-01-27 17:21 ` David Miller
2009-01-27 17:21 ` Paul Moore
2009-01-27 17:21 ` Patrick McHardy
2009-01-27 17:24 ` Paul Moore
2009-01-27 17:29 ` Patrick McHardy
2009-01-27 17:38 ` Paul Moore
2009-01-27 17:42 ` Patrick McHardy
2009-01-28 17:17 ` Paul Moore
2009-01-28 18:03 ` Patrick McHardy [this message]
2009-01-28 18:07 ` Paul Moore
2009-01-28 18:11 ` Patrick McHardy
2009-01-28 18:27 ` Paul Moore
2009-01-30 6:30 ` Herbert Xu
2009-02-24 1:31 ` xfrm selector generating IKE Paul Moore
2009-02-24 2:08 ` Herbert Xu
2009-02-24 17:23 ` Paul Moore
2009-02-25 0:33 ` Herbert Xu
2009-02-25 2:07 ` Paul Moore
2009-02-25 2:27 ` Herbert Xu
2009-02-25 2:30 ` Paul Moore
2009-02-25 2:38 ` Herbert Xu
2009-01-29 17:23 ` port bound SAs Paul Moore
2009-01-27 16:53 ` Paul Moore
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=49809DD5.6080104@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@centrify.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.