9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Salmin <roman.salmin@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] looking for advice for network setup
Date: Fri, 12 Aug 2011 00:38:57 +0400	[thread overview]
Message-ID: <CAEFe=zpAuyz39DD7bqZ8AL4uCebep1TqC5a15LZCkv+4RaPy_g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

   Hello,

 I have plan9 machine in my home network that is NATed to providers VPN.

 Other machine at work is running cpu server with real IP.

 I can connect from home to work, but I don't know any way to connect
otherwise direction.

 Can I configure this machines to be able access home data from work?
(connected to
 work cpu server be able to edit file which is at home.)

 If I am rightly understand, I can't do this directly because any namespace
that will be created
 by dialing from home to work will be inaccessibly to other terminals
connected to work cpu server.

 So I need some server on work cpu server that on dialing from home will do
necessary network mounting,
  and then listen for connection from other terminals to provide them with
updated namespace, is it?
  Does such thing exists?

 I am quite new in plan9, so please enlighten me.

P.S. plan9 actually runs at kvm at linux machines, with bridge network
setup. So I can
organise VPN in linux to solve this problem globally. But question about
plan9 solution.

[-- Attachment #2: Type: text/html, Size: 1136 bytes --]

             reply	other threads:[~2011-08-11 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 20:38 Roman Salmin [this message]
2011-08-11 21:39 ` Anthony Sorace
2011-08-12 13:50   ` Roman Salmin
2011-08-12 15:55     ` Anthony Sorace
2011-08-12 18:27       ` Steve Simon

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='CAEFe=zpAuyz39DD7bqZ8AL4uCebep1TqC5a15LZCkv+4RaPy_g@mail.gmail.com' \
    --to=roman.salmin@gmail.com \
    --cc=9fans@9fans.net \
    /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).