From: "Real Oneone" <realoneone@gmail.com>
To: "David G." <kiddion@zonnet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to re-send out the packets captured by my hook function at NF_IP_PRE_ROUTING
Date: Thu, 27 Apr 2006 10:11:44 +0800 [thread overview]
Message-ID: <84d7d9cf0604261911m46cd505fxd9fc2045d687c79f@mail.gmail.com> (raw)
In-Reply-To: <444F91F8.80809@zonnet.nl>
Many thanks, David!
I've read what you mentioned and since I've done most of the work in
kernelspace, I wonder if there is any way to send out the modified
packet directly, when of course the mac address is not filled?
Thanks again!
2006/4/26, David G. <kiddion@zonnet.nl>:
> Real Oneone wrote:
> > Hi, I plugged a callback function into netfilter at the hook point of
> > NF_IP_PRE_ROUTING, tring to capture all the packets, make
> > some changes to some of them, and invoke skb->dev->hard_start_xmit to
> > send them out directly. However, the kernel crashed before I could get
> > any printked information.
> >
> > If you have any idea of how to send the received packets out, please tell me.
>
> You might want to explore the possibilities of the existing "ip_queue"
> kernel extension instead, it was design to do packet
> capture/inspection/changing in userspace.
>
> FireFlier works that way ( http://fireflier.sourceforge.net/ ) and so
> does inlined snort (http://www.snort.org/docs/snort_manual/node7.html).
>
> You can take a look at:
> http://www.linuxia.de/netfilter.en.html#userspace and
> http://www.cs.princeton.edu/~nakao/libipq.htm for an example application.
>
next prev parent reply other threads:[~2006-04-27 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65RDw-7AC-33@gated-at.bofh.it>
2006-04-26 15:30 ` David G.
2006-04-27 2:11 ` Real Oneone [this message]
[not found] <AF63F67E8D577C4390B25443CBE3B9F73C0A@esnmail.esntechnologies.co.in>
2006-04-27 15:02 ` Real Oneone
2006-04-26 12:46 Real Oneone
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=84d7d9cf0604261911m46cd505fxd9fc2045d687c79f@mail.gmail.com \
--to=realoneone@gmail.com \
--cc=kiddion@zonnet.nl \
--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®