From: Simba <simba@lionking.at>
To: netdev@vger.kernel.org
Subject: Ethernet Frame Generation
Date: Tue, 27 Mar 2007 17:27:42 +0200 [thread overview]
Message-ID: <460937EE.8050703@lionking.at> (raw)
In-Reply-To: <20070327142519.GN521@postel.suug.ch>
Greetings,
I am new to this list. I have a very special question.
I am currently working on a new l2/l3 protocol (just for
research reasons) and i would like to make a test implementation
in the linux kernel.
For this i need to modify the ethernet header and replace it
with my header. The payload of this header holds the raw data, or
an TCP segment, or an UDP datagram.
The problem is, that i try to find out, where this code is located
in the kernel source.
I found out, that most of the ethernet handling can be found in eth.c
I am just not sure, if there are other dependencies which i need to
have a look at. I tried to find more information on the internet but
couldnt actually.
So if you can help me with this question i would really really
appreciate it.
I am quite new to this, and i am sorry, if it sounds like a silly
question for some of you.
The implementation should at the moment only go that far, that i can
make two patched linux boxes to talk to each other.
Thanks for your help
Greetings
Christoph Kellner
next prev parent reply other threads:[~2007-03-27 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 13:45 [PATCH net-2.6.22] [IPV6] FIB6RULE: Find source address during looking up route YOSHIFUJI Hideaki / 吉藤英明
2007-03-27 14:25 ` Thomas Graf
2007-03-27 15:27 ` Simba [this message]
2007-03-27 15:47 ` Ethernet Frame Generation Evgeniy Polyakov
2007-03-28 3:49 ` [PATCH net-2.6.22] [IPV6] FIB6RULE: Find source address during looking up route YOSHIFUJI Hideaki / 吉藤英明
2007-03-28 4:02 ` Noriaki TAKAMIYA
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=460937EE.8050703@lionking.at \
--to=simba@lionking.at \
--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;
as well as URLs for NNTP newsgroup(s).