From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: OFF TOPIC - LINUX NETWORKING
Date: Mon, 9 Jul 2001 13:02:48 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107091258040.19384-100000@ignatious> (raw)
In-Reply-To: <20010709120224.B248@linserver.megsinet.net>
On Mon, 9 Jul 2001, Gregory Nowak wrote:
> Why?
> I have 4 machines here, and they all go over the same cross over cable
> which gets switched from machine to machine as it's needed.
> Two of the boxes run slackware, and they connect
> with themselves as well as their windows
> counterparts just fine.
> Besides, if the windows boxes connect to the linux boxes just
> fine over the cross over cable,
> then I really don't see how a hub would help.
Well lets start with the fact that some network cards don't work properly
using a cross over cable. Then follow by the fact that no vendor I know of
will support a machine using a cross over cable.
I would also add that this eliminates the "oops, the cable is between the
wrong two boxes" errors. It also answers more of how the network is
setup. Right now, we don't know that he doesn't have two network cards in
one or more machines with one being expected to act as a router. This may
work, but is less then optimal and much more difficult to troubleshoot. It
is much easier to deal with problems when the problem is simplified.
=======
Kirk Wood
Cpt.Kirk@1tree.net
The mind is like a parachute; it works much better when open.
If your too open minded, your brains will fall out.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
mo.valli
` Steve Holmes
` Kirk Wood
` Gregory Nowak
` Kirk Wood [this message]
` Gregory Nowak
` Gregory Nowak
Holmes, Steve
` Gregory Nowak
mo.valli
` Frank Carmickle
` Kirk Wood
` Gregory Nowak
mo.valli
mo.valli
mo.valli
mo.valli
` Gregory Nowak
mo.valli
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=Pine.LNX.4.21.0107091258040.19384-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).