From: Joshua Stewart <joshua.stewart@comcast.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Tracing TCP/IP packets from NIC to TCP
Date: Fri, 03 Jan 2003 19:08:36 -0500 [thread overview]
Message-ID: <1041638921.5190.22.camel@localhost.localdomain> (raw)
I've asked questions on this topic in the previous e-mails Subj:"Help me
get up to speed, please" and Subj:"From __cpu_raise_softirq() to
net_rx_action()". I understand the packet flow from the NIC all the way
to the ip_rcv() function (and a little further). So, maybe somebody can
fill in another little gap for me.
ip_rcv() call NF_HOOK( PF_INET, NF_IP_PRE_ROUTING, skb, dev, NULL,
ip_rcv_finish) which checks all netfilter hooks that are currently
registered in the PREROUTING hook. All packets that are accepted by
these hook functions get passed to the ip_rcv_finish() function. In
ip_rcv_finish, we call ip_route_input() which sets skb->dst. Then
ip_rv_finish() returns skb->dst->input(skb).
I don't understand enough about the kernel's routing mechanisms to
figure out how these packets (sk_buffs) make their way to the tcp
stack. Can somebody fill me in on exactly what the skb->dst structure
does and where the rt_hash_table array gets setup. If I could just
follow this sk_buff until I start hitting code from tcp.c I'd be more
than satisfied.
Thanks,
Josh
reply other threads:[~2003-01-03 23:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1041638921.5190.22.camel@localhost.localdomain \
--to=joshua.stewart@comcast.net \
--cc=linux-kernel@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®