Most recent edit on 2006-04-04 17:12:44 by JaQa

Additions:
~1) If you are already running an older version of Freenet, for example Freenet 0.5, shut it down. You can turn it back on later, but it simplifies the install to turn it off at this point.

1. Run the installer:
2. Follow the prompts; choose power user mode if you want to set bandwidth limits and so on. You can enter your dyndns.org DNS address into the IP address box if you need to.
   
   Deletions:
   0) Shut down your existing 0.5 freenet node. You can turn it back on later, but it simplifies the install to turn it off at this point.

1) Run the installer:
2) Follow the prompts; choose power user mode if you want to set bandwidth limits and so on. You can enter your dyndns.org DNS address into the IP address box if you need to.

---

Edited on 2006-04-04 17:10:55 by JaQa

Deletions:

Installing Java

Freenet is written using the Java programming language. To run it you need Java installed on your machine. You may already have it but if not we strongly recommend you download the version of Java made by Sun, which can be freely downloaded from Java.com∞.
(Technical users : Blackdown worked fine last time I tried it if Sun's jre isn't an option for some reason, even though it was the ancient 1.4.1, but it's a hassle to set up. It doesn't include needed cryptography providers, so you have to download GNU Crypto∞ and edit the policy files to use it. Also Freenet 0.7 *does* run on GCJ, but slowly; we haven't been able to identify why yet.)

---

Edited on 2006-04-04 16:41:29 by JaQa [moved telnet interface connection details to other page]

Deletions:
10) type CONNECT:
Hit enter and then copy and paste the ID of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "lastGoodVersion" to "End".)
You should get response from the node that ID was added.
(to make nodes connected to each other both nodes must have added themselves to each other)
11) type STATUS again, you should now see your new added node/nodes and their state, if
you're lucky you will see something like this:
CONNECTED 24.30.37.118:11999 Dalm 0.9093123123143807 Fred,0.7,1.0,232 bias=1.0 reqs: pRO=1.0 (h=2) ins: pRO=0.0 (h=127)
And now you can participate in the test.
Please note:
Always use the most recent version.
I wish you Happy Testing :)

---

Edited on 2006-04-04 16:35:55 by JaQa [moved node swap to other page]

Deletions:
7) If possible, open or forward the udp port (the node.listenPort setting; you can see this in the Configuration page) in your firewall or nat (although Freenet should work without this for most NATs)
8) now you need to exchange IDs with other testers to get connected to the network
A good way to achieve this is to use an IRC client to join the #freenet channel on irc.freenode.net
9) Get your node reference from the Darknet∞ page on fproxy∞. It should look something like this:
lastGoodVersion=Fred,0.7,1.0,403
physical.udp=83.196.11.200:3000
identity=cfc89ce4d9b06f43040a0e4d08b159fedb8c3c7cb7894623afd5e5fd3a480afd
myName=hrm
location=0.816079058182507
testnetPort=4000
testnet=true
version=Fred,0.7,1.0,297
End
(this is a nodes ID). Copy and paste these lines to http://code.bulik.org∞. You will end up with a url like http://code.bulik.org/1500?raw∞. (Add ?raw if your url doesn't have it, because it makes life easier).
Do not enter a reference direct into IRC. You will get kicked from the channel.
On IRC, you may find others willing to give you their references. You must both enter each others' references (see below) for the connection to be successful. Don't be offended if someone doesn't want to give you their reference; strictly speaking, you should only exchange references with people you trust.

---

Edited on 2006-04-04 16:09:08 by JaQa

Additions:

Installing Freenet 0.7

Installing Java

Freenet is written using the Java programming language. To run it you need Java installed on your machine. You may already have it but if not we strongly recommend you download the version of Java made by Sun, which can be freely downloaded from Java.com∞.

Setting up a Freenet 0.7 node:

# RUN_AS_USER

4) This is fproxy, the primary built-in interface to Freenet 0.7. You can also telnet to port 2323 to get to the console interface:

$ telnet localhost 2323

Shut down the node (use the Fproxy homepage∞, it has a big fat shutdown button).
8) now you need to exchange IDs with other testers to get connected to the network
9) Get your node reference from the Darknet∞ page on fproxy∞. It should look something like this:

10) type CONNECT:
Hit enter and then copy and paste the ID of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "lastGoodVersion" to "End".)
11) type STATUS again, you should now see your new added node/nodes and their state, if

