I think there is a flaw in freenet routing. For the problem described below,
I discovered the following:
When I am on machine B where node B is, if I use GetFiles
with -serverAddress address_of_A
I can retrieve the freesite with no problem, and it was super fast.
But after that, I thought B should now know where the data is from, and
store a local copy of it.
But is actually does not. So when I use GetFiles without the -serverAddress
tcp/127.0.0.1:port
I just cannot retrieve the site.
Again, I have A's address in B's nodes.config to start with.
-----Original Message-----
From: fn20010618 [mailto:[EMAIL PROTECTED]]
To: Support@Freenetproject. Org
Subject: a question
This is really strange:
I have two nodes A and B. In the nodes.config file of A I have B, and vice
versa.
I have freenet:MSK@SSK@NLgvvGUTGnwgEN9jKEeC3G6jhEEQAgE/freenews/jingpian//
inserted in A. And I can access the freesite on the machine where A is with
no problem.
But on B I always get a "Cannot read Mapfile" error when I am using fproxy.
I refreshed many times. If I use manifest's GetFiles it just hangs there.
This just happens to certain freesites, occationally. I even inserted these
sites with htl=60. The above is just an example. At the same time, I can
get, on B, other freesites inserted in A with no problem.
If you have any idea how to solve such problems, I would appreciate it.
Thank you.
Peter
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
freenet-tech mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/tech
