> > Every computer should be running a Freenet node anyway. There are ways > > to make Freenet work behind firewalls, though it's a bit tricky last I > > heard. Something like a Squid proxy server for Freenet is actualy > > redundant. > > I mean that from a security standpoint I would not want every machine on > my LAN running FreeNet. Not that I don't trust the programmers of FreeNet > but each new bit of ware you have to run on each machine is just one more > thing to worry about. The entire LAN is essentially running as a single > computer on the Net so it doesn't make sense to run more than one node and > it makes the most sense to run that node as part of the proxy server that > is already setup. There is already some proxy server FProxy or something > like that which lets you use a local machine to host FreeNet objects > within the web browser. Couldn't you just wrap that into an already > existing proxy server (once it reaches a stable API) to simplify > installation and admining?
If you really want this, why not set FProxy (or FwProxy, whatever) at your main node to accept the IPs of the machines on your LAN? Then they can all access the same node through a web browser. You could also set FCP/XML-RPC to accept those same IPs, and thus any FCP or XML-RPC based clients can go through there. _______________________________________________ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
