On Thu, 31 Jul 2003, Simon Wade wrote: > I downloaded the latest freenet disto, installed it on > Mac OS 10.2 and ran it using JDK 1.4.1_01. The first > time I ran it, the localhost:8888 page can up with no > images and each of the links lead to an error page, so > I restarted the freenet and got slightly better > results.
On new nodes I've set up it usually takes a good ten minutes before the images on the gateway page (localhost:8888) will show up. Those images are called activelinks and they come from within Freenet, not from fproxy (the HTML interface found at localhost:8888), so they take time to load. As you said elsewhere in your email, it takes time for your node to integrate into the network. Much more time than other P2P networks. Consequently, restarting will not help, and in fact will hurt. Even my well-connected node will slow down considerably after I restart it. You're right, it's a drawback, but it's not something that can be tracked down and squished, like a bug. What kind of error pages did you get? What did they say? There are two general errors you can get. One is a "Route Not Found". It means something is wrong, and it's pretty rare. The other is a "Data Not Found". These are somewhat common. They're nothing serious, it just means that the node sent out a request for the information you wanted, and wasn't able to find it. It may not exist, or it may exist but not on any of the nodes your request came to. If you leave the DNF error page there, it'll auto-refresh after a minute. When it does that it sends out a request again, but this time with a higher Hops To Live (HTL) value. For the links on the gateway page, they all should exist (except maybe YoYo), so letting the DNF page auto-refresh once or twice will usually find it. After getting the data that first time, subsequent tries will be much faster, and will improve with time. > I then > ran the update.sh script, ran freenet again, and it > came up with errors in the terminal saying that it > couldn't determine my IP and asking me to specify my > ip in the config file. So I opened the config file, > only to find that it had been overwritten by the > update and there were only two lines in there. I had a > look around and found that I should remove the config > file and run freenet again to go through the setup > questions. Having got my config file back, I tried to > use the system again with similar results. You're running Windows, correct? This *is* a bug, and the squishers are actively tracking it down. > I understand that Freenet is not going to perform well > until it has had an opportunity to learn about its > environment and gather information about other nodes, > but I was surprised by how poorly it behaved when I > ran it for the first time. I should add that I am not > a novice computer user, and have been doing > network-related programming for about four years now. I had the same experience, first time I ran Freenet (about two years ago). I couldn't get any of the links to load, and I waited forever! I ditched it and didn't come back until several months later. I was able to get it to work then. It has gotten a thousand percent better since then, and yet it's still a big problem for Freenet. By the way, have you gotten it to work yet? -todd _______________________________________________ Tech mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/tech
