Hi.
Thanks for all the input, i have got, regarding this issue. I think, the
problem is because i'm behind a firewall, when i'm not at home. Because
when i'm at home, i can access my node through my local network, vith my
public ip. Så, what i did, was set up at ssh tunnel, and now i can
acces
Greg Wooledge <[EMAIL PROTECTED]> writes:
> mainport.port=
> mainport.bindAddress=*
> mainport.allowedHosts=127.0.0.1,192.168.2.1,192.168.2.2,192.168.2.4,192.168.2.20
>
> $ netstat -ant | grep
> tcp0 0 0.0.0.0:0.0.0.0:* LISTEN
> tcp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After trying various things to get 539, 537, or any version of fred
working, I renamed my datastore directory, to reset it. That worked.
The problem is that I have a 20GB datastore that was corrupted, I think.
Since this is the native filesystem (no
On Mon, Dec 16, 2002 at 02:11:12PM -0600, GeckoX wrote:
> I changed some settings in my conf file:
>
> was:
> inputBandwidthLimit=100
> outputBandwidthLimit=15000
> maximumThreads=180
>
>
> now is:
> inputBandwidthLimit=10
> outputBandwidthLimit=1
> maximumThreads=150
>
> Then I sto
Heine Laursen ([EMAIL PROTECTED]) wrote:
> Hi. I want to connect to my node (With my browser)
> mainport.allowedHosts=* #Have also tryed, with ip's
> mainport.bindAddress=xxx.xxx.xxx.xxx #(Public ip) have also tryed with *
These two are reversed. Here is what I use (on a Debian woody node,
kern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I changed some settings in my conf file:
was:
inputBandwidthLimit=100
outputBandwidthLimit=15000
maximumThreads=180
now is:
inputBandwidthLimit=10
outputBandwidthLimit=1
maximumThreads=150
Then I stopped fred with the stop script provid
This is an auto-generated response designed to answer your question as quickly as
possible. Please note that you will not receive a reply if you respond directly to
this message. We hope the directions below answer your question. If after following
the directions your problem is still unresolve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks. That seemed to do it. I deleted the rtnodes* and rtprops* files but I didn't
delete the lsnodes* files.
When I deleted the lsnodes* files and restarted, that seemed to fix it. Unfortunately,
I now have to start all
over with the routing tab
> Dec 16, 2002 8:18:45 AM (freenet.node.Main, main): loading routing table
> Exception in thread "main" java.lang.OutOfMemoryError
>
> Anyone got any ideas? I have a permanent node with a 30GB datastore...
>
> :GeckoX
Someone else posted a similar (identical?) problem. I'd hazard a guess
that you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just downloaded and installed build 539 and it won't start. Here's what the log
looks like when it dies:
Dec 16, 2002 8:17:23 AM (freenet.support.io.Bandwidth, main): new
Bandwidth(100,0,RECEIVED)
Dec 16, 2002 8:17:23 AM (freenet.support.io.Ba
I think, you have to add the following two lines to your freenet config
file:
mainport.params.servlet.1.params.bindAddress=*
mainport.params.servlet.1.params.allowedHosts=*
I have added this two lines, and i can connect to my node via the internet
from other computers. These two lines are also not
Hi. I want to connect to my node (With my browser)
Så, i have read some, of the former posts, about the problem,
but i simpley can't connect to my home node, and browse the freenet.
The home computer is a debian woody running kernel 2.4.19
My freenet.conf looks like this: (Ip's removed)
ipAddres
12 matches
Mail list logo
