[freenet-support] Backed off weirdness in freenet 1232
- Freenet 0.7.5 Build #1232 build01232 - Freenet-ext Build #26 r23771 So far I've understood the backoff percentages in advanced connection details but no longer. The attached picture shows what I'm saying. What ticks me off the most is being connected for over 90 minutes to peers that are 99,9 % of the time backed off. This defeats the purpose of having 32 peers with output of 90 kB/s. The bug I'm reporting is something I didn't see before. Note the values backed off wait time remaining and time total. Time total is now smaller than the time remaining. Seems to be happening with several peers. Hows about giving the peers a loser rating and connect the losers together. Sure they won't be able to download anything but they won't be slowing me down either, which is the most important thing, since I'm the most important person in the world. attachment: Backoff FAIL.png___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] How can a system administrator detect active freenodes?
Alex Pyattaev wrote: You know, I do think that freenet is a good idea. And in fact, until freenet users will consume too much traffic, i'm not going to ban them. Because i don't want to. In fact, right now 100.0% of major traffic consumers are using *other* P2P networks. Mostly torrents, some use mule DC, but they are much less pain - DC-like protocols never utilize 100% bandwidth due to long periods when noone is leeching from you. So the upload traffic is poorly utilized, and downloads are not so fast due to lack of seeders. So the major problem is torrent, which is extremely easy to detect and ban. And I like the idea. As of freenet, my interest is pure theory right now, since freenet users just don't bother be. If you like Freenet (cool that you do!) you could help the project: try to catch Freenet users on your network and report the results here, so developers would get valuable info. If you do catch someone, you could even (anonymously?) help him set up a more secure node, and then try to catch him again. The only problem that I can see here (and it may be kind of serious) would be: what if your bosses realize that you use resources, work hours, etc to catch Freenet users, and then you don't actually ban them? If you don't have a good excuse for that, may be better just forget the whole idea. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] How can a system administrator detect active freenodes?
The only problem that I can see here (and it may be kind of serious) would be: what if your bosses realize that you use resources, work hours, etc to catch Freenet users, and then you don't actually ban them? If you don't have a good excuse for that, may be better just forget the whole idea. Dude, don't worry. They are not that good=) and actually i like the idea. howeverm right now i have to finish the job on torrent and DC tracking. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Seednodes wanted: poor bootstrapping performance at the moment
In recent weeks a number of established seednodes have gone offline and/or changed IP without their owners sending me the new noderef. We are now down to 11 seednodes, but more importantly, bootstrapping is becoming a problem, with automated tests sometimes failing to get 10 nodes in 10 minutes, and often taking a long time. Twice in recent days I have tried to run sdiz's long-term tests, and both times it has failed to bootstrap on the fetch phase. Also bootstrapping is sometimes - apparently at random - very slow, e.g. staying at 2 peers for some time. An important part of the solution is more seednodes. If you have at least 256kbps upstream bandwidth (more is better), a stable 24x7 node, a static IP address or domain name, and have successfully forwarded your opennet port, please consider helping us out: - Go to config settings, go to advanced mode, opennet, enable be a seednode. - Email me your opennet noderef. You can get it from: http://127.0.0.1:/strangers/myref.fref It is also possible that this isn't the cause of the problem, maybe it is caused by the 1231 changes ... any thoughts? signature.asc Description: This is a digitally signed message part. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Missing changelog for build 1227
Sorry... I'll just post the commit changelog. object c5009c153b0745ad19f16e478fc619a8864d241c type commit tag build01227 tagger Matthew Toseland t...@amphibian.dyndns.org 1249153708 +0100 1227: 1224 mandatory 7 August Client layer: - Fix instant timeouts on startup trying to defrag with a big node.db4o. - Fix a wierd NPE probably related to stuff left over in the database from bugs. - Make the number of blocks defragged a constant. Web interface: - Fix forcedownload headers. On some systems force download was not forcing the file to be downloaded. Alerts etc: - Move disabling useralerts to the alerts page (from the welcome page). Saces says it wasn't working? Plugins: - LoadPlugin, PluginRemoved, RemovePlugin, ReloadPlugin. Run off thread. - Require Identifier in FCP GetPluginInfo. Dev stuff: - Indent. - Logging. - Fix a logging-related NPE on some site inserts. saces volodya toad signature.asc Description: This is a digitally signed message part. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Freenet 0.7 build 1232
Sorry folks, don't use 1231 (fortunately the upload to the auto-update didn't complete), it had a severe bug preventing startup. 1232 fixes this and also has some minor work on plugins. signature.asc Description: This is a digitally signed message part. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Freenet inside LAN
I've just found Freenet, and it looks really great. I've always considered freedom of speech pretty much the most important thing you can have, so I love what this is doing. Anyway, I've had what seems to be a good idea - set up people at my school to use freenet. I'm planning to bundle it with a few other apps (tor, firefox+privacy addons, utorrent, etc) and let people download it and put it on their flash drives, and run it whenever they get on a school computer. As they did this, they'd connect to a mini-freenet (darknet of course), within the school. The main problem I've got here is that freenet doesn't work over LAN, or at least I can't figure out how to make it do so. I don't want one computer on freenet, and the others running a browser pointed to 192.168.1.X. I want to set up a darknet composed of computers within the same LAN. If anyone knows how I could do this, or could suggest another way to do it (I tried WASTE, and couldnt get it going either) I would very much appreciate it. Thanks, Ellimistd ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
