Date: Tue, 06 Jul 2004 00:37:19 +0200
From: Steffen Schwientek [EMAIL PROTECTED]
Subject: [freenet-support] start-problems
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
I can´t connect to my freenet-core. If I point my
browser to localhost:, i just get not found.
I started the freenet-daemon using the gentoo
freenet startup script, which certainly starts
an java engine, but I don´t know if it also start
freenet, since no log is written, and I can´t
connect to the freenet port.
I too am running Freenet from Gentoo (kernel 2.6.7), and my initial joy over
finding it in the portage tree and thus being able to simply emerge it was
quicly cooled by the fact, that the configuration E-build appears broken. It
would simply freeze after asking for my port number, and never get further.
This meant that the configuration file was never written.
I solved that problem by installing Freenet on a Windows PC and simply copy
the file freenet.ini to my Gentoo-box into /etc/freenet.conf.
I shall post it at the end of this mail. As you see, it looks pretty normal
apart from the file paths
Here you can also see, where the logfile ends up.
Notice also that I have the line...
... which allows everybody on the internet to connect to Fred through my
machine. This was only for testing purposes and should be changed to
something less dangerously.
Anyway - after you've gotten the freenet.conf taken care of (changed the
paths, entered your own IP and made a port redirect in your router for
whatever listenport you are using), it's simply a matter of starting the
And if everything seems to run smoothly, let it be started automatically at
Rc-update add freenet default
As far as checking whether it is running correctly, a ps -A should show you
not one, but a lot of java processes. And of course you should also be able
to connect to Fred in your browser.
Freenet runs very well on the Blackdown-JAVA that Gentoo installs - and so
--- my freenet.conf
# Freenet configuration file
# Note that all properties may be overridden from the command line,
# so for example, java freenet.node.Main --listenPort 1 will cause
# the setting in this file to be ignored
# * * * * * * * * * * * * * * * * * * * * * * * * * * *
# * --=== READ THIS!!! READ THIS!!!READ THIS!!! =---
# * + VERY IMPORTANT!! +
# * #something is a comment!
# * %something is ALSO a comment!
# * if you change any settings, REMOVE THE % IN THE BEGINNING OF THE
# * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
# Lines that start with % are settings that have been unchanged from
# default, and that are thus ignored by the node (so they don't linger
# when we want to change the default settings). If you change these
# settings you should remove the %.
# This file was automatically generated by Freenet.scripts.Setup (at
# The IP address of this node as seen by the public Internet. You only need
to override this if it cannot be autodetected, for example if you have a NAT
(a.k.a. IP Masquerading) firewall/router, in which case you will need to set
it to the IP address or DNS name of the internet-side interface of the
router, which needs to be static (www.dyndns.org and similar services can
help here if you have a dynamic IP).
ipAddress=Steffen Schwienteks IP goes here
# The port to listen for incoming FNP (Freenet Node Protocol) connections
# The port to listen for local FCP (Freenet Client Protocol) connections on.
# A comma-separated list of hosts that may connect to the FCP port
# (clientPort). If left blank, only the localhost will be allowed. If you
set this, make sure localhost is included in the list or access won't be
allowed from the local machine.
# May be given as IP addresses or host names.
# If this is set then users that can provide the password can
# can have administrative access. It is recommended that
# you do not use this without also using adminPeer below
# in which case both are required.
# If this is set, then users that are authenticated owners
# of the given PK identity can have administrative access.
# If adminPassword is also set both are required.
# Transient nodes do not give out references to themselves, and should
# therefore not receive any requests. Set this to yes if you cannot
# receive incoming connections, or