From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux vs. Windows XP routing latency
Date: Sat, 05 Jun 2004 13:06:25 +0000 [thread overview]
Message-ID: <40C1C551.5050505@wildgooses.com> (raw)
In-Reply-To: <20040602150137.4746.qmail@hc-online.com.ar>
>What is a duplex mismatch?
>
>
When the duplex setting of your connection aren't matched....! :-)
Google is very useful for finding out about stuff. Try links 2,3 and
onwards
http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=duplex+mismatch
However, if you have even a budget "switch" in between these two
machines then this would fix the problem. Note that a "hub" will not
fix the problem though.
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-05 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 15:01 [LARTC] Linux vs. Windows XP routing latency donsapo
2004-06-02 21:36 ` Peter Surda
2004-06-04 8:13 ` donsapo
2004-06-04 14:37 ` Debreczeni Peter
2004-06-05 13:06 ` Ed Wildgoose [this message]
2004-06-07 6:34 ` Ronny Aasen
2004-06-07 7:39 ` Paulo Andre
2004-06-18 0:01 ` Andy Furniss
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=40C1C551.5050505@wildgooses.com \
--to=lists@wildgooses.com \
--cc=lartc@vger.kernel.org \
/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