Varia

Go back to the Ultimate FAQ index

<300> Varia

[300] - Varia

[301] - What is fproxy?
[302] - How do I make FProxy accept connections from any computer, rather than just allowing connections from my own?
[303] - How do I get Freenet working with a Firewall/NAT?
[304] - How do I extract the necessary seedNode values from my own node?
[305] - Why are there so many messages in my logfile with a backtrace attached?
[306] - How can I zap my data store?
[307] - Why would I want to zap my data store?
[308] - I have a monolithic data store. Should I worry about the Data Store Bug?? What can I do about it?
[309] - How do I generate a pair of SSK-keys?
[310] - After an update, will I have to reseed the node?

[301] What is fproxy?

FProxy is a Freenet plugin included and switched on by default which allows you to access Freenet through your web browser. If you are using Freenet now you are probably already using FProxy. In practical terms, this means that you can surf Freenet as you might surf the World Wide Web.

In recent versions of Freenet, the "fproxy" service has been replaced by "mainport", so you may not find references to fproxy in your configuration any longer. Nevertheless, it seems likely that people will continue to refer to the web browser interface by the name of FProxy.

[302] How do I make FProxy accept connections from any computer, rather than just allowing connections from my own?

In your freenet.conf or freenet.ini file, add the lines:

mainport.bindAddress=* mainport.allowedHosts=127.0.0.1,192.168.1.1,192.168.1.2

such that the allowedHosts line contains the list of all the IP addresses you wish to allow access to the fproxy port. Be sure to include 127.0.0.1 so you can talk to your own node!

Older versions of Freenet had lines beginning with "fproxy.". The mainport service replaces both fproxy and nodeinfo (or rather, it consolidates them into a single service running on one port).

In Freenet 0.5.0.1 and later, mainport also supersedes the nodestatus service.

Note that the connection from the remote host using your fproxy is also limited by the bandwidth throttle you may have used. But I've read that machines from the same subnet (eg. 10.0.0.12 and 10.0.0.89) wouldn't be subject to such limitation.

[303] - How do I get Freenet working with a Firewall/NAT?

Edit your freenet.conf or freenet.ini file, change the ipAddress setting to be the IP address of your firewall or NAT. Also note the listenPort setting, or change it to whatever port you want Freenet to listen on.

You now need to configure your firewall/NAT to forward incoming connections on the listenPort to the computer on which you Freenet node is running. Many modern firewalls and NATs have a web interface to do this, or if you do not administer the firewall, you will need to ask your system administrator to do this.

If everything fails, try using a remote freenet gateway (fproxy). You can use either a ssh forward or a secure proxy to connect to the remote gateway. Of course, you have to trust the proxy or the ssh shell system admin so he/she won't log your activities and know what freenet keys you are retrieving. A secure (SSL-backend) proxy is not imperative in case you don't care about anonimity and just want to surf freenet. Of course, I really discourage you to do that.

[304] - How do I extract the necessary seedNode values from my own node?

java freenet.node.Main --export myreference.ref

Make sure your classpath is okay or use -cp/-classpath.

Alternative, under Windows, the windows_systray_app? can be used:

Right-click the freenet icon in the systray? Select 'Export Ref' from the popup menu. You will be asked to provide a filename and the seedNode will then be exported.

[305] - Why are there so many messages in my logfile with a backtrace attached?

The development version (0.4) of fred outputs a backtrace if a log entry is triggered by an exception. To turn it quiet you must change the java source in Freenet/support/Standard Logger??.java the relevant parts are calls to printStackTrace

[306] - How can I zap my data store?

java -jar freenet.jar --resetDS

[307] - Why would I want to zap my data store?

Older version 0.4 Freenet nodes used a "monolithic" data store, which built a file system inside a single huge file on disk. The code to manage this data store was complex, and had bugs (the infamous Data Store Bug?) which caused it to become corrupt periodically, requiring the node operator to reset the data store before the node could be restarted.

In theory, this should not happen to a native data store, which is the default for nodes running newer versions of Freenet.

[308] - I have a monolithic data store. Should I worry about the Data Store Bug?? What can I do about it?

In a word, yes. Some people have run monolithic data stores for months without corruption. Other people can't run for more than a few hours without corruption. You have 3 options:

Option #1: leave it running as is. It may eventually corrupt itself, at which time you can delete it, or reset it and start over.

Option #2: you can delete it and start over with a new native data store. To do this, delete the store_NNNN file from your Freenet directory, and then set

storeType=native

in your freenet.ini or freenet.conf file.

Option #3: you can set

storeType=convert

in your freenet.ini or freenet.conf file, and if you have enough free space in your Freenet directory, Freenet will attempt to convert your monolithic data store to a native one. However, if your monolithic data store is already corrupt (even if the corruption wasn't enough to make the full Data Store Bug? appear and prevent the node from starting), the conversion may fail. If the conversion fails, go to Option #2.

[309] - How do I generate a pair of SSK-keys?

fcpputsite -g NOTE: fcp generates a keypair in a different way fishtools do. FCP does not include the P Ag M? at the privkey before generating the public one. What happens is that when you try to publish your site with fishtools and give it your privkey without the "P Ag M?" so that it does its job, it will generate a public key that is actually different from the one FCP did, because it will by default force the addition of P Ag M? to the privkey in order to calc the pubkey. Just read fishtools doc in order to make it ignore the lack of P Ag M? in your privkey.

[310] - After an update, will I have to Reseed the node?

No. When you seeded the node and successfully connected to the Freenet at large, entries for newly-discovered external nodes were added to your node's Routing Table?. Barring bugs, the routing table stays populated between restarts, so your node should automatically 'remember' all of the ones that it previously discovered upon restart.