linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: root@chaos.analogic.com
Cc: adilger@clusterfs.com (Andreas Dilger),
	jjasen1@umbc.edu (John Jasen),
	mikeg@wen-online.de (Mike Galbraith),
	vda@port.imtp.ilyichevsk.odessa.ua (Denis Vlasenko),
	linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: reading your email via tcpdump
Date: Wed, 20 Mar 2002 00:34:32 +0000 (GMT)	[thread overview]
Message-ID: <E16nU3k-0000oJ-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.3.95.1020319151601.4151A-100000@chaos.analogic.com> from "Richard B. Johnson" at Mar 19, 2002 03:19:55 PM

> The data sent/received on the network is precious. You will not have
> any 'extra' data on its end except for possibly a single byte if the
> data didn't have an even length. Note that these things are checksummed
> and also CRCed in the hardware.

Wrong for ethernet. Ethernet has a minimum frame size

Alan

  reply	other threads:[~2002-03-20  0:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 17:20 reading your email via tcpdump Mike Galbraith
2002-03-19 11:39 ` Denis Vlasenko
2002-03-19  9:19   ` Mike Galbraith
2002-03-19 14:20     ` John Jasen
2002-03-19 14:58       ` Mike Galbraith
2002-03-19 18:11       ` Mike Fedyk
2002-03-19 15:47         ` Andreas Dilger
2002-03-19 20:02           ` Mike Fedyk
2002-03-19 20:19           ` Richard B. Johnson
2002-03-20  0:34             ` Alan Cox [this message]
2002-03-20  1:00               ` Petko Manolov
2002-03-19 21:04           ` Urban Widmark
2002-03-20  7:46             ` Mike Galbraith
2002-03-19 18:56         ` Mike Galbraith
2002-03-19 18:52           ` Mike Fedyk
2002-03-19 19:16             ` Mike Galbraith

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=E16nU3k-0000oJ-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=adilger@clusterfs.com \
    --cc=jjasen1@umbc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=root@chaos.analogic.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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).