> > > You shouldn't run into problems doing a direct copy, assuming you
> > > change the four ports mentioned in freenet.ini. You will simply have
> > > multiple instances of freenet running, each accessible via it's own
> > > http port, each accessing it's own udp data pipes/local sockets. I
> > > think.

> > thank you for getting back to me.
> > If I understand you correctly, if I copy the "freenet"
> > directory/subdirectories from machine A to another machine in a
> > different geographical location, say machine B, I don't need to do
> > anything but start the service (run.sh start). All of my
> > configuration files, trusted friends, etc. will be duplicated from
> > machine A to machine B. Then, a new KEY will be issued by machine B
> > that I can use to make friends with machine A. Correct?

> Oh ... hrmm ... right, each node has it's "identity key" ... stored in
> the opennet-OPENNETPORT and node-DARKNETPORT files. I'm not sure what
> would happen if two nodes with the same "identities" run at the same
> time. (They will, of course, but I'm not sure what, if any, collisions
> will happen. I don't think I want to find out either :b.) Perhaps (my
> wild guess) if you delete these two files they will be regenerated?

There is yet another problem.  The cache (both of them) will contain 
information from the originating Machine A.
It seems, there is no easy way to clone.

Support mailing list
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Reply via email to