netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Maillist netdev <netdev@oss.sgi.com>
Subject: Re: IPsec xfrm resolution
Date: Sat, 19 Feb 2005 20:53:33 +0100	[thread overview]
Message-ID: <4217993D.4070107@trash.net> (raw)
In-Reply-To: <20050219190333.GA22166@gondor.apana.org.au>

Herbert Xu wrote:

>On Sat, Feb 19, 2005 at 07:47:11PM +0100, Patrick McHardy wrote:
>  
>
>>>That's a bug.  How can you forward packets properly if the tunnel mode
>>>SA is missing?
>>>      
>>>
>>Using normal routing. What meaning would "optional" have otherwise ?
>>If the encapsulation has to be done, the user shouldn't mark the SA
>>as optional in my opinion.
>>    
>>
>
>In that case you can't mark IPCOMP SAs as optional in this scenario
>which is the most common application of optional:
>
>IPCOMP(tunnel) -- ESP(transport)
>  
>
I've checked KAME, it also skips IPSEC_LEVEL_USE SAs if they aren't present.
IPCOMP in tunnel mode is a special case. It wants to express more than just
"optional". It means to say "use SA if present and some things wrt. size 
apply,
otherwise use a similar SA with proto=IPIP". One of both has to be used, and
this is what "optional" can't express. The current method is to use the IPIP
SA automatically created with the IPCOMP SA when the compressed size exceeds
the uncompressed size, but it doesn't handle a missing SA. This suggests we
need to special-case tunnel mode IPCOMP in xfrm_tmpl_resolve() and either
ignore "optional" for IPIP tunnel mode SAs or create them on demand.

Regards
Patrick

  reply	other threads:[~2005-02-19 19:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050209085251.GA9030@gondor.apana.org.au>
     [not found] ` <420B9DF1.3020704@trash.net>
     [not found]   ` <20050210202810.GA1609@gondor.apana.org.au>
     [not found]     ` <42144C3F.2060501@trash.net>
     [not found]       ` <20050217091137.GA9476@gondor.apana.org.au>
2005-02-17 23:26         ` IPsec xfrm resolution Patrick McHardy
2005-02-18 10:08           ` Herbert Xu
2005-02-19  6:03             ` Patrick McHardy
2005-02-19  9:23               ` Herbert Xu
2005-02-19 12:29                 ` Patrick McHardy
2005-02-19 18:32                   ` Herbert Xu
2005-02-19 18:47                     ` Patrick McHardy
2005-02-19 19:03                       ` Herbert Xu
2005-02-19 19:53                         ` Patrick McHardy [this message]
2005-02-19 20:26                           ` Patrick McHardy
2005-02-20  6:57                             ` Herbert Xu
2005-03-18  4:32                 ` David S. Miller
2005-03-18  6:24                   ` Herbert Xu
2005-03-20 15:51                   ` Patrick McHardy
2005-03-20 20:38                     ` Herbert Xu
2005-03-23  2:28                       ` Patrick McHardy

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=4217993D.4070107@trash.net \
    --to=kaber@trash.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.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).