9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] punching through firewalls...
Date: Tue, 10 Dec 2013 15:06:38 +0000	[thread overview]
Message-ID: <9553e1bc09b92fde0bc2a8f650742c9c@quintile.net> (raw)

Hi,

In order to get remote access through a firewall I
currently have a script which I run on the inside
of the firewall which posts a file descriptor I
can mount from home.

while(~ true true){
	cpu -h home -c 'rm -f /srv/work ; srvfs work /mnt/term ; while() sleep 600 '>[2] /dev/null
	sleep 10
}

so at home I just:

	mount /srv/work /n/work
	bind /n/work/net /net.alt

This works but the performance is not great espicially
if I cpu into the work machine from home:

	cpu -u /net.alt/tcp!work

I assume the lack of zip is due to the multiple 9p round
trips necessary to establish the connection.

Is there a more elegant, and hopefully more performant way of
do this using import -B?

failing that any other techniques?

sadly ssh -R isn't very useful on plan9 (I think).

-Steve



             reply	other threads:[~2013-12-10 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 15:06 Steve Simon [this message]
2013-12-10 16:56 ` Conor Williams

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=9553e1bc09b92fde0bc2a8f650742c9c@quintile.net \
    --to=steve@quintile.net \
    --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).