From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9 network issues
Date: Wed, 21 Feb 2001 07:47:15 +0000 [thread overview]
Message-ID: <E14VTzY-0003Pt-0C@finch-post-12.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 140 bytes --]
Run snoopy(8) on the 9box, and tcpdump on the
linuxcontainer, and check whether your hypothesis about
the flashing lights is accurate.
[-- Attachment #2: Type: message/rfc822, Size: 1981 bytes --]
From: Sam Hopkins <sah@borf.com>
To: undisclosed-recipients: ;
Subject: [9fans] 9 network issues
Date: Tue, 20 Feb 2001 19:11:53 -0500 (EST)
Message-ID: <200102210011.TAA17720@new.borf.com>
Heya,
I've brought up a standalone system for the purpose of doing a
demonstration this coming weekend at a local linux fest. I'm
having some odd network issues I thought someone could have
some ideas on. Here goes ...
In trying to ping the gateway ( a linux box ), I get nothing.
The little light on my hub gives me the flashies, so I know
activity is going out, but no flashies on the lines the gateway is connected
to.
In trying to ping the 9box from the gateway, still nothing. Though now,
I get flashies from both lines. The linux box gets icmp "Host
Unreachable." ... err, s/gets icmp/prints/.
Ok, so I know the general solution to be shouted from the rooftops
will be "simple, throw the linux box away." In this case, I simply can't.
To win over these linuxers, interoperability is going to be important.
Thoughts?
Cheers,
Sam
next reply other threads:[~2001-02-21 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 7:47 nigel [this message]
2001-02-22 13:18 ` [9fans] MBR Problems with Install Mark C. Otto
2001-02-22 16:06 ` Douglas A. Gwyn
2001-02-22 17:32 ` Mark C. Otto
-- strict thread matches above, loose matches on Subject: below --
2001-02-21 0:11 [9fans] 9 network issues Sam Hopkins
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=E14VTzY-0003Pt-0C@finch-post-12.mail.demon.net \
--to=nigel@9fs.org \
--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).