From: "Primiano Tucci" <mail@primianotucci.com>
To: <netdev@vger.kernel.org>
Subject: Ethernet frames filtering/relaying. Help needed
Date: Mon, 21 May 2007 16:49:56 +0200 [thread overview]
Message-ID: <000201c79bb7$4c97b680$0201a8c0@airforce1> (raw)
Hi all, I'm new to this Mailing list
Some days ago I started development of a new 2.6 network driver (formerly it
should be a decentered Network Load Balancing driver).
I'm not too much familiar with kernel networking, so I'm asking you what's
the best approach to do something like this:
- Allocate a new tun interface... let's say tun0 (no problems with this
step)
- Monitor layer2 traffic on an existing device(let's say eth0).
-Catch all Ethernet frames arrived on eth0 with an arbitrary destination MAC
address.... let's say catch all the frames that has 01:00:02:03:04:05 as
destination MAC addr.
-Extrapolate the IP datagram contained in the frames and push it in tun0
I need some suggestions about the best approach to catch and relay Ethernet
frames on eth0. Should I use netfilter? Should I not?
Any help will be appreciated. Thanks
Primiano Tucci
reply other threads:[~2007-05-21 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000201c79bb7$4c97b680$0201a8c0@airforce1' \
--to=mail@primianotucci.com \
--cc=netdev@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