From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: generating ethernet packets
Date: Wed, 7 Jan 2004 10:22:38 +0100 [thread overview]
Message-ID: <20040107092238.GP14285@lug-owl.de> (raw)
In-Reply-To: <20040106123019.76fd7d22.cialdi@firenze.net>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On Tue, 2004-01-06 12:30:19 +0100, Massimiliano Cialdi <cialdi@firenze.net>
wrote in message <20040106123019.76fd7d22.cialdi@firenze.net>:
> On Mon, 5 Jan 2004 03:58:32 +0000 (GMT)
> James Stevenson <james@stev.org> wrote:
> > iirc there are 100's of example on doing this
> where are all these examples?
Mailing lists aren't for saving you from asking some search engines. Try
this and read the first 20 hits.
http://www.google.de/search?hl=de&ie=UTF-8&oe=UTF-8&q=linux+socket+send+raw+ethernet&btnG=Google+Suche&meta=
> it is also possible to generate an ethernet frame with wrong crc?
Don't *ask*! That's something that you can easily try after getting your
basic program ready. Just prepare a wrongly CRCed frame and try to send
it. While doing so, let a tcpdump run on the local machine as well as on
some remote machine.
Oh, and results may be surprising.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-07 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 14:35 generating ethernet packets Massimiliano Cialdi
2003-12-31 4:37 ` syedk
2003-12-31 13:47 ` Massimiliano Cialdi
2004-01-05 3:58 ` James Stevenson
2004-01-06 11:30 ` Massimiliano Cialdi
2004-01-07 9:22 ` Jan-Benedict Glaw [this message]
2003-12-31 7:01 ` Progga
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=20040107092238.GP14285@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@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).