• If you are using Linux there are some optional tips and tricks which might make your life easier.
• BuildingFromSource

java -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Version

Deletions:
To participate in freenet alphatest we strongly recommend the following : Sun's jre or jdk.
Get it from Java.com∞.

Setting up a 0.7 node:

#RUN_AS_USER
4) This is fproxy, the primary built-in interface to Freenet 0.7. You can also telnet to port 2323 to get to the console interface.
Shut down the node (use the fproxy homepage, it has a big fat shutdown button).
8) now you need to exchange ID's with other testers to get connected to the network
9) Get your node reference from the Darknet page on fproxy. It should look something like this:
10) type CONNECT:
Hit enter and then copy and paste the ID (reference) of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "lastGoodVersion" to "End".)
11) type STATUS again, you should now see your new added node/nodes and their state, if
12) If you can't connect, check that your reference has a line beginning "physical.udp". If it doesn't, try FirewallAndRouterIssues.

• If you are using Linux here are some (optional) LinuxTippsAndTricks which might make your life easier.
• BuildingFromSource java -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Version
  
  

  ---

  
  Edited on 2006-04-04 15:53:03 by CynicalMoose [Added note about code.bulix.org]
  
  Additions:
  (this is a nodes ID). Copy and paste these lines to http://code.bulik.org∞. You will end up with a url like http://code.bulik.org/1500?raw∞. (Add ?raw if your url doesn't have it, because it makes life easier).

Do not enter a reference direct into IRC. You will get kicked from the channel.
On IRC, you may find others willing to give you their references. You must both enter each others' references (see below) for the connection to be successful. Don't be offended if someone doesn't want to give you their reference; strictly speaking, you should only exchange references with people you trust.
Hit enter and then copy and paste the ID (reference) of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "lastGoodVersion" to "End".)
12) If you can't connect, check that your reference has a line beginning "physical.udp". If it doesn't, try FirewallAndRouterIssues.

Deletions:
(this is a nodes ID). Copy and paste these lines into IRC.
Hit enter and then copy and paste the ID of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "lastGoodVersion" to "End".)

---

Edited on 2006-04-04 06:55:08 by NextGens

Additions:
Inserting content
They are three ways of inserting content at the moment :

1) use frost Frost∞
2) using jSite ∞
3) using telnet and FCP like true FCP hackers ;)

---

Edited on 2006-04-02 01:13:03 by TheBishop

Additions:
Exchanging node references over IRC

Use this to find out the version number without starting the node

java -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Version

Deletions:
$ java -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Version

---

Edited on 2006-03-31 16:43:29 by MatthewToseland [darknet page on fproxy]

Additions:
9) Get your node reference from the Darknet page on fproxy. It should look something like this:

Deletions:
9) type (in the tmci interface) STATUS and press ENTER

You should get some lines similar to the following:

---

Edited on 2006-03-29 23:33:53 by RobertGuerra

Additions:
$ java -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Version

---

Edited on 2006-03-28 21:03:20 by MatthewToseland [setuid]

Additions:
Now edit the run.sh to make it setuid to the new user:
#RUN_AS_USER
should become:
RUN_AS_USER=freenet
Then the node will run in its own user, and it will start when your computer starts. You can start it now by:
/etc/init.d/freenet-new start
This will become easier when we have some proper linux packages!!

---

Edited on 2006-03-28 20:55:46 by MatthewToseland [point users at the installer]

