From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <dd38e9021a6048b11f1b047be0134dcf@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu server to vmware auth server ... so close ....
From: rsc@plan9.bell-labs.com
In-Reply-To: <Pine.LNX.4.44.0304151432470.1417-100000@maxroach.lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 15 Apr 2003 17:23:01 -0400
Topicbox-Message-UUID: 90794dc0-eacb-11e9-9e20-41e7f4b1d025

> 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.