From: Julien Vehent <julien@linuxwall.info>
To: Hamid Nassiby <h.nassiby@gmail.com>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: Packet manipulation in user space
Date: Thu, 08 Apr 2010 22:52:10 +0200 [thread overview]
Message-ID: <cf60659524ea8ac90afc3024108635b6@localhost> (raw)
In-Reply-To: <h2ub3f13ff81004081154tbf514844hdfb703cf81f857d2@mail.gmail.com>
On Thu, 8 Apr 2010 23:24:09 +0430, Hamid Nassiby <h.nassiby@gmail.com>
wrote:
> Capture each packet which is coming inside or going outside the
> computer in Data-link Layer.
> Create a copy of the packet and drop the original one.
> Copy of packet must be available in user space to be manipulated by
> our protocol.
> After manipulation in user space, inject encrypted/decrypted version
> of the privileged (copy of) packets to the network or upward to the
> application layer.
>
libnetfilter_queue ?
http://www.netfilter.org/projects/libnetfilter_queue/index.html
next prev parent reply other threads:[~2010-04-08 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <h2hb3f13ff81004081148n221e9728mb5a14944cf4ffd06@mail.gmail.com>
2010-04-08 18:54 ` Packet manipulation in user space Hamid Nassiby
2010-04-08 20:52 ` Julien Vehent [this message]
2010-04-09 6:00 ` Hamid Nassiby
2010-04-09 9:02 ` Jan Engelhardt
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=cf60659524ea8ac90afc3024108635b6@localhost \
--to=julien@linuxwall.info \
--cc=h.nassiby@gmail.com \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.