9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dean Ash <Dean.Ash@Ingenix.com>
To: "'9fans@cse.psu.edu'" <9fans@cse.psu.edu>
Subject: RE: [9fans] stats: ethererr
Date: Thu, 16 Aug 2001 16:08:46 -0500	[thread overview]
Message-ID: <5DD31A171181D31184A100508B5ED98901E34099@MSP0-MSX1.Ingenix.com> (raw)

cool, now I have a beginning. driver I don't know about that one. P9
recognizes the card (I'm told it's a 3COM 905, have to verify that). Card is
a distinct possibility, linux didn't work with it either, which I'd say is
weird with a 3COM card. Wire, maybe the one coming out of the computer is
bad but I'm almost 80% sure the port that connects P9 to the rest of the
network is bad. Well I'll have to do some futzing around this weekend if
time permits. Thanks for the help. Great website by the way Boyd. I just got
done going through it, very humorous.

Dean

-----Original Message-----
From: Boyd Roberts [mailto:boyd@fr.inter.net]
Sent: Thursday, August 16, 2001 3:58 PM
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stats: ethererr


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 ...



             reply	other threads:[~2001-08-16 21:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16 21:08 Dean Ash [this message]
2001-08-16 22:01 ` Boyd Roberts
2001-08-20  8:56   ` Douglas A. Gwyn
  -- strict thread matches above, loose matches on Subject: below --
2001-08-16 22:21 Dean Ash
2001-08-16 20:34 Dean Ash
2001-08-16 20:58 ` Boyd Roberts
2001-08-16 16:32 Dean Ash
2001-08-16 20:22 ` Boyd Roberts

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=5DD31A171181D31184A100508B5ED98901E34099@MSP0-MSX1.Ingenix.com \
    --to=dean.ash@ingenix.com \
    --cc=9fans@cse.psu.edu \
    /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).