9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Speaking of routing....
Date: Thu, 13 Feb 2003 10:03:23 -0700	[thread overview]
Message-ID: <20030213095533.L50666@\x1d> (raw)
In-Reply-To: <200302131652.h1DGqNM22144@augusta.math.psu.edu>

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


  reply	other threads:[~2003-02-13 17:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 16:52 Dan Cross
2003-02-13 17:03 ` andrey mirtchovski [this message]
2003-02-13 17:13 ` Skip Tavakkolian
     [not found] <20030213095533.L50666@ >
2003-02-13 22:16 ` Dan Cross
2003-02-13 22:24   ` andrey mirtchovski
2003-02-13 22:27     ` David Gordon Hogan
2003-02-13 23:14       ` Dan Cross
2003-02-13 23:23         ` northern snowfall
2003-02-13 23:24         ` David Gordon Hogan
2003-02-13 23:46           ` Dan Cross
2003-02-14  0:11         ` Russ Cox
2003-02-14  0:17           ` Dan Cross
2003-02-14  0:21             ` David Presotto
2003-02-14  0:29               ` northern snowfall
2003-02-14  0:31               ` Dan Cross
2003-02-14  0:34                 ` David Presotto
2003-02-14  0:32               ` David Presotto
2003-02-14  0:44                 ` Dan Cross
2003-02-14  0:48                   ` David Presotto
2003-02-14  0:50                     ` Dan Cross
2003-02-14  0:52                       ` David Presotto
2003-02-14  0:57                         ` Dan Cross

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='20030213095533.L50666@\x1d' \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).