Additions:
0) Shut down your existing 0.5 freenet node. You can turn it back on later, but it simplifies the install to turn it off at this point.
1) Run the installer:
If you are on Windows, you may be able to simply go here, and click on the link:
http://downloads.freenetproject.org/alpha/installer/install.html∞
If you are on Linux you most likely will have to run from the command line:
javaws http://downloads.freenetproject.org/alpha/installer/freenet.jnlp∞
2) Follow the prompts; choose power user mode if you want to set bandwidth limits and so on. You can enter your dyndns.org DNS address into the IP address box if you need to.
3a) On Windows, the installer should set up the node to automatically run (as a service) on starting up your computer, and it will open a web browser pointing to http://127.0.0.1:8888/∞
3b) On Linux, the installer will provide a run.sh script. You will need to use this script to start it (./run.sh start). Then you need to open a browser pointing to http://127.0.0.1:8888/∞ yourself. However, you should probably take precautions to secure it:
Create a new user for Freenet:
adduser freenet
Make the Freenet node you just installed be owned by it:
chown -R freenet.freenet /usr/local/freenet
Add it to your startup scripts:
ln -s /usr/local/freenet/run.sh /etc/init.d/freenet-new
update-rc.d freenet-new defaults
(The above will work on Debian, not tested elsewhere!)
4) This is fproxy, the primary built-in interface to Freenet 0.7. You can also telnet to port 2323 to get to the console interface.
5) If you have another node on port 8888 fproxy, then:
Shut down the node (use the fproxy homepage, it has a big fat shutdown button).
Edit freenet.ini manually, and change fproxy.port=8888 to some other port, say 9888.
Start the node back up.
Start the other node back up.
6) Some config settings can be changed from the Configuration link from the homepage. Those that cannot, you have to shut the node down as above and edit freenet.ini. The config page will at least give you the basic documentation for each option, so it is still useful even if you have to shut down the node. You have already specified your bandwidth limit, port number, and IP address, if necessary, in the installer; you can change them in the config file or possibly through the Configuration link.
7) If possible, open or forward the udp port (the node.listenPort setting; you can see this in the Configuration page) in your firewall or nat (although Freenet should work without this for most NATs)

Deletions:
1) Download the following files and place them in the same directory (you may want to create a directory called "Freenet" for this):
http://downloads.freenetproject.org/alpha/freenet-cvs-snapshot.jar∞
and
http://downloads.freenetproject.org/alpha/freenet-ext.jar∞
2) From within the directory in which you saved these files, start the node with command (parameters in quare brackets [ ] are OPTIONAL):
Unix/Linux/OSX:
java -client -Xdebug -Xmx128M -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Node [<config filename>]
Windows:
java -Xmx128M -cp freenet-ext.jar;freenet-cvs-snapshot.jar freenet.node.Node [<config filename>]
Usually you won't need to specify a config file, so you can omit the last part.
Note: Newer builds have a command parser listening on a port (in config file 'tmci.port'). It is possible to connect to this port using netcat hostname tmci-port' or telnet, and enter commands there. It seems no longer possible to enter commands directly via stdin, so you might as well start freenet as a daemon or in the background.
Also, note that all of the following can be done via the webinterface. Simply point a browser to the fproxy host / address, and go to 'configuration' for initial setup, and 'darknet' for connections.
The node will pick a port randomly. You can override this in the config file later on.
3) Once your Freenet node starts, there will be a delay, and you can access its command line interface (newer builds use the tmci port, see above), type HELP to get a list of commands. Type QUIT to exit.
4) Open freenet.ini (or whatever you called the config file) in a text editor, and customize it as necessary. If you need to use a specific port, edit node.listenPort; if you need to tell the node your IP address, edit node.ipAddressOverride; if you need to set a bandwidth limit (outgoing bytes only), set one in node.outputBandwidthLimit. The file should already contain the defaults for all available options. Note the port number from node.listenPort. This is important, and is displayed also when the node starts, and when you type STATUS in the GUI.
5) Start the node up in the same way you did before.
6) give your node a name via the tmci interfae:
NAME:<your new node's name>
7) If possible, open or forward the udp port (the node.listenPort setting) in your firewall or nat (although Freenet should work without this for most NATs)

---

Edited on 2006-03-28 20:30:34 by MatthewToseland [GCJ]

Additions:
(Technical users : Blackdown worked fine last time I tried it if Sun's jre isn't an option for some reason, even though it was the ancient 1.4.1, but it's a hassle to set up. It doesn't include needed cryptography providers, so you have to download GNU Crypto∞ and edit the policy files to use it. Also Freenet 0.7 *does* run on GCJ, but slowly; we haven't been able to identify why yet.)

Deletions:
(Technical users : Blackdown worked fine last time I tried it if Sun's jre isn't an option for some reason, even though it was the ancient 1.4.1, but it's a hassle to set up. It doesn't include needed cryptography providers, so you have to download GNU Crypto∞ and edit the policy files to use it.)

---

Edited on 2006-03-18 17:15:42 by BlaatSchaap [added note about fproxy configuration]

Additions:
Also, note that all of the following can be done via the webinterface. Simply point a browser to the fproxy host / address, and go to 'configuration' for initial setup, and 'darknet' for connections.

---

Edited on 2006-03-18 17:09:54 by BlaatSchaap [added comment about tmci]

Additions:
Usually you won't need to specify a config file, so you can omit the last part.
Note: Newer builds have a command parser listening on a port (in config file 'tmci.port'). It is possible to connect to this port using netcat hostname tmci-port' or telnet, and enter commands there. It seems no longer possible to enter commands directly via stdin, so you might as well start freenet as a daemon or in the background.
3) Once your Freenet node starts, there will be a delay, and you can access its command line interface (newer builds use the tmci port, see above), type HELP to get a list of commands. Type QUIT to exit.
6) give your node a name via the tmci interfae:
9) type (in the tmci interface) STATUS and press ENTER

