From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <055c01c12696$23d64780$3cf7c6d4@SOMA>
From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
References: <5DD31A171181D31184A100508B5ED98901E34092@MSP0-MSX1.Ingenix.com>
Subject: Re: [9fans] stats: ethererr
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Date: Thu, 16 Aug 2001 22:58:02 +0200
Topicbox-Message-UUID: df5f20c4-eac9-11e9-9e20-41e7f4b1d025

i shall try and resurrect my badly banged around neurons after my
göteborg trip, so here goes:

> >> - crc means your packets are trashed when they get received

each ethernet packet has a 16 bit crc.  it 'ensures' that it got
received ok, but that's a lie.  talk to Sun about UDP checksums...

so on the rx and tx sides the crc's have to be done right.

> Received by whom or what? the DHCP server? or my p9 machine? if it's my
> machine doing the trashing is there a way to fix it? if they're getting
> trashed by the dhcp server what can I do to fix that, especially since I
> have to go through a network admin =)

this has nothing to do with DHCP.  these is the physical bits on the wire [ethernet].
DHCP is a coupla layers up.  you have wire/card/driver problems.

the framing is to do with the pre/post-able bits that are there to ensure
collisions based on speed of light / velocity factor propagation.  well,
maybe i really mean that the coax/utp needs to be modulated in the right
way at the right time.

> The other stuff was greek to me. Tx, rx? what is that apparently I need to
> read a book on basic networking and ethernet cards.

tx = transmit
rx = receive

de f/vk2bhr ...