netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Avniwb" <avniwb@future.futsoft.com>
To: "'Vasu'" <vasu@ee.iitb.ac.in>, "'linux-net'" <linux-net@vger.kernel.org>
Subject: RE: injecting packets
Date: Tue, 16 Apr 2002 13:45:29 +0530	[thread overview]
Message-ID: <000801c1e51e$df6b1100$0307040a@future.futsoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0204161203210.15280-100000@brahmi.ee.iitb.ac.in>

try dev_queue_xmit in dev.c.

or u can see chapter 13 of this...

http://www.cs.unh.edu/cnrg/gherrin/linux-net.html

ENJOY!!!
Avni :-)


-----Original Message-----
From: linux-net-owner@vger.kernel.org
[mailto:linux-net-owner@vger.kernel.org]On Behalf Of Vasu
Sent: Tuesday, 16 April 2002 12:10 PM
To: linux-net
Subject: injecting packets



Hi.

I am trying to write a module that takes Ethernet packets from the user
domain, and injects it into the proper place ( which I think is the
sk_buffers ), so that to the IP, TCP layer, the packets look as if coming
from the Ethernet device. Can someone please suggest me which files to
look into, and which structs to handle, for getting this done. Also, I
want to do the reverse task, i.e. take some particular packets ( say which
come from a specific port ) from sk_buffers and send it to user space.

Please assume that this silly looking Rx/Tx has some importance :)

Regards.

Vasu.
III yr EE student.


-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************

  reply	other threads:[~2002-04-16  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 23:36 kernel module to generate UDP & TCP traffic? Ben Greear
2002-04-15 23:43 ` David S. Miller
2002-04-16  0:25   ` Ben Greear
2002-04-15 23:43 ` Amit Kucheria
2002-04-15 23:52   ` Ben Greear
2002-04-16  6:39   ` injecting packets Vasu
2002-04-16  8:15     ` Avniwb [this message]
2002-04-16 22:27     ` Casey Carter

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='000801c1e51e$df6b1100$0307040a@future.futsoft.com' \
    --to=avniwb@future.futsoft.com \
    --cc=linux-net@vger.kernel.org \
    --cc=vasu@ee.iitb.ac.in \
    /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).