[freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
I have the same problem as described in Bug ID 0002694, after updating to latest freenet version, downloads fail - this happened with multiple keys. Klicking on restart in downloads menu does result in the same error immediately : "Temporary files error: invalid block type". I deleted the persistent-temp-* directory, after that the setup wizzard showed up (?), and all downloads were reset. I re-requested the download keys, and for the keys that failed before, the download failed again with the same error. I have not had a successfull downlaod after the update. This is the FIRST sever bug in freenet after my use of it for quite a while now. Although beeing beta it worked so far all the time. Functionality is fundamentally impacted. In case you need more info, reply.
[freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
I have the same problem as described in Bug ID 0002694, after updating to latest freenet version, downloads fail - this happened with multiple keys. Klicking on restart in downloads menu does result in the same error immediately : "Temporary files error: invalid block type". I deleted the persistent-temp-* directory, after that the setup wizzard showed up (?), and all downloads were reset. I re-requested the download keys, and for the keys that failed before, the download failed again with the same error. I have not had a successfull downlaod after the update. This is the FIRST sever bug in freenet after my use of it for quite a while now. Although beeing beta it worked so far all the time. Functionality is fundamentally impacted. In case you need more info, reply. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] bug report: 2 peers forcibly disconnected due to not acknowledging packets
Version Information & Node Control Freenet 0.7 Build #1178 r23592M Freenet-ext Build #24 r23199 Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at support at freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 98.197.198.209:60008 * 78.70.60.132:30842
[freenet-support] bug report: 2 peers forcibly disconnected due to not acknowledging packets
Version Information & Node Control Freenet 0.7 Build #1178 r23592M Freenet-ext Build #24 r23199 Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 98.197.198.209:60008 * 78.70.60.132:30842 ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Route not found - stability next generation routing
Hello [EMAIL PROTECTED], first of all I want to thank the developers of freenet and freenet related tools for their work. It is a needed tool these days. However, I have been using freenet for some time - also before next generation routing started. My general experience is that the performance has gone worse: 1) After starting a new node version or not having it online for a while the node sometimes fails to establish a stable freenet connection. I fix this by deleting all rouing files (*_a und *_b in the freenet directoy) and downloading a new seednodes.ref file. However, this does not always work on the first attempt. 2) Even after having the node up for a wile and(!) successfully downloading content, the node more often fails to route the request to other nodes than before NG-routing. Wihtout NG routing I was able to have request returned with 25 HTL with a "data not found" error - a clear indication that the data was not there for sure. With NG routing I am having trouble to get a data-not found message at all, most of the errors I only get "route not found" with 1 or 2 nodes or even 0 being contacted. Now to my questions: a) is there a way to make my freenet node try to contact NEW nodes more often? For example by more aggressivle cleaning up the routing table? b) How can I tweak routing that my node (AFTER successfully receiving data!) does no longer think, it does no know where to deliver the requests to? c) Why does my node deliver "route not found" errors with onlny a few (<< 5) other nodes it tried to contact? How can I make it contact more nodes? (> 20) d) Do nodes tell each other about the nodes they know? e) is it easy to get involved in the freenet development? Since I am a software engeneer my own I have the impression that the ideas behind NG routing are reasonable, but the algorithm itself is not stable, yet. Esp in the special case of starting a node or having one that it not permanently online. I came to that conclusion because I have been reading the support-archive and was surprised, that some people even with NG-routing seem to have good performance (as I experienced it without NG routing). Thanks for any answers! Uli Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de ___ 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]