From: David Dillow <dave@thedillows.org>
To: Park Lee <parklee_sel@yahoo.com>
Cc: Kausty <kkumbhalkar@gmail.com>,
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: Fri, 24 Dec 2004 01:23:27 -0500 [thread overview]
Message-ID: <1103869407.3016.7.camel@ori.thedillows.org> (raw)
In-Reply-To: <20041223062905.20979.qmail@web51503.mail.yahoo.com>
On Wed, 2004-12-22 at 22:29 -0800, Park Lee wrote:
> 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?
Are you sure you're not seeing the creation of a reply packet? Unless
you're testing with UDP and a listening socket on the receiver, you're
going to get a response packet if the incoming packet makes it through
the iptables rules. You were testing with ICMP echo requests (ping), if
I recall.
I think either you're basing your idea of the packet flow on printk()'s,
or I'm just too tired and missing where xfrm_lookup() gets called on the
rx path... (yes, sk can be NULL there, but I was wrong about it being
called for Rx'd packets, I think).
However, if your NIC driver does NAPI, you can see an xfrm_lookup() on
the reply packet when the driver calls netif_receive_skb() -- this bit
me recently...
--
David Dillow <dave@thedillows.org>
next prev parent reply other threads:[~2004-12-24 6:23 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
2004-12-24 6:23 ` David Dillow [this message]
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=1103869407.3016.7.camel@ori.thedillows.org \
--to=dave@thedillows.org \
--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 \
--cc=parklee_sel@yahoo.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
all inboxes | Powered by JetHome®