Hint: All these settings can also be made through FProxy
You can run the Freenet server on one machine and allow other machines not running Freenet to access FProxy over the network. Note that this is a potential security hole, since you will be sending cleartext traffic over the LAN, so other LAN users can use packet sniffers to see what you're requesting.
To set this up, you have to change the bindTo settings in freenet.ini. For example, if you run your Freenet server on a machine with IP address 192.168.0.1, then you should change these settings:
console.bindTo=192.168.0.1 fcp.bindTo=192.168.0.1 fproxy.bindTo=192.168.0.1
You can also combine several IP bindings with a comma-seperated list:
fproxy.bindTo=192.168.0.1,127.0.0.1
This makes freenet listen to the defined interfaces, but still doesn't grant access for any hosts, which must be done explicitly. To do that add this lines:
console.allowHosts=192.168.0.0/24 fcp.allowedHosts=192.168.0.0/24 fproxy.allowedHosts=192.168.0.0/24
You could also allow single hosts, which might be slightly more secure:
fcp.allowedHosts=192.168.1.119
You will have to stop and restart Freenet in order for these changes to come into effect.
Remember that, if you have freenet running on a differen machine, you can't access it with http://127.0.0.1:8888. Instead you have to use the IP address to the one you set above; http://192.168.0.1:8888. Keep this in mind since freenet links often contain the 127.0.0.1 part.