Deletions:
Usually you won't need to specify a config file, so you can omit the last part.
3) Once your Freenet node starts, there will be a delay, and you can access its command line interface, type HELP to get a list of commands. Type QUIT to exit.
6) give your node a name:
9) type STATUS and press ENTER

---

Edited on 2006-02-22 00:00:36 by 82-32-17-1.cable.ubr03.azte.blueyonder.co.uk [config rewrite changes invocation]

Additions:
java -client -Xdebug -Xmx128M -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Node [<config filename>]
java -Xmx128M -cp freenet-ext.jar;freenet-cvs-snapshot.jar freenet.node.Node [<config filename>]
Usually you won't need to specify a config file, so you can omit the last part.
The node will pick a port randomly. You can override this in the config file later on.
3) Once your Freenet node starts, there will be a delay, and you can access its command line interface, type HELP to get a list of commands. Type QUIT to exit.
4) Open freenet.ini (or whatever you called the config file) in a text editor, and customize it as necessary. If you need to use a specific port, edit node.listenPort; if you need to tell the node your IP address, edit node.ipAddressOverride; if you need to set a bandwidth limit (outgoing bytes only), set one in node.outputBandwidthLimit. The file should already contain the defaults for all available options. Note the port number from node.listenPort. This is important, and is displayed also when the node starts, and when you type STATUS in the GUI.
5) Start the node up in the same way you did before.
6) give your node a name:
7) If possible, open or forward the udp port (the node.listenPort setting) in your firewall or nat (although Freenet should work without this for most NATs)
8) now you need to exchange ID's with other testers to get connected to the network
9) type STATUS and press ENTER
10) type CONNECT:
11) type STATUS again, you should now see your new added node/nodes and their state, if

Deletions:
java -client -Xdebug -Xmx128M -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress, default: autodetect>] [<bandwidth limit, default: 15>]
java -Xmx128M -cp freenet-ext.jar;freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress, default: autodetect>] [<bandwidth limit, default: 15>]
So for example:
... freenet.node.Node 4000 123.123.123.123 50
Starts a node on 123.123.123.123 with FNP 4000 and a bandwidth limit of 50 "big packets" per second. A "big packet" is around 1200 bytes.
Notes:

• in the future you will always need to start the node with same port
• the bandwidth limit is in big packets per second, which are around 1200 bytes, the default is 15
• you do need to specify your external IP to use this, you can discover this easily using a service like http://myipaddress.com/∞

3) If possible, open or forward that udp <port> in your firewall or nat (although Freenet should work without this for most NATs)
4) Once your Freenet node starts, there will be a delay, and you can access its command line interface, type HELP to get a list of commands
5) give your node a name:
6) now you need to exchange ID's with other testers to get connected to the network
7) type STATUS and press ENTER
8) type CONNECT:
9) type STATUS again, you should now see your new added node/nodes and their state, if

---

Edited on 2006-02-16 10:36:29 by N8cb5.n.pppool.de

Additions:
2) From within the directory in which you saved these files, start the node with command (parameters in quare brackets [ ] are OPTIONAL):
java -client -Xdebug -Xmx128M -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress, default: autodetect>] [<bandwidth limit, default: 15>]
java -Xmx128M -cp freenet-ext.jar;freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress, default: autodetect>] [<bandwidth limit, default: 15>]
So for example:
... freenet.node.Node 4000 123.123.123.123 50
Starts a node on 123.123.123.123 with FNP 4000 and a bandwidth limit of 50 "big packets" per second. A "big packet" is around 1200 bytes.

