Five Easy Steps To Installing Freenet Classic Opennet (FCon)

October 19th, 2011 | Posted in Anonymity, Blogging, Censorship, Freenet, Internet, Misc Assorted General Stuff, Open source, Privacy, Programming, Software, Technology, Tutorials | 3 Comments

Having recently announced the release of build 5110, the first new build of Freenet Classic Opennet (FCon) in well over two years it has occurred to me that it would be a good idea to put together a brief walkthrough of the installation process.

Because I’m a windows user and have never installed it on a Linux machine these directions are specifically for windows.  When I am able to I’ll do another walkthrough for Linux.

Freenet’s hardware requirements are, in modern terms, pretty mild.

Minimum:

400MHz Pentium 2, with at least 192MB of RAM.

Recommended:
1GHz or more processor with 256MB RAM or more.

As you can see most modern computers will far exeed these requirements.

*Note*

Back around 2004 I actually managed to run freenet on a 200mhz Pentium with only 64mb of ram running Windows 98.  It was very slow and sluggish but it worked enough to view freesites or use FIW to insert new editions of freesites

On my laptop with a 2.1ghz cpu and 2gb of ram I am able to run Freenet while running cpu intensive tasks like rendering high definition video and neither process will suffer any noticeable performance drop at all.

These steps should work the same on Windows 98, xp, and seven.  Windows Vista will probably be more of a pain but I don’t have a vista machine to test on.

1 get or already have Java JRE 7 from http://java.sun.com/javase/downloads/index.jsp

2 download the distribution archive at this url:

http://peculiarplace.com/freenet/downloads/freenet-0.5-build-5110.zip

and extract the archive to c:\freenet (or whatever directory you want.  I’m using c:\freenet for this example.)

3 use a plain text editor like notepad to edit flaunch.ini change the JavaExec= and Javaw= lines to point to where java.exe and javaw.exe are located. If you used the default install they will probably be in C:\Program Files\Java\jre1.7\bin\

4 edit freenet.ini

*note* remove the % from the beginning of any line you edit or freenet will ignore the change

You only need to edit these entries:

ipaddress=

If freenet cannot determine your IP address by itself, you will need to set it here.

listenport=

the port number that freenet will use to listen for incoming connections from other freenet nodes. You can change this to any number you like as long as it’s higher than 1024 and lower than 65535.  Do not use the same port number as another application

storeSize=

The size of the local data store.  The more space you allocate here the better.  It defaults to one gigabyte (1G) however you can increase this to however much space you can spare.

At this point you can save freenet.ini and close the editor.  It’s very likely that you could never need to edit this file again.

4-a make sure that incoming TCP traffic on listenport is forwarded to the computer freenet is running on (see your router or firewall docs for how to do this)

4-b optional (but very convenient), get a http://dyn.com/dns/dyndns-free/ domain name & use dynupdate to keep it pointed at your IP address, then put that name in ipaddress in freenet.ini

5 create a shortcut to “freenet.exe” and put it on your desktop, program menu or if you want freenet to start when the computer boots, put the shortcut in the “StartUp” entry of the program menu.

Double click on the freenet.exe shortcut to start freenet.  When Freenet starts, you’ll see the blue rabbit icon in your system tray by the clock.  Right-Click on it to start and stop Freenet.

To open the Freenet web interface you can either double click on the rabbit icon in the system tray, right click and select “open gateway” or just type http://127.0.0.1:8888 into your web browser.

*NOTE* The “Configure” option on that right click menu will try to run a utility called “Nodeconfig.exe” You are infinitely better off to simply stop freenet temporarily and edit freenet.ini yourself instead.  In most cases editing that file will be a VERY rare need.  Once Freenet is working you may well never need to edit it.

Because in my experience the “Nodeconfig.exe” utility has caused more problems than it’s worth by overwriting perfectly good freenet.ini files when all I wanted to do was tweak a setting I have elected not to include it in this distribution.

As a result, clicking “configure” will result in an error message because the program isn’t there.  Just dismiss the error message and use a plain text editor like notepad to edit freenet.ini directly.

[tags]freenet classic opennet, fcon, freenet, freenet 0.5, install, install guide, install walkthrough, install freenet, install fcon, anonymity, anonymous publishing, privacy, internet, encryption, anti-censorship, censorship proof, censorship, freedom of speech, freedom of speech online[/tags]

If you enjoyed this post, make sure you subscribe to my RSS feed!
Link to this post:
Just copy this code and paste it on your site where you want the link to appear:

3 Responses to “Five Easy Steps To Installing Freenet Classic Opennet (FCon)”


  1. […] video that was here has since been deleted due to an accident. However there is an up to date post, Five Easy Steps To Installing Freenet Classic Opennet (FCon) that I think does a much better job of walking you through the FCon install […]


  2. Good to see you’re still working the 0.5 net.  I think this 0.7 stuff has made my java-fu go soft, tried to start my old node up and got about 20 lines of errors.  Can you refresh my brain on why the ‘Exception in thread “main” java.lang.NoClassDefFoundError’ would show up under *nix?


  3. Unfortunately I haven’t much knowledge of *nix or the differences between freenet on *nix as opposed to windows.  I’ve meant to learn more about it and even get a Kubuntu system going but there’s always been other stuff to deal with first and a lack of enough hardware.

    As for the error message, I’ll have to dig into the source and see what I can find out.  Does the error message give any more details or does it just stop there saying that there is an error without any further clue about where it is?