kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: fordearlinux@gmail.com (shivanth)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Path for STOLEN Packets!!!
Date: Tue, 22 Nov 2011 21:46:53 +0530	[thread overview]
Message-ID: <4ECBCAF5.10005@gmail.com> (raw)
In-Reply-To: <CADWUQZ7XR=ELSjwedTV3GP+E1W0c+-UKxZJ5OkeXEqM9X2TG=Q@mail.gmail.com>

On 11/22/2011 1:26 PM, Kesava Srinivas wrote:
> Hi ,
> Even after lot of google; didn't get the accurate answer for this. 
> After STEALING Packets (NF_STOLEN); want to send the Manipulated 
> Packet (added extra header) to some of the available net devices. 
> Please let me know what is the Function that I Should call to do this 
> step ?? Also; once the skb was expanded by 20 bytes to add new ip 
> header; do I need to reassign the skb pointer to the new location ??
>
> -Thanks in Advance,
> VKS
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi srinivas,
     You can send/transmit  the manipulated skb buffer by passing it to 
dev_queue_xmit . Be carefull though, any error crafting the packet, a 
kernel panic is waiting 4 you :-)
These articles might help
http://www.phrack.org/issues.html?issue=61&id=13 
<http://www.phrack.org/issues.html?issue=61&id=13>

http://www.phrack.org/issues.html?issue=55&id=12#article
Regards
shivanth

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111122/508bae9e/attachment.html 

      reply	other threads:[~2011-11-22 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  7:56 Path for STOLEN Packets!!! Kesava Srinivas
2011-11-22 16:16 ` shivanth [this message]

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=4ECBCAF5.10005@gmail.com \
    --to=fordearlinux@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).