>I control a unix (linux enterprise) server for my web sites.  Can I run a node on 
>this and access it from home?  Obviously typing will not pull 
>it up since it is at a server farm in another state. 

by default the only host which is allowed to connect to the node interface on port 
8888 is localhost ( this is to forbid everyone else but the owner of the 
machine to access the node.

in your freenet.cont/.ini there is a line reading:

# List of IP addresses (for example ""), DNS names ("erica" or 
"www.nsa.gov") or netmasks ("") of hosts (computers) that should be 
allowed to access the main web interface of your 
freenet node. Defaults to localhost ( only.

here you can change the array of allowed host for example to:
where is the ip of your xp computer.
please remember to remove the heading % which is a comment character!

you should also notice that connecting from your xp to the freenet node is now done 
over unencrypted http. this means that if you're being sniffed your actions can be 
seen and every file you retrieve out of freenet 
will be unencrypted, too, which will utterly destroy the principle of privacy. if 
you've got nothing to hide that *might* be okay, but ipspoofing/-claiming will allow 
others to access your freenet node, which might have 
negative effects on your reputation ;)

so the better alternative would be:
create a ssh tunnel from the linux box to your xp system (or vice versa). see 'man 
ssh' and look for the -L and -R options. on your windoze box you can try PuTTY which 
has a (hidden?) ssh daemon function; or use 
a different ssh tunnel software.
this will protect your traffic and authorize the node access.
that's the way you should choose to go

>Also, if I have a router at home and 2 comps (XP machines) can I have each computer 
>running a node?

of course, just make sure the FNP ports of each node are different (they're chosen 
randomly, so they are usually different) and forward the two ports from the router to 
the according xp box.

you can even have more than one node per computer! if so, you should change the ports 
for the mainport (8888) and the fcp port (8481) for the second node to something else 
(you could possibly just add +1) so 
they don't affect each other.

>With the above resources how do I get the most out of it? (configuration).  My 
>BIGGEST thing is speed. I hate not finding what I am looking for and I hate file not 

uhm, transfer speed of a splitfile is great and is able to easily max out your 
connection as the split-file is retrieved in parallel from different sources.
overall, freenet has a large latency but usually a nice transfer speed.

404's are sadly quite common as the node first has to 'weave' itself into the freenet 
network before it can archive decent performance and knowledge of the surrounding 
after that process it's supposed to run quite okay
you just shouldn't be afraid of letting the node run 24/7 for at least a week or so 
(i'd say, the opinions differ) to let the node become part of the network.
also be prepared that a node can use up large amounts of the network bandwidth 
resulting in massive transfer volumes. several gigs per month are common.

>What would be better, unstable or stable?

unstable is the testfield but has all the fixes first.
stable is more pleasant and is updated quite regulary, too.
if you choose to run an unstable node you ought to update the node every single day as 
the unstable branch progresses very fast

don't worry, your node will automatically tell you when a newer version is available 
(by noticing new build numbers within the network)



Support mailing list
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support

Reply via email to