From: <plan9@itic.ca>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] tcp problems
Date: Sat, 16 Mar 2002 15:50:37 -0600 [thread overview]
Message-ID: <FIEDLHOOAEHBJAPIKGJCCELICAAA.plan9@itic.ca> (raw)
We also used to test ect2 and elnk3 both wired to an old D-Link so called switch. Auto negociation clearly was a big mess and we were obliged to do it by hand. Further more we discovered that operations became very slOooooow and finaly stated it came from the switch ASIC since a more recent did not produce the same results. The switch got killed, the ploblems (auto-nego / perfs) disapeared. Next time, we may buy a Cisco 19xx or 29xx, those work for sure !
<forsyth@caldo.demon.co.uk> a crit dans le message news:<20020316194329.7904519ABD@mail.cse.psu.edu>...
> i'm sure i saw similar effects when i had a full-duplex link that one side thought
> was half-duplex (or conversely, a half-duplex link that one or both
> treated as full-duplex); i'd always assumed the acks and other packets were lost.
> they could communicate but it got very slow.
> i mention it because hardware-level autoconfiguration between
> cards and switches often got messed up a few years ago.
> i seem to have better luck with things now on 10/100meg, but perhaps there's
> still something not quite right with Gigabit ether kit's negotiation, if you're
> relying on that. or perhaps the driver isn't setting that quite right.
> probably nothing to do with your problems but i thought i'd mention it just in case.
>
next reply other threads:[~2002-03-16 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 21:50 plan9 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-16 19:39 forsyth
2002-03-16 16:30 presotto
2002-03-16 3:54 andrey mirtchovski
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=FIEDLHOOAEHBJAPIKGJCCELICAAA.plan9@itic.ca \
--to=plan9@itic.ca \
--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).