9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Iafrate - CSCI/F1997 <diafrate@scs.Ryerson.CA>
To: presotto@plan9.bell-labs.com
Cc: forsyth@vitanuova.com, 9fans@cse.psu.edu
Subject: Re: [9fans] Communication problem!!
Date: Tue, 10 Apr 2001 13:10:47 -0400	[thread overview]
Message-ID: <Pine.GSO.4.21.0104101310070.3975-100000@jupiter.scs.ryerson.ca> (raw)
In-Reply-To: <20010410170519Z48579-10235+9@saturn.scs.ryerson.ca>

When we run route print, we get everything the same that you've entered
except for the defgate which is 192.168.1.0


On Tue, 10 Apr 2001 presotto@plan9.bell-labs.com wrote:

> Date: Tue, 10 Apr 2001 13:05:04 -0400
> From: presotto@plan9.bell-labs.com
> To: diafrate@scs.Ryerson.CA, forsyth@vitanuova.com, 9fans@cse.psu.edu
> Subject: Re: [9fans] Communication problem!!
>
> You can figure out what the file system thinks about its address
> by typing
>
> 	route print
>
> You should get something like:
>
> 	ifc's
> 	addr 0.0.0.0 mask 0.0.0.0 defgate 0.0.0.0
> 	addr 192.168.1.3 mask 255.255.255.0 defgate 192.168.1.1
>
> I missed part of this thread.  Can anything ping your file
> server?  Can your cpu server get to anything else?
>



       reply	other threads:[~2001-04-10 17:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010410170519Z48579-10235+9@saturn.scs.ryerson.ca>
2001-04-10 17:10 ` Dave Iafrate - CSCI/F1997 [this message]
2001-04-10 17:05 presotto
  -- strict thread matches above, loose matches on Subject: below --
2001-04-10 15:19 forsyth
2001-04-10 16:39 ` Dave Iafrate - CSCI/F1997
2001-04-10 14:48 forsyth
2001-04-10 15:18 ` Dave Iafrate - CSCI/F1997
2001-04-10 15:43   ` Martin Harriss
2001-04-10 15:46     ` Dave Iafrate - CSCI/F1997
2001-04-10 14:46 forsyth
2001-04-10 14:55 ` Dave Iafrate - CSCI/F1997
2001-04-10 14:23 Dave Iafrate - CSCI/F1997

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.GSO.4.21.0104101310070.3975-100000@jupiter.scs.ryerson.ca \
    --to=diafrate@scs.ryerson.ca \
    --cc=9fans@cse.psu.edu \
    --cc=forsyth@vitanuova.com \
    --cc=presotto@plan9.bell-labs.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).