The only support for this at present is the fproxy.bindTo option (which can only take one address, so if you make it accessible to your LAN it's not accessible to localhost).
On Mon, Apr 10, 2006 at 03:11:37PM +0200, Lars Juel Nielsen wrote: > On 4/8/06, Chris Johnson <cajohnson99 at hotmail.com> wrote: > > Hello, > > > > I'm trying to access freenet from another computer on the same network. I've > > searched a lot for this problem. I keep reading that I should add these > > lines to freenet.ini: > > > > mainport.bindAddress=* > > mainport.allowedHosts=127.0.0.1,192.168.1.0/24 > > > > I'm using the new 0.7 version. In my ini file, those lines don't exist. I > > can add them, but when the daemon restarts, the lines are removed. Are > > these not the correct lines to add? > > _______________________________________________ > > That's how it was done in 0.5 but I haven't seen anything about how to > do it in 0.7 or if it's even possible. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/support/attachments/20060410/225913b8/attachment.pgp>
