linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: mgopik@yahoo.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem with FEC on CLLF
Date: Fri, 19 Jan 2001 07:58:13 +0100 (CET)	[thread overview]
Message-ID: <200101190658.HAA00760@piglet.grunz.lu> (raw)
In-Reply-To: <20010103152029.51915.qmail@web11108.mail.yahoo.com>


On   3 Jan, this message from gopi krishna echoed through cyberspace:
> If we connect this to our switch *through a
> hub*(100mbps half duplex), everything is working fine.
>
> If we connect this directly to the switch, both the
> switch and the cllf show the link status to be up and
> connected(100mbps, half duplex), but ping doesnt work.
>
> We have noticed that the switch recieves the
> packets(frames) that the cllf is sending on the fec
> port,  the switch is sending some frames to the cllf
> fec port, but cllf doesnt receive even a single frame.
>
> Any pointers to the possible problem/solution?

I have seen things like that happen with bad cables. 100 Mb/s is very
sensitive to cable quality. Use a good, commercial-grade pre-built
cable, not homemade.

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-01-19  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 15:20 Problem with FEC on CLLF gopi krishna
2001-01-19  6:58 ` Michel Lanners [this message]

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=200101190658.HAA00760@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mgopik@yahoo.com \
    /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).