From: chuck gelm <chuck@gelm.net>
To: Marc Shapiro <mshapiro_42@yahoo.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Local network hosts unreachable
Date: Mon, 02 May 2005 21:00:18 -0400 [thread overview]
Message-ID: <4276CD22.1080301@gelm.net> (raw)
In-Reply-To: <20050502225337.39012.qmail@web54108.mail.yahoo.com>
Hi, Marc:
I believe your problem is a routing problem.
(without automatic word wrap in your email application)
I'd like to see the output of
route -n
from each machine.
A 'crossover' cable between the interfaces could help
rule out problems with the hub.
However, your original message's 'error' indicated a routing problem
and not a cable or hardware problem.
HTH, Chuck
next prev parent reply other threads:[~2005-05-03 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 22:53 Local network hosts unreachable Marc Shapiro
2005-05-03 1:00 ` chuck gelm [this message]
2005-05-03 6:35 ` Andrew Kelly
2005-05-03 16:05 ` Marc Shapiro
2005-05-03 20:40 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 3:17 gerardo juarez-mondragon
2005-05-02 21:42 gerardo juarez-mondragon
2005-04-27 20:09 Marc Shapiro
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=4276CD22.1080301@gelm.net \
--to=chuck@gelm.net \
--cc=linux-admin@vger.kernel.org \
--cc=mshapiro_42@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).