From: "Srinivas M.A." <srinivas.aji@gmail.com>
To: Fahim Akhter <akhter.fahim@hotmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Modifying All Packets passing through the bridge!
Date: Mon, 10 Nov 2008 15:58:05 +0530 [thread overview]
Message-ID: <fed120860811100228x3fbff600l4e672635d4c260e3@mail.gmail.com> (raw)
In-Reply-To: <BLU149-W2552C09A3C56CF923B077E8B1A0@phx.gbl>
On Mon, Nov 10, 2008 at 11:57 AM, Fahim Akhter <akhter.fahim@hotmail.com> wrote:
> The Link
> https://lists.linux-foundation.org/pipermail/bridge/2008-October/006074.html
> , is about capturing packets and sending to user space. Speed is important
> in my current scenario. Is there anyway I can do everything in kernel
> specially by hacking or tweaking the already kernel space. Instead of socket
> programming and capturing packets at ethernet?
That message also talks about the case where userspace will not give
you enough performance. The thing to do then would be to write a
network driver which sits on top of a real network device and
processes the packets before passing it on in either direction. Look
for the vlan and bonding drivers for examples. Or maybe you could use
the netfilter hooks in bridging, if your use of this encrypted link is
restricted to being between bridges.
next prev parent reply other threads:[~2008-11-10 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 11:20 [Bridge] Modifying All Packets passing through the bridge! Fahim Akhter
2008-11-08 18:44 ` Srinivas M.A.
2008-11-10 6:27 ` Fahim Akhter
2008-11-10 10:28 ` Srinivas M.A. [this message]
2008-11-10 12:02 ` Fahim Akhter
2008-11-10 16:35 ` Stephen Hemminger
2008-11-11 5:19 ` Fahim Akhter
2008-11-11 7:16 ` Fahim Akhter
2008-11-11 17:11 ` Stephen Hemminger
2008-11-13 6:12 ` Fahim Akhter
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=fed120860811100228x3fbff600l4e672635d4c260e3@mail.gmail.com \
--to=srinivas.aji@gmail.com \
--cc=akhter.fahim@hotmail.com \
--cc=bridge@lists.linux-foundation.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