From: DHAJOGLO <DHAJOGLO@smumn.edu>
To: netdev@vger.kernel.org
Subject: noob dev question
Date: Mon, 10 Sep 2007 19:09:54 -0500 [thread overview]
Message-ID: <200709110009540720c546a9@mail.smumn.edu> (raw)
I'm new to the list and new to just about everything involving kernel development. I'm working on a project where I have successfully written a LKM to handle IP packets for protocol type 253 (an experimental protocol number). Now, I'm working on sending my reply and I hit a road block. I'm not sure if I should:
1) create a new skb with my protocol data and try to pass it to the IP handler
OR
2) use the inbound skb and just turn it around and use it to send back out manually via a NF Hook.
Ideally I would like to get my reply formatted and sent into ip_queue_xmit but I'm at the limit of what I can do regarding the manipulation of the socket buffers. I'm currently working in 2.6.18.8 as the book I'm using does not reflect some of the newer changes to the sk_buff struct. Any help or pointers would be nice. I'm looking more for online tutorials at this point.
Regards,
-dave
reply other threads:[~2007-09-11 0:15 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=200709110009540720c546a9@mail.smumn.edu \
--to=dhajoglo@smumn.edu \
--cc=netdev@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