Deletions:
2) From within the directory in which you saved these files, start the node with command:
java -client -Xdebug -Xmx128M -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress>] [<bandwidth limit>]
java -Xmx128M -cp freenet-ext.jar;freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress>] [<bandwidth limit>]

---

Edited on 2006-02-03 16:06:21 by siward.plus.com

Additions:
You should get some lines similar to the following:
lastGoodVersion=Fred,0.7,1.0,403
(this is a nodes ID). Copy and paste these lines into IRC.
Hit enter and then copy and paste the ID of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "lastGoodVersion" to "End".)

Deletions:
Copy and paste into IRC these lines:
(this is a nodes ID)
Hit enter and then copy and paste the ID of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "physical.udp" to "End".)

---

Edited on 2006-01-10 23:37:51 by CacoPatane

Additions:
Testnet Ports
In able to help with testing of the net, you will need to open/forward the testnet port. It is specified in your node ID under the 'testnetPort' tag.
When your chat program displays the node references like this:

Deletions:
when your chat program displays the node references like this:

---

Oldest known version of this page was edited on 2006-01-10 02:26:55 by TheBishop []
To participate in freenet alphatest we strongly recommend the following : Sun's jre or jdk.
Get it from Java.com∞.
(Technical users : Blackdown worked fine last time I tried it if Sun's jre isn't an option for some reason, even though it was the ancient 1.4.1, but it's a hassle to set up. It doesn't include needed cryptography providers, so you have to download GNU Crypto∞ and edit the policy files to use it.)

Setting up a 0.7 node:

To set up a node you need do following steps:

1) Download the following files and place them in the same directory (you may want to create a directory called "Freenet" for this):
http://downloads.freenetproject.org/alpha/freenet-cvs-snapshot.jar∞
and
http://downloads.freenetproject.org/alpha/freenet-ext.jar∞

2) From within the directory in which you saved these files, start the node with command:

Unix/Linux/OSX:
java -client -Xdebug -Xmx128M -cp freenet-ext.jar:freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress>] [<bandwidth limit>]

Windows:
java -Xmx128M -cp freenet-ext.jar;freenet-cvs-snapshot.jar freenet.node.Node <port> [<ip_or_dynamicdns_adress>] [<bandwidth limit>]

Notes:

• in the future you will always need to start the node with same port
• the bandwidth limit is in big packets per second, which are around 1200 bytes, the default is 15
• you do need to specify your external IP to use this, you can discover this easily using a service like http://myipaddress.com/∞

3) If possible, open or forward that udp <port> in your firewall or nat (although Freenet should work without this for most NATs)

4) Once your Freenet node starts, there will be a delay, and you can access its command line interface, type HELP to get a list of commands

5) give your node a name:
NAME:<your new node's name>

6) now you need to exchange ID's with other testers to get connected to the network

A good way to achieve this is to use an IRC client to join the #freenet channel on irc.freenode.net

7) type STATUS and press ENTER
Copy and paste into IRC these lines:

physical.udp=83.196.11.200:3000
identity=cfc89ce4d9b06f43040a0e4d08b159fedb8c3c7cb7894623afd5e5fd3a480afd
myName=hrm
location=0.816079058182507
testnetPort=4000
testnet=true
version=Fred,0.7,1.0,297
End

(this is a nodes ID)

8) type CONNECT:
Hit enter and then copy and paste the ID of the node you want to connect to. (As mentioned above the ID is [b]everything[/b] from "physical.udp" to "End".)
You should get response from the node that ID was added.
(to make nodes connected to each other both nodes must have added themselves to each other)

9) type STATUS again, you should now see your new added node/nodes and their state, if
you're lucky you will see something like this:
CONNECTED 24.30.37.118:11999 Dalm 0.9093123123143807 Fred,0.7,1.0,232 bias=1.0 reqs: pRO=1.0 (h=2) ins: pRO=0.0 (h=127)

And now you can participate in the test.

Please note:
Always use the most recent version.


I wish you Happy Testing :)

• If you are using Linux here are some (optional) LinuxTippsAndTricks which might make your life easier.
• BuildingFromSource

Running a node - Tips and Tricks

when your chat program displays the node references like this:

... just enter "connect:" and [enter], and then paste the text like seen above, it works!