From: Vojtech Pavlik <vojtech@suse.cz>
To: Pavel Machek <pavel@suse.cz>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Ethernet Error Correction
Date: Tue, 2 Oct 2001 11:55:31 +0200 [thread overview]
Message-ID: <20011002115531.A7176@suse.cz> (raw)
In-Reply-To: <20010925223437.A21831@atrey.karlin.mff.cuni.cz> <20010926004345.D11046@mea-ext.zmailer.org> <20010927142251.A58@toy.ucw.cz> <20011002112921.A7117@suse.cz> <20011002114801.A19015@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20011002114801.A19015@atrey.karlin.mff.cuni.cz>; from pavel@suse.cz on Tue, Oct 02, 2001 at 11:48:01AM +0200
On Tue, Oct 02, 2001 at 11:48:01AM +0200, Pavel Machek wrote:
> Hi!
>
> > > > Also, generic PROMISC mode still drops off received frames
> > > > with CRC error.
> > >
> > > Hmm, sounds good. Someone should create tool for communication over
> > > ethernet with broken crc's. Such communication would be stealth from
> > > normal tcpdump. Do it on your provider's network to escape accounting ;^)
> >
> > But still you'll see the number of errors on your eth card
> > skyrocketing, so you'd grow quite suspicious.
>
> Yep, but it would be _very_ hard for you to find the cause. You'd
> probably chase ghosts trying to replace cables, etc, never finding
> what happens.
Well, if you checked all the cables, you'd most likely find the device
capable of sending the bad CRC frames. Also, if you use a switch (not ha
hub or coax), it won't work at all.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-10-02 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 20:34 Ethernet Error Correction Karel Kulhavy
2001-09-25 20:57 ` Richard B. Johnson
2001-09-25 21:19 ` Ben Greear
2001-09-26 12:37 ` Richard B. Johnson
2001-09-25 21:43 ` Matti Aarnio
2001-09-27 14:22 ` Pavel Machek
2001-10-02 9:29 ` Vojtech Pavlik
2001-10-02 9:48 ` Pavel Machek
2001-10-02 9:55 ` Vojtech Pavlik [this message]
2001-10-04 21:34 ` Rob Landley
2001-10-02 9:56 ` Matti Aarnio
2001-09-26 16:51 ` Alan Cox
2001-09-27 5:26 ` Albert D. Cahalan
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=20011002115531.A7176@suse.cz \
--to=vojtech@suse.cz \
--cc=clock@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=pavel@suse.cz \
/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.