If you have a question, ask it; if you see an unanswered question, answer it.
A: There is neither a convenient method for hiding the fact that a particular IP/port is running a Freenet node nor a reason to do so. This information is given out during normal node operation; there is no breach of sensitive information if the world at large knows who runs Freenet nodes. Freenet's anonymity protects one's actions on Freenet, not whether one participates in Freenet.
-- MichaelTerry - 22 Jan 2002
A: Open up the configuration panel and click the box marked "Import Default Node Refs". If none of them work, click the "Import New Node Ref" button and cut-and-paste a node from the FreenetNodes list on this website.
-- AfreeX? - 22 Jan 2002
A: Some JREs (especially older ones) don't seem to know the -cp setting, but replacing it with -classpath should make it work anyway.
-- EricAnholt - 25 Jan 2002 (edit by SebastianSpaeth)
A: In your freenet.conf or freenet.ini file, add the line: fproxy.bindAddress=* and comment out or remove the, fproxy.allowedHosts=blahblah line if it exists. You can also replace * with a comma-delimited list of allowed hosts.
-- SebastianSpaeth
I am using freenet v 0.4. Server is installed on linux box; it works perfectly. Attempting to access it from another system on my network fails.
tcpdump -ln port 8888 on the server reveals that requests arrive and no response is sent from the server.
My full config file is:
ipAddress=<external-ip-on-router>
listenPort=12249
seedNodes=seednodes.ref
fproxy.bindAddress=*
fproxy.class=freenet.client.http.FproxyServlet
fproxy.port=8888
fproxy.params.insertHtl=5
fproxy.params.requestHtl=15
fproxy.params.filter=true
fproxy.params.passThroughMimeTypes=text/plain,image/jpeg,image/gif,image/png
fproxy.params.pollForDroppedConnection=true
fproxy.params.splitFileRetryHtlIncrement=5
fproxy.params.splitFileRetries=0
fproxy.params.splitFileThreads=5
Please delete all this extraneous information (and for that matter my question). Change the answer for the previous question.
|