> But if I understand, Freenet can't work on a network without fixed IP or dns server ? > Freenet can't work with an internal IP and port redirection from the external IP so no way to go throw a firewall ? > Lot of constraint for trying to make a free network with everyone.
Not exactly so. While Freenet can't work in, let's say, "passive" mode (when it only relies on opening connections, not accepting them) - a-la LowID clients in eMule, it certainly can work with dynamic IPs and port-forwarded firewalls. You can use any number of dynamic DNS services (such as www.dyndns.org), and many free utilities exist to automatically update dyndns records when your IP address changes. As outlined in another e-mail, there're only a handful of limitations, and some things to be aware of when using such a setup, but otherwise it works very well. I've been running Freenet in both ways - one NATted machine at work (with port forwarding from firewall - in fact, multiple forwardings through 3 NAT layers - don't ask!) and dialup (yes, it sucks) at home (with dynamic IP). > I am force to make a little program who will modify the freenet.ini for changing the IP and unloading and reloading Freenet? I wonder why so basic things are not implement in Freenet. First of all, continually restarting Freenet (say, more often then once every 30 minutes) will definetely not be good - it will have to renegotiate all peer connections, and that's a heavy stuff. Also, such drastic measures aren't required, in most scenarios. Last, but not least - some of the things you ask for _are_ implemented, others - aren't so easy, or considered not to be important by the developers. That's an open source project - so, of course, you're welcome to contribute in whatever area you see fit :-). Regards, Victor Denisov. _______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
