From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port behind corporate firewall with no DNS or port access
Date: Sat, 25 Jul 2009 09:55:16 -0700 [thread overview]
Message-ID: <7d3530220907250955r56a13db8pf83e00861d4e5c41@mail.gmail.com> (raw)
In-Reply-To: <20090725163952.GA25352@finiteless.net>
On Sat, Jul 25, 2009 at 9:39 AM, Salman Aljammaz<sio@finiteless.net> wrote:
> Uriel wrote:
>> If your work firewall proxies port 80, then things get trickier, you
>> could mount sources on the home inferno instance, and then export it
>> using mjl's httpd as a read-only http 'tree'.
>
> assuming you've got openssh, one trick i used to do back in school was
> run sshd on on port 443.
>
> you can then forward specific ports (-L) or even run socks (-D) on ssh.
>
> salman
>
>
>
If you have even one single port open outgoing, all you need is to get
a remote Plan 9/Inferno exporting /net on that port. I did it on port
22 while I was waiting for the import port to be opened.
#on the outside box
aux/listen1 -t 'tcp!*!22' /bin/exportfs
#from the inside
import -A tcp!remote!22 /net
You're using p9p so your mileage may vary... but the basic concept is
sound and allows you to completely avoid the firewall, assuming you
can actually use a remote /net on p9p. If not, well, you should run a
real Plan 9 :)
John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba
next prev parent reply other threads:[~2009-07-25 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 4:06 Jason Catena
2009-07-25 4:35 ` andrey mirtchovski
2009-07-25 4:55 ` Jason Catena
2009-07-25 13:56 ` erik quanstrom
2009-07-25 8:12 ` Steve Simon
2009-07-25 12:43 ` Uriel
2009-07-25 16:39 ` Salman Aljammaz
2009-07-25 16:55 ` John Floren [this message]
2009-07-25 16:56 ` Iruata Souza
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=7d3530220907250955r56a13db8pf83e00861d4e5c41@mail.gmail.com \
--to=slawmaster@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).