From: Conor Williams <conor.williams@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] punching through firewalls...
Date: Tue, 10 Dec 2013 16:56:48 +0000 [thread overview]
Message-ID: <CAL6pNZ_3e7WD-jqqRNGEPxmryrFATVK3=MVUBd5CSViK1VnO6g@mail.gmail.com> (raw)
In-Reply-To: <9553e1bc09b92fde0bc2a8f650742c9c@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
----
I will take a look at coding in the -R flag for this Steve...
Gonna take a while as I will have to re-up my Plan 9 network...
... or is that it??
cw5
----
...thing you'll want to do is ssh into your server but this time we're
going to pass a -R flag and a port number. That flag "Specifies that the
given port on the remote (server) host is to be forwarded to the given host
and port on the local side." Basically a reverse tunnel..
http://www.hackido.com/2009/06/quick-tip-set-up-reverse-ssh-tunnel.html
On Tue, Dec 10, 2013 at 3:06 PM, Steve Simon <steve@quintile.net> wrote:
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 2063 bytes --]
prev parent reply other threads:[~2013-12-10 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:06 Steve Simon
2013-12-10 16:56 ` Conor Williams [this message]
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='CAL6pNZ_3e7WD-jqqRNGEPxmryrFATVK3=MVUBd5CSViK1VnO6g@mail.gmail.com' \
--to=conor.williams@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).