From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu server to vmware auth server ... so close ....
Date: Tue, 15 Apr 2003 17:23:01 -0400 [thread overview]
Message-ID: <dd38e9021a6048b11f1b047be0134dcf@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304151432470.1417-100000@maxroach.lanl.gov>
> the cpu server is on a different network. It is not vmware. It is on eth0.
your last email said it was on the vmware network.
you can edit the plan 9 routing table by echoing
to /net/iproute. but i don't think that will accomplish
anything useful. it seems like your problem is that
the cpu server can't find the auth server during boot,
not the other way around.
the whole point of a nat is usually to hide the
natted network. you're trying to break that,
and it's (unsurprisingly) difficult.
prev parent reply other threads:[~2003-04-15 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 18:47 ron minnich
2003-04-15 19:53 ` rsc
2003-04-15 20:33 ` ron minnich
2003-04-15 21:23 ` rsc [this message]
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=dd38e9021a6048b11f1b047be0134dcf@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).