From: Andrew Beverley <andy@andybev.com>
To: "Prashant Batra (prbatra)" <prbatra@cisco.com>
Cc: netdev@vger.kernel.org
Subject: RE: IP forwarding on a linux IPSec gateway
Date: Tue, 31 Jan 2012 22:15:55 +0000 [thread overview]
Message-ID: <1328048155.1630.0.camel@andy-laptop> (raw)
In-Reply-To: <B97B134FACB2024DB45F524AB0A7B7F205B93C54@XMB-BGL-419.cisco.com>
On Tue, 2012-01-31 at 23:41 +0530, Prashant Batra (prbatra) wrote:
> Any links to understand the flow in the kernel for this kind of
> forwarding with IPSec to analyze where the problem could be will be
> really helpful.
Does this excellent diagram from Jan help at all?
http://upload.wikimedia.org/wikipedia/commons/3/37/Netfilter-packet-flow.svg
Andy
prev parent reply other threads:[~2012-01-31 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 10:01 IP forwarding on a linux IPSec gateway Prashant Batra (prbatra)
2012-01-31 17:47 ` Andrew Beverley
2012-01-31 18:11 ` Prashant Batra (prbatra)
2012-01-31 22:15 ` Andrew Beverley [this message]
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=1328048155.1630.0.camel@andy-laptop \
--to=andy@andybev.com \
--cc=netdev@vger.kernel.org \
--cc=prbatra@cisco.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).