From: k8 s <uint32@gmail.com>
To: Michael Becker <michbec@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPSec Inbound Processing Basic Doubt
Date: Tue, 28 Jun 2005 22:38:17 +0530 [thread overview]
Message-ID: <699a19ea05062810087b79f12f@mail.gmail.com> (raw)
In-Reply-To: <506243806.20050627182416@t-online.de>
Hello,
> So far you are right with your assumptions, I hope my explanation just
> made it a bit clearer.
Yes. It was really nice organization of whole thing.
>The whole decapsulation is done in xfrm4_rcv_encap, except in case of
>nat-traversal, where udp_rcv comes into play.
>After the whole xfrm processing is done the packet is put back into the
>network stack as it would look like without being ever processed by IPSec
>(almost :-).
I have a doubt regarding nat-traversal. Let me first admit that I
don't have a perfect understanding of the NAT traversal concept. I
heard that IPSec is kept in a UDP packet and sent. How does the tx
side processing happen (the host from which the udp encapsulated ipsec
packet originated). The last call in the stackable destination is
ip_output() as you said.
How does it go back to udp(transport) layer in this case.
S.Kartikeyan
http://www.geocities.com/kartikeyans/
next prev parent reply other threads:[~2005-06-28 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 17:55 IPSec Inbound Processing Basic Doubt k8 s
2005-06-27 16:24 ` Michael Becker
2005-06-28 17:08 ` k8 s [this message]
2005-06-28 17:31 ` k8 s
2005-06-28 21:53 ` Re[2]: " Michael Becker
2005-06-28 21:41 ` Michael Becker
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=699a19ea05062810087b79f12f@mail.gmail.com \
--to=uint32@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michbec@t-online.de \
/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.