On Mon, 18 May 2009 00:14:18 +, Jago Pearce wrote:
> This is my setup:
>
> 1) client computer with ssh forwarding on port 81 (ssh -D81) enabled
So this creates a SOCKS proxy on the remote ssh server you're
connecting to, accessable via port 81 on your local client computer.
>
> conecting t
On Mon, 18 May 2009 00:14:18 +, Jago Pearce wrote:
> This is my setup:
>
> 1) client computer with ssh forwarding on port 81 (ssh -D81) enabled
>
> conecting through
>
> 2) A proxy at address Proxy:8080
>
> 3) Connectng to my shell server runnig shh on port 443
>
> If I login with ssh I c
This is my setup:
1) client computer with ssh forwarding on port 81 (ssh -D81) enabled
conecting through
2) A proxy at address Proxy:8080
3) Connectng to my shell server runnig shh on port 443
If I login with ssh I can use lynx to browse freenet but that isn\'t very good.
How can I browse fr
On Fri, May 15, 2009 at 2:38 PM, Matthew Toseland
wrote:
> On Saturday 02 May 2009 11:09:37 theymos wrote:
>> Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209
> rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few
> hours ago. I updated using updat
On Fri, May 15, 2009 at 2:37 PM, Matthew Toseland
wrote:
> On Wednesday 13 May 2009 18:29:47 Evan Daniel wrote:
>> On Wed, May 13, 2009 at 7:33 AM, Matthew Toseland
>> wrote:
>> > On Friday 08 May 2009 17:40:58 Juiceman wrote:
>> >> >> Weird. node.db4o was an insane 375 MB. I deleted it and and
On Fri, May 15, 2009 at 2:38 PM, Matthew Toseland
wrote:
> On Saturday 02 May 2009 11:09:37 theymos wrote:
>> Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209
> rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few
> hours ago. I updated using updat