From mboxrd@z Thu Jan  1 00:00:00 1970
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Speaking of routing....
In-Reply-To: <200302131652.h1DGqNM22144@augusta.math.psu.edu>
Message-ID: <20030213095533.L50666@>
References: <200302131652.h1DGqNM22144@augusta.math.psu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Date: Thu, 13 Feb 2003 10:03:23 -0700
Topicbox-Message-UUID: 5c9c868e-eacb-11e9-9e20-41e7f4b1d025

there is a similar setup to yours at acl.lanl:

(web page doesn't seem to be working currently, so here's google's cache)
http://216.239.57.100/search?q=cache:ddDZwvPb2uUC:www.acl.lanl.gov/plan9/newnetwork/+&hl=en&ie=UTF-8

normally to access external machine i'd open a rio window and bind
/net.alt to /net in it, then leave it alone and use it when the need
arises -- just another beautiful example of private namespaces...

here are some samples taken from the web site above:

-------

This is the only machine that lives on the external network. The secondary
network interface is hooked to the external network the primary interface
is connected to the unrouted network. However all hosts on the internal
network can access the external network by using the command:


import plan9 /net.alt


and then using addresses like:


ping /net.alt/icmp!acl.lanl.gov
ssh /net.alt/tcp!acl.lanl.gov


Actually if you are willing to wait 30 seconds or so for the timeout you
don't need to use the /net.alt/ prefix. Or if you only want to use the
external interface in a given namespace you can import the external
interface on top of the internal interface, and the use "normal"
addresses:


import plan9 /net.alt
import plan9 /net.alt /net orbind /net.alt /net


Which is the method we commonly use.


andrey

On Thu, 13 Feb 2003, Dan Cross wrote:

> I have a question.  I have have a CPU server with two interfaces, one
> mounted on /net, the other on /net.alt.  They're connected to two
> networks; on internal, and the other the Internet.  I want users who
> login to the CPU server to be able to connect to either network
> seamlessly; without jumping through hoops.  Is that possible?  (I know
> this question is sort of vague, and I apologize for that, but I'm
> pressed for time at the moment).
>
> That is, when they connect somewhere, they shouldn't have to say,
> ``telnet /net.alt/tcp!foobar''; ``telnet tcp!foobar'' should work
> for hosts internal and external.  Is that possible?  I'm afraid I
> haven't looked at the code, as the machine is currently powered down,
> and my laptop's battery is dead, and the charger is at home.  :-(
>
> 	- Dan C.
>