On Sat, Jul 25, 2009 at 1:39 PM, Salman Aljammaz 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, on
On Sat, Jul 25, 2009 at 9:39 AM, Salman Aljammaz 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, on
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.
> traceroute can't get to that IP address, so I'm pretty sure the corporate
> firewall is doing its job.
traceroute failure just means that someone is not passing icmp
traffic. the only thing you know is icmp traffic won't pass.
here's a dirty trick you can do with plan 9 traceroute:
; ip/tracer
Why not run inferno (or 9vx) on your home machine, export /net on port
80, mount it from work using inferno again, and you are out.
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-
There are several places which have readonly versions of sources available via
http, alternatively there is a socks client or even htfilefs, the former uses
the SOCKS protocol to tunnel through the firewall.
htfilefs mounts a remote ISO image (like the plan9 nightly build iso)
over an http connect
On Fri, Jul 24, 2009 at 23:35, andrey mirtchovski wrote:
> Just checking: have you tried accessing it by IP address
> (204.178.31.8) rather than hostname? (this, of course, assumes that
> you've ruled out a bad ndb configuration as the reason).
>
traceroute can't get to that IP address, so I'm pr
Just checking: have you tried accessing it by IP address
(204.178.31.8) rather than hostname? (this, of course, assumes that
you've ruled out a bad ndb configuration as the reason).
how about trying with a 9p client such as cl.py from your "normal" machine?
$ cl.py n...@sources.cs.bell-labs.com
9
