Pardon me if this is a stupid question, but I've been fighting Freenet for the last 45 minutes trying to figure out exactly how to get at the Freenet proxy from a different computer. The solutions in the FAQ and Questions & Answers on the web site aren't working for me. I'm running Freenet on my server located at 192.168.1.5, and I'd like to be able to get at it from my machine located at 192.168.1.2. Connections from my machine to http://192.168.1.5:8888 are simply refused. I can use the web interface with no problems from the server via VNC, but that's a pretty nasty way to use anything long-term. Below is my freenet.conf file, with comments removed. Please, any suggestions?You need "mainport.allowedHosts=*" in your freenet.conf (without the inverted commas). If you want to restrict who can connect, use a comma separated list of each host you want to be able to contact the server in place of the asterisk, no subnet syntax available, and make sure you include localhost (and perhaps 127.0.0.1) in the comma separated list.
Thanks,
Glenn M.
--freenet.conf--
[Freenet node]
ipAddress=[mydomain.net, removed by me]
listenPort=2105
%clientPort=8481
fcpHosts=localhost,192.168.1.2,192.168.1.3
fproxy.bindAddress=*
fproxy.allowedHosts=*
%adminPassword=null
%adminPeer=null
%transient=false
%doAnnounce=true
%seedFile=seednodes.ref
%diagnosticsPath=stats
%storeType=freenet
%nodeFile=
%storeFile=
storeSize=268435456
%storeBlockSize=4096
%storeCipherName=Twofish
%storeCipherWidth=128
%routingDir=
bandwidthLimit=50000
%inputBandwidthLimit=0
outputBandwidthLimit=15000
%averageBandwidthLimit=0
%averageInputBandwidthLimit=0
%averageOutputBandwidthLimit=0
%maxNodeConnections=60
%maxConnectionsPerMinute=60
%maxConnectionsMinute=60000
%logLevel=normal
%logFile=freenet.log
%logFormat=d (c, t): m
%logDate=
%rtMaxRefs=50
%rtMaxNodes=50
%maxRoutingSteps=40
%messageStoreSize=1000
%failureTableSize=1000
%failureTableTime=1800000
%routeConnectTimeout=10000
%maxHopsToLive=25
%announcementPeers=15
%announcementAttempts=10
%announcementDelay=1800000
%announcementDelayBase=2
%announcementPollInterval=900000
%announcementThreads=3
%initialRequests=10
%initialRequestHTL=15
%services=mainport,nodestatus
nodestatus.class=freenet.client.http.NodeStatusServlet
nodestatus.port=8889
distribution.class=freenet.node.http.DistributionServlet
distribution.port=8891
distribution.params.unpacked=.
distribution.allowedHosts=*
distribution.winInstallerFilename=freenet-webinstall.exe
%authTimeout=30000
%connectionTimeout=600000
%hopTimeExpected=4000
%hopTimeDeviation=7000
%maximumThreads=120
%doRequestTriageByDelay=true
%overloadLow=0.85
%overloadHigh=0.9
%requestDelayCutoff=500
%successfulDelayCutoff=3000
%blockSize=4096
%streamBufferSize=16384
%maximumPadding=65536
%logInboundContacts=false
%logOutboundContacts=false
%logInboundRequests=false
logOutboundRequests=false
%logOutputBytes=false
%logInboundInsertRequestDist=false
%watchme=false
%logInboundInsertRequestDist=false
%watchmeRetries=3
%logSuccessfulInsertRequestDist=false
%FECTempDir=
%FECInstanceCacheSize=1
%FEC.Encoders.0.class=OnionFECEncoder
%FEC.Decoders.0.class=OnionFECDecoder
%tempDir=
%localAnnounceTargets=null
There may be an advantage in using VPN, as all hosts except localhost contacting port 8888 seem to share any bandwidth limit with the internet-facing node port, and are thus slowed arbitrarily if there is a lot of traffic (indeed I wonder if downloads effectively are counted twice?). A proxy is another choice.
nodestatus.allowedHosts works similarly. This is probably documented on the web page, I must have got it from somewhere.
--
Roger Hayter
_______________________________________________
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
