From: Joshua Stewart <joshua.stewart@comcast.net>
To: linux-net <linux-net@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Creating and sending a packet from a kernel module
Date: Thu, 20 Mar 2003 20:46:00 -0500 [thread overview]
Message-ID: <1048211160.17980.5.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
I'd like to create and send a brand new TCP SYN packet from a module.
Does anybody have an example of how to do this.
I've tried doing alloc_skb, filling in all the information I could
imagine needing in skb->data, but what is the minimal amount of stuff
needed by the other parts of the skb to get this packet moving?
Is there an easy way to create and own a TCP socket from a module that I
could send and receive on?
Thanks,
Josh
--
Joshua Stewart <joshua.stewart@comcast.net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-03-21 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 1:46 Joshua Stewart [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 6:07 Creating and sending a packet from a kernel module Nalin gupta
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=1048211160.17980.5.camel@localhost.localdomain \
--to=joshua.stewart@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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