netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "john" <johnp@marine-boy.nu>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Andrewm@uow.edu.au, netdev@oss.sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: Problems getting a stable 100 megabit connection with linksys etherfast switch
Date: Thu, 4 Mar 2004 05:44:00 -0700	[thread overview]
Message-ID: <20040304123913.M97501@marine-boy.nu> (raw)
In-Reply-To: <200403020001.48026.vda@port.imtp.ilyichevsk.odessa.ua>

Hi Denis,

Turns out I had a cable problem.  Some of the patch cables that I made, had
the wrong pinout.  After replacing them, the connection is stable at 100baseTx-FD.

Thanks

John



On Tue, 2 Mar 2004 00:01:47 +0200, Denis Vlasenko wrote
> On Sunday 29 February 2004 23:30, john wrote:
> > Hi,
> >
> > I am having problems getting a stable connection with my linux machines
> > when trying to connect them at 100 megabit speeds to a linksys etherfast
> > switch.
> >
> >
> > I have attached some diagnostic outputs for your review.  I hope that
> > someone can help me with this problem.
> >
> > I believe using a managed switch will solve the problem, but I don't want
> > to have to spend $1000.00 to fix this problem, when I should be able to
> > obtain a stable connection with the equipment I am currently using.
> 
> Try half duplex. You seldom do lots of xfers in both directions at 
> once, so half duplex is not a big loss.
> 
> Use tcpdump to see what's going on on the wire.
> --
> vda


--

      reply	other threads:[~2004-03-04 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 21:30 Problems getting a stable 100 megabit connection with linksys etherfast switch john
2004-03-01 22:01 ` Denis Vlasenko
2004-03-04 12:44   ` john [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=20040304123913.M97501@marine-boy.nu \
    --to=johnp@marine-boy.nu \
    --cc=Andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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).