All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: DiegoB <diego.beltrami@hiit.fi>
Cc: Kernel Netdev Mailing List <netdev@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Miika Komu <miika@iki.fi>
Subject: Re: [XFRM]: Optimize MTU calculation
Date: Wed, 04 Apr 2007 15:07:34 +0200	[thread overview]
Message-ID: <4613A316.8090805@trash.net> (raw)
In-Reply-To: <4612B268.6060204@hiit.fi>

DiegoB wrote:
> Patrick McHardy wrote:
> 
>> I've updated my IPsec MTU optimization patch I've posted a couple
>> of month ago to net-2.6.22 and added the further optimization
>> suggested by Herbert to account for the space lost due to alignment
>> in the room reserved for IP options in transport mode.
>>
>> Tested with IPv4 and IPv6 in tunnel and transport mode. Beet mode
>> is untested since no keying daemon seems to support it.
> 
> 
> Actually for BEET mode you can check the following:
> 
> http://hipl.hiit.fi/
> http://www.openhip.org/
> http://www.hip4inter.net/


Thanks for the pointers, I'm using manual keying for testing now.
It took me a while to properly set it up though since I wasn't
expecting that I need to specify a selector for the inbound SA.
Is there a reason for not using x->props.saddr/x->id.daddr during
inbound processing as on the output side?

draft-nikander-esp-beet-mode-06.txt states ".. MUST contain the
outer source and destination addresses, as defined in the SA"
for both inbound and outbound processing, so I think it would
be easier to handle this symetrical.

  reply	other threads:[~2007-04-04 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 16:36 [XFRM]: Optimize MTU calculation Patrick McHardy
2007-04-03 20:00 ` DiegoB
2007-04-04 13:07   ` Patrick McHardy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-06 19:48 Patrick McHardy
2007-04-09 18:47 ` David Miller

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=4613A316.8090805@trash.net \
    --to=kaber@trash.net \
    --cc=diego.beltrami@hiit.fi \
    --cc=herbert@gondor.apana.org.au \
    --cc=miika@iki.fi \
    --cc=netdev@vger.kernel.org \
    /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.