mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Park Lee <parklee_sel@yahoo.com>
To: Kausty <kkumbhalkar@gmail.com>
Cc: ipsec@ietf.org, ipsec-tools-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [Ipsec] Issue on input process of Linux native IPsec
Date: Wed, 22 Dec 2004 22:29:05 -0800 (PST)	[thread overview]
Message-ID: <20041223062905.20979.qmail@web51503.mail.yahoo.com> (raw)
In-Reply-To: <41ae448404122203477e71bb83@mail.gmail.com>

On Wed, 22 Dec 2004 at 17:17, Kausty wrote:
>
> On Tue, 21 Dec 2004 10:52:22 -0800 (PST), Park Lee
> <parklee_sel@yahoo.com> wrote:
> > Hi,
> > We know that the output process of Linux native
> > IPsec fully uses the XFRM architecture. The order 
> > of primal functions are xfrm_lookup(),
> > xfrm_tmpl_resolve(), xfrm_bundle_create() and
> > dst_output().
> > The input process for IPsec is more simple than
> > output. The order of primal functions (in IPv4) 
> > are xfrm4_rcv(), xfrm4_rcv_encap(),
> > xfrm4_parse_spi(), xfrm4_policy_check().
> >  But, Why should the input process also go 
> > throught xfrm_lookup(), xfrm_tmpl_resolve(),
> > xfrm_bundle_create()? What's the purpose of this?
>
> i havent gone through the code flow as u mentioned 
> but this is my general idea.
>
> these are generic lookup functions irrespective of 
> ipv6/v4.
> the purpose is to ensure that all the SA's are 
> applied hence a bundle needs to be created 
> everytime a packet is recieved.
> If no bundle is created then a seperate search 
> needs to be done for ESP/AH/Transport/Tunnel
>
> is this what u were looking for ??

Thanks.
But, After a packet was received, It has already been
processed by xfrm4_rcv(), xfrm4_rcv_encap(),
ah_input(), esp_input(),etc. so, I think that there is
no need to search(or created) a bundle everytime a
packet is recieved, since it has already been
processed. Am I right?


=====
Best Regards,
Park Lee


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail

       reply	other threads:[~2004-12-23  6:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41ae448404122203477e71bb83@mail.gmail.com>
2004-12-23  6:29 ` Park Lee [this message]
2004-12-24  6:23   ` David Dillow
2004-12-24 19:23     ` Park Lee
2004-12-24 21:15       ` David Dillow
2004-12-25 17:47         ` Park Lee
2005-03-10 10:37 Park Lee
2005-03-10 16:18 ` Dave Dillow

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=20041223062905.20979.qmail@web51503.mail.yahoo.com \
    --to=parklee_sel@yahoo.com \
    --cc=ipsec-tools-devel@lists.sourceforge.net \
    --cc=ipsec@ietf.org \
    --cc=kkumbhalkar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®