<> > > 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. > > That's ridiculous. Run _one_ node per LAN.
Sorry Mark, but the "one computer, one node" rule is something I picked up from Oskar (I think), and I decided I agreed with him (and not just because he's Oskar). Freenet works better with lots of smaller nodes to spread the data out then to have a few really big nodes. I think the optimal solution is to have each computer on the LAN to have a 50-200 MB store (non-transient) with the main node having a 1-2 GB store. Node announcements always go through the main node. You can skip a few computers if you have security concerns (such as on a web server). Then set your LANs firewall to block everything incoming and outgoing (except what is explicity allowed; you should do this anyway). Allow the main node to go out on the various Freenet ports. This should make it so that internal nodes don't learn about nodes outside the LAN (except for the main node). They will "learn" about new nodes when requests are sent through the main node, but those new nodes will be flushed when they can't contact that node because of the firewall. _______________________________________________ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
