From level13 at gmail.com Sat Nov 1 21:09:49 2008 From: level13 at gmail.com (Level 13) Date: Sat, 1 Nov 2008 22:09:49 +0100 Subject: [freenet-support] Ports to forward, hostname (dyndns) Message-ID: <8e767170811011409k1eaba193xc282a7b91d686afc@mail.gmail.com> Is it enough to portforward listen-port and opennet-listen-port on your NAT router in order for a 0.7 node to work properly (so two ports here as opposed to one port in 0.5)? How about the dyndns hostname, where do you have to put it (that is, if this function is still the same as it was on 0.5, so if you have a dynamic IP you can use a dyndns hostname)? From luke771 at gmail.com Sat Nov 1 22:27:25 2008 From: luke771 at gmail.com (Luke771) Date: Sat, 1 Nov 2008 23:27:25 +0100 Subject: [freenet-support] Ports to forward, hostname (dyndns) In-Reply-To: <8e767170811011409k1eaba193xc282a7b91d686afc@mail.gmail.com> References: <8e767170811011409k1eaba193xc282a7b91d686afc@mail.gmail.com> Message-ID: <20081101232725.b104460e.luke771@gmail.com> On Sat, 1 Nov 2008 22:09:49 +0100 "Level 13" wrote: > Is it enough to portforward listen-port and opennet-listen-port on > your NAT router in order for a 0.7 node to work properly Yes it's enough. >(so two ports > here as opposed to one port in 0.5)? One port if you only run Darknet or Opennet, or two ports of you run both. Another major difference with 0.5, besides the switch to UDP and the introduction of Darknet among other things, is that Freenet 0.7 does work even for users that for one or another reason can't forward any ports (for instance, those who can't access the router). These users can't connect to each other but they can still connect to anyone who can forward a port, so Freenet will work for them, as opposed to 0.5 where they could only load a bunch of extremely popular freesite. >How about the dyndns hostname, > where do you have to put it (that is, if this function is still the > same as it was on 0.5, so if you have a dynamic IP you can use a > dyndns hostname)? You paste your dyndns address in the field marked 'override IP address' in the configuration page. -- FAFS - The Freenet Applications FreeSite USK at ugb~uuscsidMI-Ze8laZe~o3BUIb3S50i25RIwDH99M,9T20t3xoG-dQfMO94LGOl9AxRTkaz~TykFY-voqaTQI,AQACAAE/FAFS/41/ freemail: luke771 at MJWEES3VJBMS2ZKMIJUECT3SJB3UK5SBKBAVQYJQO5FXGWSROE2USNDKNMZU2SK2ORXUKLDZJYWXQUSNMRYUCWD6IF3HAULWKRKWW2SJJVEGQQTDNNKGYMRWKFZW6V3ONNIDKQ3DKR3SYQKRIFBUCQKF.freemail From robert.fallis at virgin.net Mon Nov 3 08:18:20 2008 From: robert.fallis at virgin.net (robert fallis) Date: Mon, 03 Nov 2008 08:18:20 -0000 Subject: [freenet-support] upgrading node Message-ID: I've been away for a few weeks. and I now get a message to upgrade my node. my node is set to automatic update but it has not worked, How do I upgrade my node? help please bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From Volodya at WhenGendarmeSleeps.org Mon Nov 3 08:42:52 2008 From: Volodya at WhenGendarmeSleeps.org (Volodya) Date: Mon, 03 Nov 2008 08:42:52 +0000 Subject: [freenet-support] upgrading node In-Reply-To: References: Message-ID: <490EB98C.4020104@WhenGendarmeSleeps.org> robert fallis wrote: > I've been away for a few weeks. and I now get a message to upgrade my node. > my node is set to automatic update but it has not worked, How do I > upgrade my node? > help please > bob > On Windows you can open Command Prompt and go to the folder where freenet is and type: update.cmd (i think that's what it's called there now) On *nix you go to the directory where you have installed Freenet and type: ./update.sh - Volodya -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut "None of us are free until all of us are free." ~ Mihail Bakunin From cineveggie.lists at gmail.com Mon Nov 3 14:44:10 2008 From: cineveggie.lists at gmail.com (Jeff Isaac) Date: Mon, 3 Nov 2008 08:44:10 -0600 Subject: [freenet-support] Node won't connect to peers 1167/68 Message-ID: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> Hello all! I have recently stumbled across a problem with my node. I noticed that Frost was having trouble communicating the other day even though the node was running. Sure enough, the node (at the time 1167) was not connecting to any peers (this after running successfully for a few weeks). I found the warning about 1168 and upgraded manually, but this still does not help. It took a while for the node to find 1168 nodes to connect to, and now I'm lucky if it will connect to one or two busy ones. I am not sure what it means, but often the one that is supposedly connected is highlighted in a yellow bar. I suspect my ISP is attempting to block my node, but it puzzles me that, if that be the case, it can still find anyone at all. All of my node's communication is halted at this point. Would reinstalling with a new node (and thus a new port) make a difference? Any help or suggestions would be appreciated! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081103/36c68059/attachment.htm From dennisn at dennisn.dyndns.org Mon Nov 3 14:42:10 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Mon, 3 Nov 2008 09:42:10 -0500 Subject: [freenet-support] Throttling isp crashes my freenet node Message-ID: <20081103094210.1432c8cd.dennisn@dennisn.dyndns.org> My freenet node keeps crashing on me. The wrapper.log file simply says... "Restarting node: MessageCore froze for 3 minutes!" ...at which point it begins to cleanly close the databases/datastores and does finally say a clean "Goodbye from freenet.node.Node at asdf (USM deadlock)". This term "deadlock" came up a couple of times. The phrase "PacketSender deadlock" also came up in the wrapper log file. Not coincidentally, I'm sure, in my freenet log files I get *tonnes* of PacketSender errors. I'm talking about thousands of these ERROR messages logged a minute, over a hundred per second. My freenet-previous.log file was 27MB! Pretty much exclusively messages like: "(freenet.node.KeyTracker, PacketSender thread for 12345, ERROR): Packet 72390 sent over 1719253ms ago and still not acked on freenet.node.KeyTracker at blabla" My ISP is notorious for throttling p2p traffic, including blindly shaping all encrypted traffic, so I'm pretty confident that the PacketSender errors are a result of this. But this is no reason to freeze the MessageCore. I'm guessing all these rejected packets are overflowing a buffer or something, and thus freezing "MessageCore"? From bqz69 at telia.com Mon Nov 3 13:58:08 2008 From: bqz69 at telia.com (bqz69) Date: Mon, 3 Nov 2008 14:58:08 +0100 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> Message-ID: <200811031458.08792.bqz69@telia.com> On Monday 03 November 2008 15.44.10 Jeff Isaac wrote: > Hello all! > I have recently stumbled across a problem with my node. I noticed that > Frost was having trouble communicating the other day even though the node > was running. Sure enough, the node (at the time 1167) was not connecting to > any peers (this after running successfully for a few weeks). I found the > warning about 1168 and upgraded manually, but this still does not help. It > took a while for the node to find 1168 nodes to connect to, and now I'm > lucky if it will connect to one or two busy ones. I am not sure what it > means, but often the one that is supposedly connected is highlighted in a > yellow bar. I suspect my ISP is attempting to block my node, but it puzzles > me that, if that be the case, it can still find anyone at all. All of my > node's communication is halted at this point. Would reinstalling with a new > node (and thus a new port) make a difference? Any help or suggestions would > be appreciated! I have almost the same problem - my freenet continues to shut down several times a day, and I have to restart and get connected to open net peers. I am using: Build #1168 r23201 and -ext Build #24 r 23199 From batosai at freenetproject.org Mon Nov 3 18:49:02 2008 From: batosai at freenetproject.org (Julien Cornuwel) Date: Mon, 03 Nov 2008 19:49:02 +0100 Subject: [freenet-support] upgrading node In-Reply-To: References: Message-ID: <490F479E.9000806@freenetproject.org> robert fallis a ?crit : > I've been away for a few weeks. and I now get a message to upgrade my node. > my node is set to automatic update but it has not worked, How do I > upgrade my node? > help please > bob Depends on your operating system : On Windows, your should have a shortcut to update.cmd. On Linux, go in freenet's directory and run './update.sh' as a normal user (not root). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://emu.freenetproject.org/pipermail/support/attachments/20081103/9d38c840/attachment.pgp From robert.fallis at virgin.net Mon Nov 3 19:07:36 2008 From: robert.fallis at virgin.net (robert fallis) Date: Mon, 03 Nov 2008 19:07:36 -0000 Subject: [freenet-support] upgrading node In-Reply-To: <490F479E.9000806@freenetproject.org> References: <490F479E.9000806@freenetproject.org> Message-ID: On Mon, 03 Nov 2008 18:49:02 -0000, Julien Cornuwel wrote: >Depends on your operating system : > On Windows, your should have a shortcut to update.cmd. > On Linux, go in freenet's directory and run './update.sh' as a normal > user (not root). > thanks, I've run ./update.sh seems a liittle slow it still hasn't loaded my boards bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From toad at amphibian.dyndns.org Mon Nov 3 20:19:23 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Mon, 3 Nov 2008 20:19:23 +0000 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> Message-ID: <200811032019.24716.toad@amphibian.dyndns.org> On Monday 03 November 2008 14:44, Jeff Isaac wrote: > Hello all! > I have recently stumbled across a problem with my node. I noticed that Frost > was having trouble communicating the other day even though the node was > running. Sure enough, the node (at the time 1167) was not connecting to any > peers (this after running successfully for a few weeks). I found the warning > about 1168 and upgraded manually, but this still does not help. It took a > while for the node to find 1168 nodes to connect to, and now I'm lucky if it > will connect to one or two busy ones. I am not sure what it means, but often > the one that is supposedly connected is highlighted in a yellow bar. I > suspect my ISP is attempting to block my node, but it puzzles me that, if > that be the case, it can still find anyone at all. All of my node's > communication is halted at this point. Would reinstalling with a new node > (and thus a new port) make a difference? Any help or suggestions would be > appreciated! > I have heard similar things on IRC. Are you the same person who reported this on IRC? Did it work with 1166? The changes since 1166 have been really minimal ... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081103/44ceba62/attachment.pgp From toad at amphibian.dyndns.org Tue Nov 4 19:12:45 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Tue, 4 Nov 2008 19:12:45 +0000 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> Message-ID: <200811041912.51722.toad@amphibian.dyndns.org> On Monday 03 November 2008 14:44, Jeff Isaac wrote: > Hello all! > I have recently stumbled across a problem with my node. I noticed that Frost > was having trouble communicating the other day even though the node was > running. Sure enough, the node (at the time 1167) was not connecting to any > peers (this after running successfully for a few weeks). I found the warning > about 1168 and upgraded manually, but this still does not help. It took a > while for the node to find 1168 nodes to connect to, and now I'm lucky if it > will connect to one or two busy ones. I am not sure what it means, but often > the one that is supposedly connected is highlighted in a yellow bar. I > suspect my ISP is attempting to block my node, but it puzzles me that, if > that be the case, it can still find anyone at all. All of my node's > communication is halted at this point. Would reinstalling with a new node > (and thus a new port) make a difference? Any help or suggestions would be > appreciated! > Hi! Could you please click on your Plugins page, and find out whether the UPnP and JSTUN plugins are installed? If they are not, please add them. And send me your wrapper.log. Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081104/0b349c74/attachment.pgp From toad at amphibian.dyndns.org Tue Nov 4 19:14:20 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Tue, 4 Nov 2008 19:14:20 +0000 Subject: [freenet-support] upgrading node In-Reply-To: References: <490F479E.9000806@freenetproject.org> Message-ID: <200811041914.22400.toad@amphibian.dyndns.org> On Monday 03 November 2008 19:07, robert fallis wrote: > On Mon, 03 Nov 2008 18:49:02 -0000, Julien Cornuwel > wrote: > > >Depends on your operating system : > > On Windows, your should have a shortcut to update.cmd. > > On Linux, go in freenet's directory and run './update.sh' as a normal > > user (not root). > > > thanks, I've run ./update.sh > seems a liittle slow it still hasn't loaded my boards Is it broken? If you click on the Strangers page, are there any peers? How many of which type? You don't have anything on the Friends page I assume? If you click on the Plugins page, which plugins are loaded? > > bob -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081104/0faefc50/attachment.pgp From dennisn at dennisn.dyndns.org Wed Nov 5 02:09:34 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Tue, 4 Nov 2008 21:09:34 -0500 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <200811031458.08792.bqz69@telia.com> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> <200811031458.08792.bqz69@telia.com> Message-ID: <20081104210934.ee92ddaf.dennisn@dennisn.dyndns.org> > On Mon, 3 Nov 2008 14:58:08 +0100, > bqz69 wrote: > > I have almost the same problem - my freenet continues to shut down > several times a day, and I have to restart and get connected to open > net peers. > > I am using: Build #1168 r23201 and -ext Build #24 r 23199 My node also crashes many times a day now, with only a simple message in wrapper.log about "JVM appears hung: Timed out waiting for signal from JVM." Does yours have this same error message? My node, however, is able to connect to peers, though my traffic is throttled by my isp, so we do have that in common. (Though yours appears to be more heavily throttled :/.) (By the way, how much memory do you give freenet (in the wrapper config file)--although I don't think that that's the problem.) From toad at amphibian.dyndns.org Wed Nov 5 22:00:52 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Wed, 5 Nov 2008 22:00:52 +0000 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <20081104210934.ee92ddaf.dennisn@dennisn.dyndns.org> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> <200811031458.08792.bqz69@telia.com> <20081104210934.ee92ddaf.dennisn@dennisn.dyndns.org> Message-ID: <200811052200.56971.toad@amphibian.dyndns.org> On Wednesday 05 November 2008 02:09, Dennis Nezic wrote: > > On Mon, 3 Nov 2008 14:58:08 +0100, > > bqz69 wrote: > > > > I have almost the same problem - my freenet continues to shut down > > several times a day, and I have to restart and get connected to open > > net peers. > > > > I am using: Build #1168 r23201 and -ext Build #24 r 23199 > > My node also crashes many times a day now, with only a simple message > in wrapper.log about "JVM appears hung: Timed out waiting for signal > from JVM." Does yours have this same error message? > > My node, however, is able to connect to peers, though my traffic is > throttled by my isp, so we do have that in common. (Though yours > appears to be more heavily throttled :/.) > > (By the way, how much memory do you give freenet (in the wrapper config > file)--although I don't think that that's the problem.) It could very well be. Lack of memory resulting in constant garbage collection could easily cause a timeout. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081105/9050bbfa/attachment.pgp From dennisn at dennisn.dyndns.org Thu Nov 6 02:43:38 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Wed, 5 Nov 2008 21:43:38 -0500 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <200811052200.56971.toad@amphibian.dyndns.org> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> <200811031458.08792.bqz69@telia.com> <20081104210934.ee92ddaf.dennisn@dennisn.dyndns.org> <200811052200.56971.toad@amphibian.dyndns.org> Message-ID: <20081105214338.74e0debd.dennisn@dennisn.dyndns.org> > On Wed, 5 Nov 2008 22:00:52 +0000, > Matthew Toseland wrote: > > It could very well be. Lack of memory resulting in constant garbage > collection could easily cause a timeout. I really don't think it's low memory. I increased wrapper.java.maxmemory to 300, and even though only about 180MB is being used (only 250MB is allocated.. ie. 50MB hasn't been touched yet), it still crashes. (Also, varying maxmemory between 180 and 300 doesn't really affect the interval between crashes.) Just to further stress the severity of the PacketSender "packet not acked" errors that I'm getting, my freenet-previous.log is 80MB! (0.1MB of which is another RequestSender "Waited too long for a blocking send for FNPSSKDataRequest", or "java.lang.Exception: error at freenet.node.Peernode.sendSync(PeerNode.java:1517)"... but the rest, 79.9MB are *only* this one PacketSender ERROR). Also, just to further stress the severity of the crashes :) :|, here is a graph from today, each peak is a restart. (Ignore the rest of the data.) http://dennisn.dyndns.org/guest/pubstuff/freenet-jvm-crashes.png From toad at amphibian.dyndns.org Thu Nov 6 14:02:40 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Thu, 6 Nov 2008 14:02:40 +0000 Subject: [freenet-support] Freenet 0.7 build 1169 Message-ID: <200811061402.45221.toad@amphibian.dyndns.org> Freenet 0.7 build 1169 is now available. Please update. No massive changes, but some important bugfixes which hopefully will fix some of the connectivity problems that have been reported recently: - Fix announcing to the same node more than once, disconnecting, wasting lots of announcements. (Thanks sdiz) - Don't do DNS lookups constantly on the packet sender thread, this caused havoc with a node with a nonexistent DNS address. - Logging to try to track down problems with updating. - Make announcements slightly more tolerant of lag. - Make the salted-hash datastore the default for new nodes (but not for old nodes). The salted-hash datastore, written by sdiz, is a massive improvement in most respects on the old bdbje datastore. It features random replacement (which has shown in simulations to slightly improve network performance), uses much less CPU, is much more robust, and uses less in-JVM memory. However, by default it uses a Bloom filter to minimise disk I/O and improve performance; this uses 1/2048th of the size of the store, memory mapped to a disk file; it doesn't count towards the JVM memory limit. You can turn this off if seeking is not a problem (e.g. on a flash disk). Note that the salted-hash is only default for nodes that don't already have a datastore type: old nodes will not be automatically converted, since conversion takes a huge amount of disk space. This is another build with minimal changes - trunk has a number of major changes, but is not yet ready to release, so this build is based on 1166/1167/1168 rather than on the current trunk code. Please report any bugs you find! Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081106/fb1a8325/attachment.pgp From toad at amphibian.dyndns.org Thu Nov 6 14:29:42 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Thu, 6 Nov 2008 14:29:42 +0000 Subject: [freenet-support] Node won't connect to peers 1167/68 In-Reply-To: <20081105214338.74e0debd.dennisn@dennisn.dyndns.org> References: <2da599600811030644g30e80d50laed94b3a0a041c78@mail.gmail.com> <200811052200.56971.toad@amphibian.dyndns.org> <20081105214338.74e0debd.dennisn@dennisn.dyndns.org> Message-ID: <200811061429.42873.toad@amphibian.dyndns.org> Okay, the PacketSender resent-and-not-acked problem is probably caused by a bug fixed in 1169. Unfortunately we will have to wait for most of the network to update before this will make a big impact. On Thursday 06 November 2008 02:43, Dennis Nezic wrote: > > On Wed, 5 Nov 2008 22:00:52 +0000, > > Matthew Toseland wrote: > > > > It could very well be. Lack of memory resulting in constant garbage > > collection could easily cause a timeout. > > I really don't think it's low memory. I increased > wrapper.java.maxmemory to 300, and even though only about 180MB is > being used (only 250MB is allocated.. ie. 50MB hasn't been touched > yet), it still crashes. (Also, varying maxmemory between 180 and 300 > doesn't really affect the interval between crashes.) > > Just to further stress the severity of the PacketSender "packet > not acked" errors that I'm getting, my freenet-previous.log is 80MB! > (0.1MB of which is another RequestSender "Waited too long for a > blocking send for FNPSSKDataRequest", or "java.lang.Exception: error at > freenet.node.Peernode.sendSync(PeerNode.java:1517)"... but the rest, > 79.9MB are *only* this one PacketSender ERROR). > > Also, just to further stress the severity of the crashes :) :|, here is > a graph from today, each peak is a restart. (Ignore the rest of the > data.) > > http://dennisn.dyndns.org/guest/pubstuff/freenet-jvm-crashes.png > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081106/4fcfbf4a/attachment.pgp From toad at amphibian.dyndns.org Thu Nov 6 14:30:10 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Thu, 6 Nov 2008 14:30:10 +0000 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <200811061402.45221.toad@amphibian.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> Message-ID: <200811061430.11040.toad@amphibian.dyndns.org> Please forward the below to FMS. Also, if update doesn't work, please run update.sh / update.cmd manually. Thanks. On Thursday 06 November 2008 14:02, Matthew Toseland wrote: > Freenet 0.7 build 1169 is now available. Please update. No massive changes, > but some important bugfixes which hopefully will fix some of the connectivity > problems that have been reported recently: > - Fix announcing to the same node more than once, disconnecting, wasting lots > of announcements. (Thanks sdiz) > - Don't do DNS lookups constantly on the packet sender thread, this caused > havoc with a node with a nonexistent DNS address. > - Logging to try to track down problems with updating. > - Make announcements slightly more tolerant of lag. > - Make the salted-hash datastore the default for new nodes (but not for old > nodes). The salted-hash datastore, written by sdiz, is a massive improvement > in most respects on the old bdbje datastore. It features random replacement > (which has shown in simulations to slightly improve network performance), > uses much less CPU, is much more robust, and uses less in-JVM memory. > However, by default it uses a Bloom filter to minimise disk I/O and improve > performance; this uses 1/2048th of the size of the store, memory mapped to a > disk file; it doesn't count towards the JVM memory limit. You can turn this > off if seeking is not a problem (e.g. on a flash disk). Note that the > salted-hash is only default for nodes that don't already have a datastore > type: old nodes will not be automatically converted, since conversion takes a > huge amount of disk space. > > This is another build with minimal changes - trunk has a number of major > changes, but is not yet ready to release, so this build is based on > 1166/1167/1168 rather than on the current trunk code. > > Please report any bugs you find! Thanks. > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081106/e087cc8c/attachment.pgp From dennisn at dennisn.dyndns.org Thu Nov 6 19:42:35 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Thu, 6 Nov 2008 14:42:35 -0500 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <200811061402.45221.toad@amphibian.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> Message-ID: <20081106144235.456e89b3.dennisn@dennisn.dyndns.org> > On Thu, 6 Nov 2008 14:02:40 +0000, > Matthew Toseland wrote: > > Freenet 0.7 build 1169 is now available. Please update. No massive > changes, but some important bugfixes which hopefully will fix some of > the connectivity problems that have been reported recently: I'm having a LOT of trouble with 1169 (r23352)--the "JVM appears hung" way more often. Actually, although I was able to get it started** the first couple of times, I can't now. It hangs a few minutes after the FEC library is loaded--sometimes at the beginning of a PUBKEY or SSK or CHK-store cleaner, constantly using 100% cpu since being launched. I'm running an Athlon 1.2G, with 384MB ram, and a locally compiled build. Once it outputted a thread dump, though it rarely does this. The one time it did, I had the wrapper max logfile size to 2MB, and the dump filled it with lots of messages like: "java.lang.Thread.State: TIMED_WAITING (parking)" The last few lines were: "VM Thread" prio=10 tid=0x08080000 nid=0x145a runnable "VM Periodic Task Thread" prio=10 tid=0x08092000 nid=0x1460 waiting on condition JNI global references: 996 Heap def new generation total 14976K, used 12919K eden space 13312K, 84% used from space 1664K, 99% used to space 1664K, 0% used tenured generation total 198996K, used 147211K the space 198996K, 73% used compacting perm gen total 12288K, used 5663K the space 12288K, 46% used ro space 8192K, 74% used rw space 12288K, 58% used I also remember once while trying to start up, it outputted an error about not being able to open a file (I think it was trying to open libfec) because there were too many files already opened :|. But that only happened once. So yeah, I can't get freenet to start now at all. JVM hangs a few minutes after FEC lib is loaded. ** Also, when I first ran 1169, it forced me to go through the wizard again, and afterwards, although it seemed to remember most of my past settings (node name, logger settings, etc), it didn't remember my datastore size (which i converted to salted hash a few days ago). From dennisn at dennisn.dyndns.org Thu Nov 6 20:13:11 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Thu, 6 Nov 2008 15:13:11 -0500 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <20081106144235.456e89b3.dennisn@dennisn.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106144235.456e89b3.dennisn@dennisn.dyndns.org> Message-ID: <20081106151311.3fc6caac.dennisn@dennisn.dyndns.org> > On Thu, 6 Nov 2008 14:42:35 -0500, > Dennis Nezic wrote: > > ....., constantly using 100% cpu since being launched. I should also add that my load averages (uptime) were at 80. I've never seen them that high before. From vdenisov at redline.ru Fri Nov 7 00:03:24 2008 From: vdenisov at redline.ru (Victor Denisov) Date: Fri, 07 Nov 2008 03:03:24 +0300 Subject: [freenet-support] Node can't find native BigInteger library Message-ID: <491385CC.5000805@redline.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just noticed that, for some reason, my node doesn't pick up native BigInteger library: ... Initializing Node using Freenet Build #1169 r23350M and freenet-ext Build #24 r23199 with Sun Microsystems Inc. JVM version 1.6.0_06 running on amd64 Windows 2003 5.2 ... NOTICE: Resource name [net/i2p/util/jbigi-windows-x86_64.dll] was not found Library net/i2p/util/jbigi-windows-none.dll is not appropriate for this system. INFO: Native BigInteger library jbigi not loaded - using pure java ... Anything I can do to get the node to load a native library? On a related topic, Windows x86-64 native binary for Onion FEC isn't present as well. Are there plans to include it in the foreseeable future? Regards, Victor Denisov. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJE4XM1O5++4rTuI0RArMFAKCCUZ6LotMJ2Akz3Gpg3jZc1qhUDQCgnMlf ZJWBolsNbsl9afK5ICcD4yE= =MYhB -----END PGP SIGNATURE----- From toad at amphibian.dyndns.org Fri Nov 7 00:14:23 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 7 Nov 2008 00:14:23 +0000 Subject: [freenet-support] Node can't find native BigInteger library In-Reply-To: <491385CC.5000805@redline.ru> References: <491385CC.5000805@redline.ru> Message-ID: <200811070014.42732.toad@amphibian.dyndns.org> On Friday 07 November 2008 00:03, Victor Denisov wrote: > Just noticed that, for some reason, my node doesn't pick up native > BigInteger library: > > ... > > Initializing Node using Freenet Build #1169 r23350M and freenet-ext > Build #24 r23199 with Sun Microsystems Inc. JVM version 1.6.0_06 running > on amd64 Windows 2003 5.2 > > ... > > NOTICE: Resource name [net/i2p/util/jbigi-windows-x86_64.dll] was not found > Library net/i2p/util/jbigi-windows-none.dll is not appropriate for this > system. > INFO: Native BigInteger library jbigi not loaded - using pure java > > ... > > Anything I can do to get the node to load a native library? Dunno. We do have them for linux. > > On a related topic, Windows x86-64 native binary for Onion FEC isn't > present as well. Are there plans to include it in the foreseeable future? That's a bigger problem, the code isn't 64-bit clean. Nextgens tried to port it but didn't succeed. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081107/8a74e33a/attachment.pgp From dennisn at dennisn.dyndns.org Fri Nov 7 02:28:38 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Thu, 6 Nov 2008 21:28:38 -0500 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <20081106151311.3fc6caac.dennisn@dennisn.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106144235.456e89b3.dennisn@dennisn.dyndns.org> <20081106151311.3fc6caac.dennisn@dennisn.dyndns.org> Message-ID: <20081106212838.d0d9c166.dennisn@dennisn.dyndns.org> > On Thu, 6 Nov 2008 15:13:11 -0500, > Dennis Nezic wrote: > > I should also add that my load averages (uptime) were at 80. I've > never seen them that high before. Update: I tried it again, except this time I accidentally forgot to give it a seednodes.fref. The first attempt, the same thing happened: after node initialization was completed, after it found update edition 1169, and about three minutes after "Loading FEC lib", the JVM hung. BUT, the wrapper's second attempt immediately afterwards went further! It completed all the 6 cleaners (CHK-cache, CHK-store, SSK-cache, etc), but since there were no seednodes, it didn't connect to anything. BUT it was still consuming all the cpu!--supposedly not doing anything!? At this point I turned the logger back on, and to my horror, it immediately filled to over 70MB, 69.9 of which were errors of the form: (freenet.client.async.SingleBlockInserter, Insert thread for freenet.client.async.SingleFileInserter at 1f4e571(1545), ERROR): Caught java.io.IOException: File already freed encoding data freenet.support.io.TempBucketFactory$TempBucket at 16debe8 java.io.IOException: File already freed at freenet.support.io.BaseFileBucket.getInputStream(BaseFileBucket.java:251) at freenet.support.io.PaddedEphemerallyEncryptedBucket.getInputStream(PaddedEphemerallyEncryptedBucket.java:210) at freenet.support.io.TempBucketFactory$TempBucket$TempBucketInputStream.(TempBucketFactory.java:236) at freenet.support.io.TempBucketFactory$TempBucket.getInputStream(TempBucketFactory.java:220) at freenet.support.io.BucketTools.toByteArray(BucketTools.java:197) at freenet.keys.Key.compress(Key.java:233) at freenet.keys.ClientCHKBlock.encode(ClientCHKBlock.java:141) at freenet.client.async.SingleBlockInserter.innerEncode(SingleBlockInserter.java:83) at freenet.client.async.SingleBlockInserter.encode(SingleBlockInserter.java:117) at freenet.client.async.SingleBlockInserter.getBlock(SingleBlockInserter.java:209) at freenet.client.async.SingleBlockInserter.getURI(SingleBlockInserter.java:249) at freenet.client.async.SingleFileInserter.insert(SingleFileInserter.java:247) at freenet.client.async.SingleFileInserter.access$000(SingleFileInserter.java:37) at freenet.client.async.SingleFileInserter$1.run(SingleFileInserter.java:207) at freenet.support.PooledExecutor$MyThread.run(PooledExecutor.java:190) I wasn't even able to shut the node down at this point... the JVM first. From dennisn at dennisn.dyndns.org Fri Nov 7 02:49:04 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Thu, 6 Nov 2008 21:49:04 -0500 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <20081106212838.d0d9c166.dennisn@dennisn.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106144235.456e89b3.dennisn@dennisn.dyndns.org> <20081106151311.3fc6caac.dennisn@dennisn.dyndns.org> <20081106212838.d0d9c166.dennisn@dennisn.dyndns.org> Message-ID: <20081106214904.c6e5a8ce.dennisn@dennisn.dyndns.org> > On Thu, 6 Nov 2008 21:28:38 -0500, > Dennis Nezic wrote: > > .......... BUT it was still consuming all the cpu!--supposedly not > doing anything!? At this point I turned the logger back on, and to my > horror, it immediately filled to over 70MB, 69.9 of which were errors > of the form: > > (freenet.client.async.SingleBlockInserter, > Insert thread for freenet.client.async.SingleFileInserter at 1f4e571 > (1545), ERROR): Caught java.io.IOException: > File already freed encoding data > freenet.support.io.TempBucketFactory$TempBucket at 16debe8 > java.io.IOException: File already freed at > freenet.support.io.BaseFileBucket.getInputStream > (BaseFileBucket.java:251) at If I start with a fresh datastore (if I move my old datastore directory somewhere else), I get a slightly different bunch of error messages, though not nearly as many as before, and all mostly of this type: (freenet.client.async.ClientPutter, Insert thread for freenet.client.async.SingleFileInserter at eaf40c(348), ERROR): addBlock() but set finalized! on freenet.client.async.ClientPutter at 1d87b85 (freenet.client.async.ClientPutter, Insert thread for freenet.client.async.SingleFileInserter at eaf40c(348), ERROR): onTransition: cur=freenet.client.async.MultiPutCompletionCallback at 1de45e2, old=freenet.client.async.SingleFileInserter at eaf40c, new=freenet.client.async.MultiPutCompletionCallback at 122c9df They would usually (not always) occur together, or 1ms apart. There would also somtimes occur a row of: (freenet.client.async.ClientPutter, Pooled thread awaiting work @70, ERROR): addBlock() but set finalized! on freenet.client.async.ClientPutter at 1d87b85 And I was able to easily shut down the node in this case :|. (No JVM hangs :\.) From dennisn at dennisn.dyndns.org Fri Nov 7 03:18:14 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Thu, 6 Nov 2008 22:18:14 -0500 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <20081106214904.c6e5a8ce.dennisn@dennisn.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106144235.456e89b3.dennisn@dennisn.dyndns.org> <20081106151311.3fc6caac.dennisn@dennisn.dyndns.org> <20081106212838.d0d9c166.dennisn@dennisn.dyndns.org> <20081106214904.c6e5a8ce.dennisn@dennisn.dyndns.org> Message-ID: <20081106221814.704d67e1.dennisn@dennisn.dyndns.org> Hrm.. sorry.. it seems to be working now that I'm using r23350. I was having all my problems with r23352--which I could have sworn was referenced in freenet-stable-latest.jar.url this morning :|. Anywho, sorry for the noise. From toad at amphibian.dyndns.org Fri Nov 7 17:00:46 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 7 Nov 2008 17:00:46 +0000 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <20081106212838.d0d9c166.dennisn@dennisn.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106151311.3fc6caac.dennisn@dennisn.dyndns.org> <20081106212838.d0d9c166.dennisn@dennisn.dyndns.org> Message-ID: <200811071700.47266.toad@amphibian.dyndns.org> Do you have any inserts queued? On Friday 07 November 2008 02:28, Dennis Nezic wrote: > > On Thu, 6 Nov 2008 15:13:11 -0500, > > Dennis Nezic wrote: > > > > I should also add that my load averages (uptime) were at 80. I've > > never seen them that high before. > > Update: I tried it again, except this time I accidentally forgot to > give it a seednodes.fref. The first attempt, the same thing happened: > after node initialization was completed, after it found update edition > 1169, and about three minutes after "Loading FEC lib", the JVM hung. > > BUT, the wrapper's second attempt immediately afterwards went further! > It completed all the 6 cleaners (CHK-cache, CHK-store, SSK-cache, etc), > but since there were no seednodes, it didn't connect to anything. BUT > it was still consuming all the cpu!--supposedly not doing anything!? At > this point I turned the logger back on, and to my horror, it immediately > filled to over 70MB, 69.9 of which were errors of the form: > > (freenet.client.async.SingleBlockInserter, > Insert thread for freenet.client.async.SingleFileInserter at 1f4e571(1545), ERROR): > Caught java.io.IOException: > File already freed encoding data freenet.support.io.TempBucketFactory$TempBucket at 16debe8 > java.io.IOException: File already freed > at freenet.support.io.BaseFileBucket.getInputStream(BaseFileBucket.java:251) > at freenet.support.io.PaddedEphemerallyEncryptedBucket.getInputStream(PaddedEphemerallyEncryptedBucket.java:210) > at freenet.support.io.TempBucketFactory$TempBucket$TempBucketInputStream.(TempBucketFactory.java:236) > at freenet.support.io.TempBucketFactory$TempBucket.getInputStream(TempBucketFactory.java:220) > at freenet.support.io.BucketTools.toByteArray(BucketTools.java:197) > at freenet.keys.Key.compress(Key.java:233) > at freenet.keys.ClientCHKBlock.encode(ClientCHKBlock.java:141) > at freenet.client.async.SingleBlockInserter.innerEncode(SingleBlockInserter.java:83) > at freenet.client.async.SingleBlockInserter.encode(SingleBlockInserter.java:117) > at freenet.client.async.SingleBlockInserter.getBlock(SingleBlockInserter.java:209) > at freenet.client.async.SingleBlockInserter.getURI(SingleBlockInserter.java:249) > at freenet.client.async.SingleFileInserter.insert(SingleFileInserter.java:247) > at freenet.client.async.SingleFileInserter.access$000 (SingleFileInserter.java:37) > at freenet.client.async.SingleFileInserter$1.run(SingleFileInserter.java:207) > at freenet.support.PooledExecutor$MyThread.run(PooledExecutor.java:190) > > I wasn't even able to shut the node down at this point... the JVM first. > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081107/92f63a1e/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 7 17:02:55 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 7 Nov 2008 17:02:55 +0000 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <20081106221814.704d67e1.dennisn@dennisn.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106214904.c6e5a8ce.dennisn@dennisn.dyndns.org> <20081106221814.704d67e1.dennisn@dennisn.dyndns.org> Message-ID: <200811071702.56163.toad@amphibian.dyndns.org> Would you mind trying a recent testing build? update.sh testing / update.cmd testing ? The bugs in trunk have been largely fixed... On Friday 07 November 2008 03:18, Dennis Nezic wrote: > Hrm.. sorry.. it seems to be working now that I'm using r23350. > > I was having all my problems with r23352--which I could have sworn was > referenced in freenet-stable-latest.jar.url this morning :|. > > Anywho, sorry for the noise. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081107/e87dac8d/attachment.pgp From dennisn at dennisn.dyndns.org Sat Nov 8 14:38:04 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Sat, 8 Nov 2008 09:38:04 -0500 Subject: [freenet-support] Freenet 0.7 build 1169 In-Reply-To: <200811071702.56163.toad@amphibian.dyndns.org> References: <200811061402.45221.toad@amphibian.dyndns.org> <20081106214904.c6e5a8ce.dennisn@dennisn.dyndns.org> <20081106221814.704d67e1.dennisn@dennisn.dyndns.org> <200811071702.56163.toad@amphibian.dyndns.org> Message-ID: <20081108093804.dddeeac7.dennisn@dennisn.dyndns.org> > On Fri, 7 Nov 2008 17:02:55 +0000, > Matthew Toseland wrote: > > Would you mind trying a recent testing build? update.sh testing / > update.cmd testing ? The bugs in trunk have been largely fixed... Yes--things seem to be running a lot better as of r23371--the jvm hasn't hung yet after almost a day of uptime. From toad at amphibian.dyndns.org Sat Nov 8 15:15:05 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Sat, 8 Nov 2008 15:15:05 +0000 Subject: [freenet-support] Freenet 0.7 build 1170 Message-ID: <200811081515.13265.toad@amphibian.dyndns.org> Freenet 0.7 build 1170 is now available, please upgrade! There are many changes, built over the time since 1166 - the last 3 builds have been critical bugfixes only. The most important changes: - New compression formats: Files are compressed with gzip, bzip2 or lzma, whichever gives best compression. This should give a significant saving for many files, and the increased compression time is likely offset by the reduced insertion time. - New container format: Freesites are packed into tar files, rather than zip files. These tar files are then compressed as above. For HTML, plain text etc, if it fits into the container, we should expect a substantial gain (50% seems plausible) in the number of blocks needed to insert a site, and therefore how long it takes to fetch it; please reinsert your freesites. - Make sure the user goes through the first-time wizard - if they haven't, open it on connecting to fproxy. The purpose here is to avoid problems with newbies with unconfigured nodes because of various failures. If you have your settings exactly as you want them, please click on "I am not a newbie". - A new blue theme by Dieppe, and some minor fixes to the web interface. - Warn the user if their IP address is not detected and there are no IP detection plugins loaded. Also some minor fixes to IP detection. - Don't drop a plugin just because it didn't load this time, try it again on next startup unless the user tells us not to. Minor changes to plugin loading. - Fix a bug causing us to leak file handles (fd's). - Lots of bug fixes and internal refactoring. - And the usual translation updates. There has also been lots of work on the installer, the web site, the firefox profile, the UPnP plugin (which you should reload if you use it), the db4o branch, the Web of Trust and Freetalk (formerly FMS) plugins (which p0s has been working hard on for some time and will be ready for initial testing very soon), and jSite 0.6.2 is out (bombe). Credits (for the node/website/profile/UPnP): bombe dieppe j16sdiz luke771 nextgens smar toad tommy xor yongjhen Please let me know if you have any difficulty with the auto-update mechanism, and please report any bugs you find to the bug tracker: https://bugs.freenetproject.org/ Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081108/08116be5/attachment.pgp From toad at amphibian.dyndns.org Sat Nov 8 17:51:26 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Sat, 8 Nov 2008 17:51:26 +0000 Subject: [freenet-support] Urgent: Do not run the wizard on 1170! Message-ID: <200811081751.36435.toad@amphibian.dyndns.org> 1170 will ask you to go through the wizard again. This is on the theory that most of our users are oldtimers and may not have set the security levels. DO NOT GO THROUGH THE WIZARD if your node is running 1170. Click on "I will configure the node manually". If you do go through the wizard, it will reset your datastore size and bandwidth limits to the defaults. :< On 1171, it will ask you what you want to set these settings to, with the default being the current value - but if your node updates to 1170 it may take a considerable time to update to 1171, so you may be running 1170 ... Sorry! (Yes it hurts me more than it hurts you...) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081108/238041d2/attachment.pgp From toad at amphibian.dyndns.org Sun Nov 9 00:22:11 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Sun, 9 Nov 2008 00:22:11 +0000 Subject: [freenet-support] Freenet 0.7 build 1173, 1172 and 1171 Message-ID: <200811090022.21016.toad@amphibian.dyndns.org> Freenet 0.7 build 1173 is now available. This build is self-mandatory i.e. it only talks to nodes running at least 1173. Freenet should be able to upgrade itself automatically using "Update over Mandatory", pulling the data from nodes that are "TOO NEW". If it doesn't, please upgrade manually using update.sh / update.cmd. We have had a node running build 1151 upgrade itself successfully via Update over Mandatory; but builds prior to 1173 had some serious bugs that would prevent a successful update until it was mandatory. So we made it mandatory immediately, so all nodes would update. This may cause some temporary network disruption, sorry folks... Also if you are running a node prior to 1165, upgrading to 1170 or later will automatically migrate your datastore to salted-hash. This is not intended, but we only started writing the store type to disk in 1165 (6 weeks ago). I apologise for the self-mandatory build, and for the 4 builds in a day. It was necessary because of a series of rather serious bugs. Most serious were the updating bugs fixed in 1173: 1171: - In1170, all users were forced to go through the first-time wizard again (or click on the I-am-not-a-newbie option). Partly this is to ensure that nodes get configured even if the user installs and then forgets about it, and comes back and finds it doesn't work. But this also affects existing nodes. The idea behind this was that most nodes on the network are probably old-timers who may not have set trust levels. Unfortunately, the wizard overwrites your bandwidth limits and datastore size, without telling you if it manages to autodetect them! In 1171, we ensure that if you use the wizard after having configured your node, it always shows the bandwidth and datastore selection pages, and defaults them to your current settings. 1172: - Don't force all users to go through the wizard. Only redirect to the wizard if it hasn't been visited before, AND the node has no peers and/or has opennet disabled. Hence it will be shown on a new node install that the user has forgotten about (which was the real concern), but not on most nodes. - Fix Update over Mandatory triggering instantly on seeing a new build on nodes that have been online for more than 3 hours. Unfortunately, fixing this greatly exacerbated the other updating bugs - the node would not update at all until a build was mandatory. - Fix a bug causing very small freesite and file inserts to be decompressed more than once and therefore fail. - Faster and simpler LZMA decompression (came up while debugging the above issue, greatly reduces the number of lines, simple copy/paste from third party code; low risk). 1173: - Major bugfix to Update over Mandatory (it was only working when the build was mandatory, and not falling back to it if Update over Freenet failed, which it was doing because of the next bug). - Major bugfix to Update over Freenet (the "normal" updating process, which is much less disruptive to the network than UOM). -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081109/9431fde6/attachment.pgp From dennisn at dennisn.dyndns.org Sun Nov 9 03:09:42 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Sat, 8 Nov 2008 22:09:42 -0500 Subject: [freenet-support] Freenet 0.7 build 1173, 1172 and 1171 In-Reply-To: <200811090022.21016.toad@amphibian.dyndns.org> References: <200811090022.21016.toad@amphibian.dyndns.org> Message-ID: <20081108220942.f17f6762.dennisn@dennisn.dyndns.org> > On Sun, 9 Nov 2008 00:22:11 +0000, > Matthew Toseland wrote: > > Freenet 0.7 build 1173 is now available. It is still using much more of (my 1.2GHz) cpu than I would like. It regularly hovers at 100% for a few minutes, then calms down, then repeats. And, probably not unrelated, it is still producing LOTS of PacketSender ERRORs in the freenet logfiles. (I am forced to disable logging, otherwise it could /easily/ grow out of control.) For example, just now I enabled logging for /less/ than 2 minutes, and it grew to over 2MB, *ENTIRELY* composed of freenet.node.KeyTracker, PacketSender thread, Packet bla sent over blams ago still not acked ERRORs. It has been brought up on IRC a number of times today, most notably by mkan--but I forget if a reason/solution was given. It may not be isp throttling as I originally guessed, since mkan lives in a different part of the world, and is experiencing the same thing--as I think many others are as well. In this last 2min test of mine, all of the errors came from my 1173 opennet peers. Only one of them was listed as "BACKED OFF" (I was/am connected to him for 4h49m)--the other two were (and still are) "CONNECTED" (for 48m and 1h21m). They have varying overload probability percentages, 14% 16% 42% respectively. They have varying congestion control rates, 1MB/s 1MB/s 17Bytes/s respectively. They have varying RTT times, 263ms 138233ms 71006ms. They have varying overloaded percentages, the "backed off" one was "99.8% 7974/10800/AcceptedTimeout" but the other two were 3% and 28%, both with 0/1/ForwardRejectedOverload. From dennisn at dennisn.dyndns.org Sun Nov 9 03:14:38 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Sat, 8 Nov 2008 22:14:38 -0500 Subject: [freenet-support] Freenet 0.7 build 1173, 1172 and 1171 In-Reply-To: <20081108220942.f17f6762.dennisn@dennisn.dyndns.org> References: <200811090022.21016.toad@amphibian.dyndns.org> <20081108220942.f17f6762.dennisn@dennisn.dyndns.org> Message-ID: <20081108221438.ac44a300.dennisn@dennisn.dyndns.org> > On Sat, 8 Nov 2008 22:09:42 -0500, > Dennis Nezic wrote: > > In this last 2min test of mine, all of the errors came from my 1173 > opennet peers. Only one of them was listed as "BACKED OFF" (I > was/am connected to him for 4h49m)--the other two were (and still are) > "CONNECTED" (for 48m and 1h21m). They have varying overload > probability percentages, 14% 16% 42% respectively. They have varying > congestion control rates, 1MB/s 1MB/s 17Bytes/s respectively. They > have varying RTT times, 263ms 138233ms 71006ms. They have varying > overloaded percentages, the "backed off" one was "99.8% > 7974/10800/AcceptedTimeout" but the other two were 3% and 28%, both > with 0/1/ForwardRejectedOverload. With just one of those opennet peers, who is still "CONNECTED", In those 2min I got about 5000 of these ERROR messages!... many times just under 200/s. 40% of my traffic with this peer is having to be resent. (according to the strangers stats page.) From freenetwork at web.de Sun Nov 9 11:07:40 2008 From: freenetwork at web.de (freenetwork at web.de) Date: Sun, 09 Nov 2008 12:07:40 +0100 Subject: [freenet-support] #1173: Internal error: Found interface freenet.support.compress.Compressor, but class was expected Message-ID: <4916C47C.5070100@web.de> Hi list, after updating to lastest mandatory build #1173 revision r23439 all my downloads are failing with "Internal error: Found interface freenet.support.compress.Compressor, but class was expected" as error message. The downloads have been started and taken over from a previous build. Now what? From bbackde at googlemail.com Sun Nov 9 15:25:38 2008 From: bbackde at googlemail.com (bbackde at googlemail.com) Date: Sun, 9 Nov 2008 16:25:38 +0100 Subject: [freenet-support] Convert to salted hash store NOW? Message-ID: I wonder if I should convert to the salted hash store now. Is it really stable? Or should I wait until more new nodes used it for some time before I convert my 'rocking-stable' old store to the new one? I mean, over the time I saw some bugs that were found sometimes later, and I don't know if the new store is used on some testing nodes for a long time now without problems... Thanks for considering to provide me a reasonable answer. bback -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________ From dennisn at dennisn.dyndns.org Sun Nov 9 16:49:16 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Sun, 9 Nov 2008 11:49:16 -0500 Subject: [freenet-support] #1173: Internal error: Found interface freenet.support.compress.Compressor, but class was expected In-Reply-To: <4916C47C.5070100@web.de> References: <4916C47C.5070100@web.de> Message-ID: <20081109114916.1b070159.dennisn@dennisn.dyndns.org> > On Sun, 09 Nov 2008 12:07:40 +0100, > "freenetwork at web.de" wrote: > > Hi list, > > after updating to lastest mandatory build #1173 revision r23439 all my > downloads are failing with "Internal error: Found interface > freenet.support.compress.Compressor, but class was expected" as error > message. The downloads have been started and taken over from a > previous build. Strange--all my downloads do seem to have recovered throughout all these past updates. Though, I believe my downloads are fairly recent (a week or so old) inserts--not sure if that matters. Did you try restarting any of them? New compression procedures were introduced around 1170, so maybe that is affecting it. From freenetwork at web.de Sun Nov 9 20:07:51 2008 From: freenetwork at web.de (freenetwork at web.de) Date: Sun, 09 Nov 2008 21:07:51 +0100 Subject: [freenet-support] #1173: Internal error: Found interface freenet.support.compress.Compressor, but class was expected In-Reply-To: <20081109114916.1b070159.dennisn@dennisn.dyndns.org> References: <4916C47C.5070100@web.de> <20081109114916.1b070159.dennisn@dennisn.dyndns.org> Message-ID: <49174317.3070704@web.de> Dennis Nezic wrote: >> On Sun, 09 Nov 2008 12:07:40 +0100, >> "freenetwork at web.de" wrote: >> >> Hi list, >> >> after updating to lastest mandatory build #1173 revision r23439 all my >> downloads are failing with "Internal error: Found interface >> freenet.support.compress.Compressor, but class was expected" as error >> message. The downloads have been started and taken over from a >> previous build. >> > > Strange--all my downloads do seem to have recovered throughout all > these past updates. Though, I believe my downloads are fairly recent (a > week or so old) inserts--not sure if that matters. > > Did you try restarting any of them? New compression procedures were > introduced around 1170, so maybe that is affecting it. Restarting them resulted in the downloads going back to "Internal error: ..." within seconds. I tried several times with several node restarts... From ebaschiera at gmail.com Sun Nov 9 21:30:17 2008 From: ebaschiera at gmail.com (Ermanno Baschiera) Date: Sun, 9 Nov 2008 22:30:17 +0100 Subject: [freenet-support] Convert to salted hash store NOW? In-Reply-To: References: Message-ID: I switched 3 days ago. The conversion took more than 48h for my 30 GB datastore on a Via C7 1.2GHz and a SATA hd. It went fine, except for the datastore that has been somehow shrinked to 24 GB (6 GB went lost?). I haven't yet tested cpu or i/o usage. This is just my experience. I hope someone has been more lucky than me. :-) -ermanno 2008/11/9 : > I wonder if I should convert to the salted hash store now. > Is it really stable? Or should I wait until more new nodes used it for some time > before I convert my 'rocking-stable' old store to the new one? > I mean, over the time I saw some bugs that were found sometimes later, > and I don't > know if the new store is used on some testing nodes for a long time > now without problems... > > Thanks for considering to provide me a reasonable answer. > > bback > > -- > __________________________________________________ > GnuPG key: (0x48DBFA8A) > Keyserver: pgpkeys.pca.dfn.de > Fingerprint: > 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A > __________________________________________________ > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > From toad at amphibian.dyndns.org Mon Nov 10 15:11:48 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Mon, 10 Nov 2008 15:11:48 +0000 Subject: [freenet-support] #1173: Internal error: Found interface freenet.support.compress.Compressor, but class was expected In-Reply-To: <49174317.3070704@web.de> References: <4916C47C.5070100@web.de> <20081109114916.1b070159.dennisn@dennisn.dyndns.org> <49174317.3070704@web.de> Message-ID: <200811101512.04579.toad@amphibian.dyndns.org> On Sunday 09 November 2008 20:07, freenetwork at web.de wrote: > > Dennis Nezic wrote: > >> On Sun, 09 Nov 2008 12:07:40 +0100, > >> "freenetwork at web.de" wrote: > >> > >> Hi list, > >> > >> after updating to lastest mandatory build #1173 revision r23439 all my > >> downloads are failing with "Internal error: Found interface > >> freenet.support.compress.Compressor, but class was expected" as error > >> message. The downloads have been started and taken over from a > >> previous build. > >> > > > > Strange--all my downloads do seem to have recovered throughout all > > these past updates. Though, I believe my downloads are fairly recent (a > > week or so old) inserts--not sure if that matters. > > > > Did you try restarting any of them? New compression procedures were > > introduced around 1170, so maybe that is affecting it. > Restarting them resulted in the downloads going back to "Internal error: > ..." within seconds. I tried several times with several node restarts... What if you delete them and then re-add them (for the same URIs)? Downloads do seem to work here and that sort of error would normally indicate a compile problem ... which afaics is impossible here... Can you please search your logs/freenet-latest.log for any related ERROR with a stack trace? Search for "Found interface", send me the lines surrounding it. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081110/2f2e374f/attachment.pgp From toad at amphibian.dyndns.org Mon Nov 10 15:15:52 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Mon, 10 Nov 2008 15:15:52 +0000 Subject: [freenet-support] #1173: Internal error: Found interface freenet.support.compress.Compressor, but class was expected In-Reply-To: <49174317.3070704@web.de> References: <4916C47C.5070100@web.de> <20081109114916.1b070159.dennisn@dennisn.dyndns.org> <49174317.3070704@web.de> Message-ID: <200811101515.54001.toad@amphibian.dyndns.org> Another question: How did you update? Through update.sh/update.cmd, or through the node auto-update? Thanks. On Sunday 09 November 2008 20:07, freenetwork at web.de wrote: > > Dennis Nezic wrote: > >> On Sun, 09 Nov 2008 12:07:40 +0100, > >> "freenetwork at web.de" wrote: > >> > >> Hi list, > >> > >> after updating to lastest mandatory build #1173 revision r23439 all my > >> downloads are failing with "Internal error: Found interface > >> freenet.support.compress.Compressor, but class was expected" as error > >> message. The downloads have been started and taken over from a > >> previous build. > >> > > > > Strange--all my downloads do seem to have recovered throughout all > > these past updates. Though, I believe my downloads are fairly recent (a > > week or so old) inserts--not sure if that matters. > > > > Did you try restarting any of them? New compression procedures were > > introduced around 1170, so maybe that is affecting it. > Restarting them resulted in the downloads going back to "Internal error: > ..." within seconds. I tried several times with several node restarts... > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081110/a66aa831/attachment.pgp From toad at amphibian.dyndns.org Mon Nov 10 15:24:09 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Mon, 10 Nov 2008 15:24:09 +0000 Subject: [freenet-support] #1173: Internal error: Found interface freenet.support.compress.Compressor, but class was expected In-Reply-To: <49174317.3070704@web.de> References: <4916C47C.5070100@web.de> <20081109114916.1b070159.dennisn@dennisn.dyndns.org> <49174317.3070704@web.de> Message-ID: <200811101524.10546.toad@amphibian.dyndns.org> After talking to nextgens, I have a theory: Go to the Browse Freenet page. At the bottom, find out what version of freenet-ext.jar you are using. Then give me the md5sum of the jar (you may need to shut down the node, and there may be two -ext's; you want whichever one wrapper.conf refers to). If the ext version is prior to version 24, please run update.sh / update.cmd manually to update it. This should solve your problem. On Sunday 09 November 2008 20:07, freenetwork at web.de wrote: > > Dennis Nezic wrote: > >> On Sun, 09 Nov 2008 12:07:40 +0100, > >> "freenetwork at web.de" wrote: > >> > >> Hi list, > >> > >> after updating to lastest mandatory build #1173 revision r23439 all my > >> downloads are failing with "Internal error: Found interface > >> freenet.support.compress.Compressor, but class was expected" as error > >> message. The downloads have been started and taken over from a > >> previous build. > >> > > > > Strange--all my downloads do seem to have recovered throughout all > > these past updates. Though, I believe my downloads are fairly recent (a > > week or so old) inserts--not sure if that matters. > > > > Did you try restarting any of them? New compression procedures were > > introduced around 1170, so maybe that is affecting it. > Restarting them resulted in the downloads going back to "Internal error: > ..." within seconds. I tried several times with several node restarts... > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081110/c53fa084/attachment.pgp From toad at amphibian.dyndns.org Wed Nov 12 13:27:06 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Wed, 12 Nov 2008 13:27:06 +0000 Subject: [freenet-support] Freenet 0.7 build 1174 Message-ID: <200811121327.12978.toad@amphibian.dyndns.org> Freenet 0.7 build 1174 is now available. This will be mandatory on Friday. Changes are minimal, including an important bugfix in connection setup that may help to solve the current packet not acked errors, support for longer filenames in containers, a small bug in the logging code, adding wAnnA? to the default bookmarks, and an update to the French translation. Please upgrade. Please report any bugs, preferably to the bug tracker at https://bugs.freenetproject.org/ . Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081112/40330a74/attachment.pgp From toad at amphibian.dyndns.org Thu Nov 13 18:16:55 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Thu, 13 Nov 2008 18:16:55 +0000 Subject: [freenet-support] Freenet 0.7 build 1175 Message-ID: <200811131817.06852.toad@amphibian.dyndns.org> Freenet 0.7 build 1175 is now available. Please upgrade. Changes: - Handle the "Packet X sent Yms ago and still not acked" bug better. Don't complain in the log until 10 minutes, then disconnect from the peer and log the fact. We can then reconnect, but we will do so cleanly, so hopefully not get it again for a while. It seems that most of the disruption caused by this bug was caused by the logging on every resend and not the bug itself... Of course we will need to fix the bug too. - Show a search box on the homepage, pointing to XMLLibrarian, if XMLLibrarian is not loaded. - Finnish translation update. Please report any bugs you find to the bug tracker: https://bugs.freenetproject.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081113/3e47955e/attachment.pgp From toad at amphibian.dyndns.org Thu Nov 13 18:52:52 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Thu, 13 Nov 2008 18:52:52 +0000 Subject: [freenet-support] State of the Freenet, and tentative roadmap Message-ID: <200811131852.58250.toad@amphibian.dyndns.org> CHANGES SINCE 0.7 Lots of work has been done on Freenet since 0.7 was released. The main highlights in code already shipped and available are sdiz's new datastore (which should greatly improve CPU usage and I/O), lots of debugging, profiling and optimisation, and two major improvements to routing: friend-of-a-friend routing and turning off location swapping on opennet. These two should improve data retention and performance significantly. We have also implemented empirical measurements of network performance, which have proved useful although they give a rather noisy signal. And there are two major projects which have not yet been deployed, which are discussed below: the db4o branch, and the new Freetalk plugin. Other changes include better bandwidth limiting. The conference in July came up with many good ideas; some of these are already in 0.8, some will be postponed to later versions, but it was great to meet up with everyone and make sure we're all on the same page, including the theoreticians. All this, plus some small further changes and a lot of debugging, should make for a 0.8.0 some time in the next few months which will be a major improvement on 0.7.0, and will have taken much less than the nearly 3 years it took to reach 0.7.0! FINANCES We currently have $6863.24., including $4820 remaining from Google. This is shown live (updated hourly) on the web site. Emu costs around ?80/month, I cost around ?1440/month; the weak pound obviously helps matters, but when I started work on Freenet I only cost $1250/mo; now I cost nearly twice that (in a few months time I might be prepared to take a small pay cut, but it won't cover the difference). This makes keeping going from individual donations difficult, and over the last 18 months we've largely continued from large donations from individuals or companies - Google's and John Gilmore's being the biggest. Hopefully shipping 0.8 (or 0.8 alpha 1) combined with an urgent appeal for funds will generate us some more publicity and more cash, and more volunteers, but it's an open question whether we will make enough to keep going for more than a few months. DB4O STATUS The db4o branch is an attempt to put most of the client layer into a lightweight object database, so that we have no more hours of reloading the pending requests from the datastore after a restart, faster startups, and vastly less memory usage for large download queues. It has achieved most of these goals already, but it has taken far longer than anticipated, and this is why I haven't been working much on the mainstream stable Freenet over the last 5 months. However it should be ready soon: I will post a new jar for wider testing soon, and with a few more weeks of work it should be ready to merge. FREETALK (FORUMS IN FREENET) AND WEB INTERFACE USABILITY Chat is essential for any community, especially an anonymous one; without a good anonymous chat system, the chances of new users continuing to use Freenet are low IMHO. We had Frost, but an unknown person has effectively destroyed Frost with denial of service attacks (made possible by Frost's weak design). FMS is the chat system currently used most widely on Freenet, and its architecture should be immune to the attacks on Frost, but FMS has some serious problems: It is written in C++, so is difficult to bundle with Freenet, and cannot be an obvious part of the web interface or inlined in freesites; it uses both a newsreader and a web browser, so is hard to use; and it has had some exploitable bugs, and may still have them. I have stopped using FMS because I don't have time to do a proper code review (and I'm not sure I'm competent to do so), and nobody I trust has done one. So we clearly need a new chat system. Thanks to the massive efforts of batosai, saces and especially xor/p0s, the Freetalk plugin should be ready by the time we ship 0.8. This will be a menu item on the web interface, just under Browse Freenet, and will be an officially code reviewed and supported plugin. Hopefully its web interface will also be embeddable in freesites, as a site forums system. Freemail may also be added to the top level GUI, if and when it becomes sufficiently stable and has a good web interface; we had a Summer of Code student working on one but that didn't work out. There has been lots of discussion on making the user interface more friendly. The main principle here is to make what you can do with Freenet more obvious, and hide technical details in submenus. This of course means all the major functions of Freenet must be bundled and code reviewed as plugins, and accessible from Fproxy (experience suggests most users won't use them if they're not obvious and two clicks away!). Real time chat among darknet peers has also been discussed, with a more "social networking" feel for darknet, since that's exactly what it is. Dieppe has built some mockups (especially the first one): http://doc-fr.freenetproject.org/Fproxy_mockup http://amphibian.dyndns.org/freenet/browse-mockup/html/browse.html http://amphibian.dyndns.org/freenet/mockup2/mockup2/html/browse.html TENTATIVE ROADMAP 0.8: - ALREADY IMPLEMENTED: New compression algorithms, FOAF, no swap on opennet, salted hash datastore, lots of minor refactoring, ... - Merge the db4o branch. - Some work on plugin dependancies, plugin updating. - More work on searching: adjacent word matching, fix the spider, make it look better, possibly make it embeddable in freesites and support adding indexes from freesites. - LOTS of debugging. Debug current network problems, debug bootstrapping taking ages ... - Hopefully bundle a working and reasonably easy to use Freetalk. 0.9: - Rest of the UI refactoring. - Splitfile crypto randomization (greatly improves security for large inserts). - Tunnels. Greatly improve security, significant performance cost. - Bloom filters. Greatly improve performance, significant security cost. - BUT PUT THEM TOGETHER, and you get greatly improved security for the paranoid at a slighty performance cost, improved security and current performance or better for the moderately paranoid, and greatly improved performance for the not so paranoid. - Possibly some low level changes (e.g. streams, a proposal to greatly reduce the bandwidth cost of padding). 0.10: - Passive requests: These are needed for efficient, large scale Web of Trust (a vital component of Freetalk, but also probably useful for filesharing and other things in future). They are also very helpful for other applications such as streaming, and can save significant amounts of bandwidth for downloads in many cases. - Long-term requests: Closely related to passive requests. Needed to deal with uptime issues, and some of the more serious steganographic transport plugins. Uptime issues are especially important: other p2p networks also have to deal with them, often not very well, and the problem will only get worse as more and more people only have laptops. - Possibly transport plugins: This would enable Freenet to pretend to be HTTP traffic, or Skype(tm), or whatever. 1.0 - DEBUG DEBUG DEBUG DEBUG Post 1.0: - Better support for sneakernet and other high latency transports. The main remaining issue is how to assign locations on a low uptime / high latency network. - Content filters for *everything* - PDFs for example are quite feasible, and strategically important, but a lot of work. - Better darknet support - targeted swapping, better fragmented network support, etc. SECURITY SUMMARY There are 3 main classes of attack on Freenet itself that are of particular concern: harvesting nodes, statistical attacks to find out what your peers are doing, and key-based searches where the attacker moves across the network and slowly closes in on the source of some large content. All of them are much harder if you use darknet mode and pick your Friends carefully. Right now Freenet's security is nowhere near what it should be; if you have to stake your freedom or worse on it, think carefully about the risks and the alternatives (which are usually much easier to block). The features mentioned for 0.9 should greatly improve security against these attacks. However, for many purposes, especially if you use a darknet, Freenet is still better than many of the alternatives. NEAR FUTURE/NEAR PAST On Saturday I released builds 1170, 1171, 1172 and 1173. 1170 included at least a month's worth of work on trunk, all since 1166, which wasn't released earlier as it was too unstable. 1173 was self-mandatory, meaning that every node had to upgrade immediately, or lose connectivity. This has caused some short term problems for the network; it was unavoidable, sorry folks. The 1170 changes are quite significant: If you have a freesite, please reinsert it (it will load significantly faster in most cases). Much of the recent chaos (addressed to some degree in 1174 and 1175) may have been caused by my being absent from trunk development, building db4o. That's nearly finished and I'm spending some time on trunk at the moment. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081113/b6e9f452/attachment.pgp From freenet at chello.at Fri Nov 14 01:09:03 2008 From: freenet at chello.at (freenet at chello.at) Date: Fri, 14 Nov 2008 2:09:03 +0100 Subject: [freenet-support] Wrapper does not start Message-ID: <13296196.1226624943915.JavaMail.root@viefep13> Since last update on 13.11. Freenet fails to start. I get the following Message in wrapper.log: STATUS | wrapper | 2008/11/14 02:01:01 | Launching a JVM... INFO | jvm 5 | 2008/11/14 02:01:01 | java.lang.NoClassDefFoundError: freenet/node/NodeStarter INFO | jvm 5 | 2008/11/14 02:01:01 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter INFO | jvm 5 | 2008/11/14 02:01:01 | at java.net.URLClassLoader$1.run(Unknown Source) INFO | jvm 5 | 2008/11/14 02:01:01 | at java.security.AccessController.doPrivileged(Native Method) INFO | jvm 5 | 2008/11/14 02:01:01 | at java.net.URLClassLoader.findClass(Unknown Source) INFO | jvm 5 | 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) INFO | jvm 5 | 2008/11/14 02:01:01 | at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) INFO | jvm 5 | 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) INFO | jvm 5 | 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClassInternal(Unknown Source) INFO | jvm 5 | 2008/11/14 02:01:01 | Exception in thread "main" ERROR | wrapper | 2008/11/14 02:01:01 | JVM exited while loading the application. FATAL | wrapper | 2008/11/14 02:01:01 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2008/11/14 02:01:01 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2008/11/14 02:01:01 | <-- Wrapper Stopped I already included "wrapper.restart.delay=15" to wrapper.conf - but that only delays the hangup. My OS is WinXP pro SP3 From Volodya at WhenGendarmeSleeps.org Fri Nov 14 10:04:30 2008 From: Volodya at WhenGendarmeSleeps.org (Volodya) Date: Fri, 14 Nov 2008 10:04:30 +0000 Subject: [freenet-support] ARKs USKs and SSKs (from Frost) Message-ID: <491D4D2E.2020106@WhenGendarmeSleeps.org> Somebody has asked me to send this (i will post the original in Russian and then the translation done by me) (please note that i don't really think that all of this makes sense, i'm an interpreter) == Original == ????????????? USK ??? ?????????? ARK ????? ????? ??????????. ???? ?? ???: ??? ?????? ????? IP, ???????? ??? ????????? ?????? ???? ??? ??? ????????????? ???????? ?????, ????? ?????? ARK ?????? ?????????????, ??? ???? ?? ???????????, ???????? ?? ?????????? ?????????? ?????? - ? ??? ????? "???????" ?? ????, ???? ????? ???????????? ??????????????? ?????? ????. ? ??????????, ??????, ?????????? ????? ?????????? "????????" ? ?????????????????? ?????? ARK ?????? ????? 4 ??????, ??????????? ??? ?????? ??????? USK - ? ????? "???????" ???????? ARK ??????????? ??????????. ??? ???????? ????? ??? ????, ?????????? ?? ????????????? ? ??????? ???????????? IP. ????????? ??????? ????? ???? ?????? ?????? ARK ?????? ??????, ?????? ??? ????????? ??? ?? ????????? ??????????? ?????? ?????? ?? 5 ?? 100 ?? ????????? ? ????????? (??????????? ????????????? ??????????? ?? ???????????, ? ???????? ?? ???????? ??????????). ??? ?????? ????? ?????? ?? 4, ? 44 ??????????? ??????. ?????? ??????? ?????????? USK/SSK ?????? ? ?????????? ????????? ??????? ????????? ?????? ????????? ?????? SSK, ????? ?????????? ?????? ???????. ???? ??? ??????????? ????, ??? ?????? ????????? ???????? ???????? SSK ? ??? ????????? ???????, ????? ????????? ???????? ??????? ? ???????? ?? ???? ?????????. ? ?????????, _???_ ????????? ??? ???? ????????, ??? ?????????? ??? ??????? ? ????, ? ??? ?????????? ????? ?????????? ?????? ?? ?????????????. ? ?????? (?? ?????????????) ?????? ??? ???????? ???????? ?? ?? ?????????? ? ????? ??????? SSK. ?????????? ?????????? ???????? ???? ?? ????????? ? ???? ????????? ?????? SSK ? ?????? ?????? ? ????????? ??????? ? ??????????????? ??????????? ? ???, ????? ????????? ????????? ?????????? SSK. ??? ?????? ????????? ?????? ????????????? ?????????? ?????????? ?????????. ? ?????????, ???? ???? ??????? ???????? ??? ???????????? ?????? ?? ??????????, ????????? ????????? ?????????? ????? ?????? SSK - ????? ???? ?????? ???????? ??????? ????????? ???????. ????????? ??????? ????? ???? ??? ?????????? ????? ???????? ?????????? ????????? ?????? SSK ?? ????????? ?????????? ? ???? ????? ????? ??????? ????????? ????????? ????????? ? ???, ??? ???? ??????? ???????????? ????????? ??????. ??? ???????? ?????? ???????, ????? ????????? ????????? ???? ??? ????????? ???? ?????? ??? ????: ????????? ?????? (??? ? ?????? ???????), ????????????????? ???????????? (?? ???? ????, ? ?? ????????? ????????? ????????? ?????????? ? ???????? ? ???????????) ??? ?????? ????????? ??????????? ????????? ?????? SSK, ?? ???? ?????????? ????????? SSK ? ?????? ?????? ?? ??? ?????? ? ?????????? ?????? - ?????? ????????? ??? ??? ?????? ? ??????? (??? ?? ??????? ???? ????????????? ?????? ?????????? ??? ??????? ??????????????). ??? ????? ? ??? ?????? ARK, ????????? ????? ????? ???????????? ???? ??? ????????????? ?????? ?????? ARK, ?? ??? ???? ?????????? ????????? ?????????, ??? ????????? ?????? ????????????? ???????? ? ????. ????? ????? ??????????? ???? ?????? ?????, ?????????? ?????????? ?? ?????????? ?????: ?????????? ARK ?????? ???? ? ???????? ??????? ????? "???????" ?? ????, ?? ??? ???? ????? ?? ??????? ???? ????? ???????????? - ? ??? ??? ??????, ?? ????? ???????????? ????????? IP, ?? ?????? ???????? ???? ARK. == Translation == Using of USK for the implimentation of ARK has obvious downfalls. One of them is that during the rapid change of IP, for example during the change of the version of the node or during the repeated connection loss, number of ARK increases rapidly, and during this process there is no attempt to check if previous versions are still accessible; and they can "fall out" from the network, if almost instantaneously other nodes are restarting. As a result, as it seems, quite often "breaks" in the sequence of ARK appear with the length of more than 4 versions, which is a requirement for the working of normal USK; this leads to the search for the "new" ARK number giving no results. This is especially important for the nodes working less than 24 hours a day and having a dynamic IP. One solution may be a request for ARK far ahead, say a few times with the random increase of a version number from 5 to 100 related to the existing one (of course distributed not equally, but maybe as a reverse exponent). Or a dumb request for 44 rather than 4 following versions. Another bug problem of USK/SSK is related to the algorithm of attempting repeat write to the existing SSK, when a specific version is provided. Node after finding that another programme attempts to write SSK with the already existing version immediately interrupts the request and notifies the programme. Unfortunately _ALL_ the programmes after that assume that information is already on the network, and if no new information exists do nothing. In the best (but not optimal) case they attempt to write the same information to the new version of SSK. Correct behaviour of the programmes would be to ask the node for the existing version of SSK in full and check the completeness and correctness of the received, to exclude the existence of the unreadable SSK. In case of an problem with the fetch of the data the need for the reinsert becomes clear. Unfortunately even if one knows ahead of the time that the data has not changed, programmes are forced to write a new version of SSK, or the node will once again interrupt the request. One optional solution may be the node allowing the rewrite of the current version of SSK until it finishes successfully and only after letting the programme know that the write has been successful as a rewrite of the data. Or beginning of the new request when programme asks the node how to behave if the version already exists: repeat write (as the first solution), check the match (the node, not the programme, asks for the current version and compares)or only check the fetchability of the existing version of SSK (attempt to read SSK in the full but without providing the data or writing it anywhere) - only check the existence (or at least that there are enough blocks for full reconstruction). This is important also for the working of ARK, as often restart of the node is not a reason to reinsert the ARK version, but it is important that the existing version is still in the network. Otherwise even neighbours working constantly on the constant address: unchanged ARK of such a node can "fall off" the network, but the node itself will not notice that even after the restart; but the neighbours during the restart after changing IP will be unable to get that ARK. == End == -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut "None of us are free until all of us are free." ~ Mihail Bakunin From dennisn at dennisn.dyndns.org Fri Nov 14 17:40:46 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Fri, 14 Nov 2008 12:40:46 -0500 Subject: [freenet-support] Freenet 0.7 build 1175 In-Reply-To: <200811131817.06852.toad@amphibian.dyndns.org> References: <200811131817.06852.toad@amphibian.dyndns.org> Message-ID: <20081114124046.b8c56494.dennisn@dennisn.dyndns.org> On Thu, 13 Nov 2008 18:16:55 +0000, Matthew Toseland wrote: > Freenet 0.7 build 1175 is now available. Please upgrade. Changes: > - Handle the "Packet X sent Yms ago and still not acked" bug better. > Don't complain in the log until 10 minutes, then disconnect from the > peer and log the fact. We can then reconnect, but we will do so > cleanly, so hopefully not get it again for a while. It seems that > most of the disruption caused by this bug was caused by the logging > on every resend and not the bug itself... Of course we will need to > fix the bug too. State Of The (My) 1175... It "feels" like it's running smoother, although it's cpu profile here hasn't changed substantially. Perhaps just a bit, due to better logging. The log files are finally usable! (Usually under 100K per hour now :) So, in one random 1 hour sample, here are the main ones that I get: 4 "Forcing disconnect" PacketSender ERRORs, both from opennet and darknet peers, "because packets not acked after 10 minutes!". Does this mean that NO packets have been received from these peers, or just a big bunch of them? (I'm pretty sure my ISP doesn't kill connections, but just drops a fraction of the packets.) For some reason, these error messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) netPeerNode. 40 MessageCore ERRORs "from RequestSender waitFor _unclaimed iteration took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit" or "from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize of 596 for matched: true" 24 freenet.io.xfer.BlockTransmitter.sendAsync(), "Terminated send -123413232423 ... as we haven't heard from receiver in 1m54s." 4 freenet.io.xferPacketThrottle, Blocktransmitter: "Unable to send throttled message, waited 60100ms" 6 freenet.io.comm.MessageCore Scheduled job ERRORS "removeTimedOutFilters took 4000ms" 4 freenet.node.KeyTracker PacketSender "Packet 1234 sent over 600600ms ago and still not acked". (THEY STILL EXIST!?! ;) 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet and opennet), "processing packet took 4000ms" .. with times ranging from 3000ms to 6600ms. 8 freenet.node.FNPPacketMangler "Message[1..4] timeout error: Processing packet for freenetnode.tld:1234" Also, in this log, I have noticed that the port number, in the @ip:port@ portion of the error message does NOT match the port number listed on the /friends/ web page. Why is that? (What happens, by the way, if a darknet peer does change his port, by the way--we'd have to re-add his node reference?) From lmartineau at cyberus.ca Thu Nov 13 22:47:49 2008 From: lmartineau at cyberus.ca (Lorraine Martineau) Date: Thu, 13 Nov 2008 17:47:49 -0500 Subject: [freenet-support] connecting Message-ID: <000601c945e1$dc3aa9c0$909fc5d1@D7HM3L81> I thought that I had downloaded all the requirements for registering with Freenet . I was however stumped by the userid question and didn't fill it . I probably should have entered "lorraine". Can you see this application and tell me how to retrieve it, or do I start over. Thank you for your assistance. I wish to disconnect from Cyberus. Is that the first thing to do...I didn't know how I could connect to Freenet without a server. Lorraine Martineau lmartineau at freenet.ca I hope!!! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081113/447aa18b/attachment.htm From markushahnma at yahoo.de Fri Nov 14 14:56:25 2008 From: markushahnma at yahoo.de (Markus Hahn) Date: Fri, 14 Nov 2008 14:56:25 +0000 (GMT) Subject: [freenet-support] Former mail "Can't open again" is out of date. Need Friends. Message-ID: <848258.35880.qm@web28615.mail.ukl.yahoo.com> Dear Supporters, the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some "friends". But still I don't know how to operate it from the command line (bash or dash). Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081114/4e5fae5d/attachment.htm From toad at amphibian.dyndns.org Fri Nov 14 19:24:49 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 19:24:49 +0000 Subject: [freenet-support] connecting In-Reply-To: <000601c945e1$dc3aa9c0$909fc5d1@D7HM3L81> References: <000601c945e1$dc3aa9c0$909fc5d1@D7HM3L81> Message-ID: <200811141924.50707.toad@amphibian.dyndns.org> On Thursday 13 November 2008 22:47, Lorraine Martineau wrote: > I thought that I had downloaded all the requirements for registering with Freenet . I was however stumped by the userid question and didn't fill it . I probably should have entered "lorraine". > Can you see this application and tell me how to retrieve it, or do I start over. > Thank you for your assistance. > I wish to disconnect from Cyberus. Is that the first thing to do...I didn't know how I could connect to Freenet without a server. > Lorraine Martineau > lmartineau at freenet.ca I hope!!! I really think you've got the wrong Freenet here ... This mailing list is for http://freenetproject.org/ : a censorship resistant peer to peer network: ========================================== What is Freenet? Freenet is free software which lets you publish and obtain information on the Internet without fear of censorship. To achieve this freedom, the network is entirely decentralized and publishers and consumers of information are anonymous. Without anonymity there can never be true freedom of speech, and without decentralization the network will be vulnerable to attack. Communications by Freenet nodes are encrypted and are "routed-through" other nodes to make it extremely difficult to determine who is requesting the information and what its content is. Users contribute to the network by giving bandwidth and a portion of their hard drive (called the "data store") for storing files. Unlike other peer-to-peer file sharing networks, Freenet does not let the user control what is stored in the data store. Instead, files are kept or deleted depending on how popular they are, with the least popular being discarded to make way for newer or more popular content. Files in the data store are encrypted to reduce the likelihood of prosecution by persons wishing to censor Freenet content. The network can be used in a number of different ways and isn't restricted to just sharing files like other peer-to-peer networks. It acts more like an Internet within an Internet. For example Freenet can be used for: * Publishing websites or 'freesites' * Communicating via message boards * Content distribution * Sending email messages Unlike many cutting edge projects, Freenet long ago escaped the science lab, it has been downloaded by over 2 million users since the project started, and it is used for the distribution of censored information all over the world including countries such as China and the Middle East. Ideas and concepts pioneered in Freenet have had a significant impact in the academic world. Our 2000 paper "Freenet: A Distributed Anonymous Information Storage and Retrieval System" was the most cited computer science paper of 2000 according to Citeseer, and Freenet has also inspired papers in the worlds of law and philosophy. Ian Clarke, Freenet's creator and project coordinator, was selected as one of the top 100 innovators of 2003 by MIT's Technology Review magazine. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/0a6c8f67/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 19:39:45 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 19:39:45 +0000 Subject: [freenet-support] Freenet 0.7 build 1178 (and 1176, 1177) Message-ID: <200811141939.51728.toad@amphibian.dyndns.org> Freenet 0.7 build 1178 is now available. Please upgrade. Sorry I accidentally released 1176, then had some bugfixes in 1177 and 1178. Anyway, the main changes relative to 1175: - Try to prevent both sides of a connection attempting to rekey at the same time, by having the receiver start 2.5 minutes early. This seems to have been the root cause of many of the recent problems. It may not be completely fixed, but should happen much less often. - When we disconnect from a peer because of it not acknowledging our packets, tell the user via a useralert as well as logging an error. - Get rid of WouldBlockException errors as well: If we cannot send a packet to a peer because there are too many packets in flight and none are being acknowledged, don't busy-loop and spam the logs, wait for it to become un-blocked again. If it doesn't become un-blocked in 10 minutes, log an error and tell the user via a useralert. - Change the default log rotation period to 10 minutes rather than 1 hour to save disk space. - Clarify the config option for packet padding: Turning off packet padding is BAD. Packet padding is essential against a passive attacker. In the next few days you may see the "Probably a bug" errors on the web interface. Hopefully once this build is mandatory (on Monday) these will go away. If you still see these from Tuesday onwards, let us know. Please update, and let us know how it works out. Hopefully this build will fix most of the recent network problems, oversized log files and high CPU usage when not doing anything. If you find any bugs, please report them on the bug tracker: https://bugs.freenetproject.org/ . Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/ca5614f9/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 19:48:13 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 19:48:13 +0000 Subject: [freenet-support] Wrapper does not start In-Reply-To: <13296196.1226624943915.JavaMail.root@viefep13> References: <13296196.1226624943915.JavaMail.root@viefep13> Message-ID: <200811141948.15089.toad@amphibian.dyndns.org> On Friday 14 November 2008 01:09, freenet at chello.at wrote: > Since last update on 13.11. Freenet fails to start. > I get the following Message in wrapper.log: You let freenet auto-update itself, or you used update.sh/update.cmd? If you let Freenet auto-update itself, then please send me your wrapper.log, as this is a serious bug we've been trying to gather more info on ... You can get your node back by running update.sh/update.cmd. > > STATUS | wrapper | 2008/11/14 02:01:01 | Launching a JVM... > INFO | jvm 5 | 2008/11/14 02:01:01 | java.lang.NoClassDefFoundError: freenet/node/NodeStarter > INFO | jvm 5 | 2008/11/14 02:01:01 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter > INFO | jvm 5 | 2008/11/14 02:01:01 | at java.net.URLClassLoader$1.run(Unknown Source) > INFO | jvm 5 | 2008/11/14 02:01:01 | at java.security.AccessController.doPrivileged(Native Method) > INFO | jvm 5 | 2008/11/14 02:01:01 | at java.net.URLClassLoader.findClass(Unknown Source) > INFO | jvm 5 | 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) > INFO | jvm 5 | 2008/11/14 02:01:01 | at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > INFO | jvm 5 | 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) > INFO | jvm 5 | 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClassInternal(Unknown Source) > INFO | jvm 5 | 2008/11/14 02:01:01 | Exception in thread "main" > ERROR | wrapper | 2008/11/14 02:01:01 | JVM exited while loading the application. > FATAL | wrapper | 2008/11/14 02:01:01 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. > FATAL | wrapper | 2008/11/14 02:01:01 | There may be a configuration problem: please check the logs. > STATUS | wrapper | 2008/11/14 02:01:01 | <-- Wrapper Stopped > > I already included "wrapper.restart.delay=15" to wrapper.conf - but that only delays the hangup. > > My OS is WinXP pro SP3 > > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/f872a408/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 19:52:46 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 19:52:46 +0000 Subject: [freenet-support] Freenet 0.7 build 1175 In-Reply-To: <20081114124046.b8c56494.dennisn@dennisn.dyndns.org> References: <200811131817.06852.toad@amphibian.dyndns.org> <20081114124046.b8c56494.dennisn@dennisn.dyndns.org> Message-ID: <200811141952.48081.toad@amphibian.dyndns.org> On Friday 14 November 2008 17:40, Dennis Nezic wrote: > On Thu, 13 Nov 2008 18:16:55 +0000, Matthew Toseland > wrote: > > > Freenet 0.7 build 1175 is now available. Please upgrade. Changes: > > - Handle the "Packet X sent Yms ago and still not acked" bug better. > > Don't complain in the log until 10 minutes, then disconnect from the > > peer and log the fact. We can then reconnect, but we will do so > > cleanly, so hopefully not get it again for a while. It seems that > > most of the disruption caused by this bug was caused by the logging > > on every resend and not the bug itself... Of course we will need to > > fix the bug too. > > State Of The (My) 1175... It "feels" like it's running smoother, > although it's cpu profile here hasn't changed substantially. Perhaps > just a bit, due to better logging. The log files are finally usable! > (Usually under 100K per hour now :) It still has 100% CPU most of the time then? Apparently resulting from Freenet itself rather than downloads etc? Try 1178 ... and then wait until say Wednesday ... hopefully once everyone has 1178, it will be much better. > > So, in one random 1 hour sample, here are the main ones that I get: > > 4 "Forcing disconnect" PacketSender ERRORs, both from opennet and > darknet peers, "because packets not acked after 10 minutes!". Does this > mean that NO packets have been received from these peers, or just a big > bunch of them? (I'm pretty sure my ISP doesn't kill connections, but > just drops a fraction of the packets.) For some reason, these error > messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) > netPeerNode. This is caused by the bugs we're chasing at the moment. Hopefully next week it will have gone away, or be very rare. It means that we are still connected to the node, it's still sending us packets, but it apparently doesn't understand some of the packets we send it. > > 40 MessageCore ERRORs "from RequestSender waitFor _unclaimed iteration > took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit" or > "from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize > of 596 for matched: true" > > 24 freenet.io.xfer.BlockTransmitter.sendAsync(), "Terminated send > -123413232423 ... as we haven't heard from receiver in 1m54s." > > 4 freenet.io.xferPacketThrottle, Blocktransmitter: "Unable to send > throttled message, waited 60100ms" > > 6 freenet.io.comm.MessageCore Scheduled job ERRORS > "removeTimedOutFilters took 4000ms" Hopefully these are related to the current bugs. If so they should greatly reduce. On the other hand, they may not be ... > > 4 freenet.node.KeyTracker PacketSender "Packet 1234 sent over 600600ms > ago and still not acked". (THEY STILL EXIST!?! ;) Yes, we log them at the same time as the disconnections. > > 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet > and opennet), "processing packet took 4000ms" .. with times ranging > from 3000ms to 6600ms. > > 8 freenet.node.FNPPacketMangler "Message[1..4] timeout error: > Processing packet for freenetnode.tld:1234" > > Also, in this log, I have noticed that the port number, in the > @ip:port@ portion of the error message does NOT match the port number > listed on the /friends/ web page. Why is that? It can be different, usually because of NATs, occasionally because you are connected both to the darknet and opennet nodes on that IP (which is a bug, shouldn't happen unless you have some wierd configs set). > (What happens, by the > way, if a darknet peer does change his port, by the way--we'd have to > re-add his node reference?) Probably yes. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/973c40ee/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 19:59:02 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 19:59:02 +0000 Subject: [freenet-support] Freenet 0.7 build 1175 In-Reply-To: <200811141952.48081.toad@amphibian.dyndns.org> References: <200811131817.06852.toad@amphibian.dyndns.org> <20081114124046.b8c56494.dennisn@dennisn.dyndns.org> <200811141952.48081.toad@amphibian.dyndns.org> Message-ID: <200811141959.03289.toad@amphibian.dyndns.org> Please tell me, one way or the other, whether the problem is solved or whether Freenet continues to use lots of CPU etc etc. Thanks. On Friday 14 November 2008 19:52, Matthew Toseland wrote: > On Friday 14 November 2008 17:40, Dennis Nezic wrote: > > On Thu, 13 Nov 2008 18:16:55 +0000, Matthew Toseland > > wrote: > > > > > Freenet 0.7 build 1175 is now available. Please upgrade. Changes: > > > - Handle the "Packet X sent Yms ago and still not acked" bug better. > > > Don't complain in the log until 10 minutes, then disconnect from the > > > peer and log the fact. We can then reconnect, but we will do so > > > cleanly, so hopefully not get it again for a while. It seems that > > > most of the disruption caused by this bug was caused by the logging > > > on every resend and not the bug itself... Of course we will need to > > > fix the bug too. > > > > State Of The (My) 1175... It "feels" like it's running smoother, > > although it's cpu profile here hasn't changed substantially. Perhaps > > just a bit, due to better logging. The log files are finally usable! > > (Usually under 100K per hour now :) > > It still has 100% CPU most of the time then? Apparently resulting from Freenet > itself rather than downloads etc? > > Try 1178 ... and then wait until say Wednesday ... hopefully once everyone has > 1178, it will be much better. > > > > So, in one random 1 hour sample, here are the main ones that I get: > > > > 4 "Forcing disconnect" PacketSender ERRORs, both from opennet and > > darknet peers, "because packets not acked after 10 minutes!". Does this > > mean that NO packets have been received from these peers, or just a big > > bunch of them? (I'm pretty sure my ISP doesn't kill connections, but > > just drops a fraction of the packets.) For some reason, these error > > messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) > > netPeerNode. > > This is caused by the bugs we're chasing at the moment. Hopefully next week it > will have gone away, or be very rare. It means that we are still connected to > the node, it's still sending us packets, but it apparently doesn't understand > some of the packets we send it. > > > > 40 MessageCore ERRORs "from RequestSender waitFor _unclaimed iteration > > took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit" or > > "from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize > > of 596 for matched: true" > > > > 24 freenet.io.xfer.BlockTransmitter.sendAsync(), "Terminated send > > -123413232423 ... as we haven't heard from receiver in 1m54s." > > > > 4 freenet.io.xferPacketThrottle, Blocktransmitter: "Unable to send > > throttled message, waited 60100ms" > > > > 6 freenet.io.comm.MessageCore Scheduled job ERRORS > > "removeTimedOutFilters took 4000ms" > > Hopefully these are related to the current bugs. If so they should greatly > reduce. On the other hand, they may not be ... > > > > 4 freenet.node.KeyTracker PacketSender "Packet 1234 sent over 600600ms > > ago and still not acked". (THEY STILL EXIST!?! ;) > > Yes, we log them at the same time as the disconnections. > > > > 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet > > and opennet), "processing packet took 4000ms" .. with times ranging > > from 3000ms to 6600ms. > > > > 8 freenet.node.FNPPacketMangler "Message[1..4] timeout error: > > Processing packet for freenetnode.tld:1234" > > > > Also, in this log, I have noticed that the port number, in the > > @ip:port@ portion of the error message does NOT match the port number > > listed on the /friends/ web page. Why is that? > > It can be different, usually because of NATs, occasionally because you are > connected both to the darknet and opennet nodes on that IP (which is a bug, > shouldn't happen unless you have some wierd configs set). > > > (What happens, by the > > way, if a darknet peer does change his port, by the way--we'd have to > > re-add his node reference?) > > Probably yes. > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/647227bc/attachment.pgp From dennisn at dennisn.dyndns.org Fri Nov 14 20:42:30 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Fri, 14 Nov 2008 15:42:30 -0500 Subject: [freenet-support] Freenet 0.7 build 1175 In-Reply-To: <200811141952.48081.toad@amphibian.dyndns.org> References: <200811131817.06852.toad@amphibian.dyndns.org> <20081114124046.b8c56494.dennisn@dennisn.dyndns.org> <200811141952.48081.toad@amphibian.dyndns.org> Message-ID: <20081114154230.d552c97d.dennisn@dennisn.dyndns.org> On Fri, 14 Nov 2008 19:52:46 +0000, Matthew Toseland wrote: > It still has 100% CPU most of the time then? Apparently resulting > from Freenet itself rather than downloads etc? Well, it's not /so/ serious that it stays at 100% all the time. It jumps up for a few minutes, then calms down to almost nothing for a few minutes. (The valleys are longer than the peaks.) And keeps repeating this. I'm running another process that steadily uses on average 25% of the (1.2GHz) cpu, and my 15minute load time is consistently around 3. Maybe the threads are all triggered to run at the same time, and should be staggered? > > Also, in this log, I have noticed that the port number, in the > > @ip:port@ portion of the error message does NOT match the port > > number listed on the /friends/ web page. Why is that? > > It can be different, usually because of NATs, occasionally because > you are connected both to the darknet and opennet nodes on that IP > (which is a bug, shouldn't happen unless you have some wierd configs > set). Actually, the logs do say that I was connected to this same ip address both in opennet and darknet :|. (And the opennet port is properly listed in the strangers page. (It seems unlikely that his darknet port would be routed in a NAT, but not his opennet port :|.) From dennisn at dennisn.dyndns.org Fri Nov 14 20:50:36 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Fri, 14 Nov 2008 15:50:36 -0500 Subject: [freenet-support] Former mail "Can't open again" is out of date. Need Friends. In-Reply-To: <848258.35880.qm@web28615.mail.ukl.yahoo.com> References: <848258.35880.qm@web28615.mail.ukl.yahoo.com> Message-ID: <20081114155036.f94ad630.dennisn@dennisn.dyndns.org> On Fri, 14 Nov 2008 14:56:25 +0000 (GMT), Markus Hahn wrote: > Dear Supporters, > > the question I have sent to you some hours ago is obsolete. I have > found the button to start it again. Freenet is running properly. Now > I should try to find some "friends". But still I don't know how to > operate it from the command line (bash or dash). Thanks. Out of curiosity, what kinds of things were you looking to do via the command line? There is, by the way, a telnet interface that lets you do quite a bit, which is disabled by default. There are also some command line tools that interface with freenet, such as pyFreenet, that might be useful, if they work :). From vdenisov at redline.ru Fri Nov 14 22:01:27 2008 From: vdenisov at redline.ru (Victor Denisov) Date: Sat, 15 Nov 2008 01:01:27 +0300 Subject: [freenet-support] Some downloads failing since updating to 1178 Message-ID: <491DF537.5090501@redline.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Several downloads from my download queue failed to start after my node autoupgraded to 1178 (some *did* restart normally). Error messages (Reason column in the "Failed downloads") in the web interface vary: Temporary files error: invalid stored block lengths Temporary files error: Corrupt GZIP trailer Temporary files error: invalid literal/length code Temporary files error: invalid distance code Temporary files error: invalid block type The node gives me two options: Remove and Restart. If I click on restart, the item fails almost immediately with the same error it had before. I've migrated to salted-hash store when 1175 went out. I tried restarting the node again and cleaning up ./tmp - not helped any. I have plenty of disk space. Log files don't seem to contain anything related to the issue I'm experiencing. Running on Windows XP x64 with Java 1.6.0_06, 64 bit. Regards, Victor Denisov. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHfU31O5++4rTuI0RAhAFAKDFwm8VLevPNMI3v/+ArCgrIkAs0wCgp7kX rcAT4OtPrWEnOiMuRGKSz68= =YYIA -----END PGP SIGNATURE----- From dennisn at dennisn.dyndns.org Fri Nov 14 23:21:50 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Fri, 14 Nov 2008 18:21:50 -0500 Subject: [freenet-support] Freenet 0.7 build 1178 (and 1176, 1177) In-Reply-To: <200811141939.51728.toad@amphibian.dyndns.org> References: <200811141939.51728.toad@amphibian.dyndns.org> Message-ID: <20081114182150.89ce7c25.dennisn@dennisn.dyndns.org> On Fri, 14 Nov 2008 19:39:45 +0000, Matthew Toseland wrote: > Freenet 0.7 build 1178 is now available. Wow! What a difference. 1178 is like a totally different program, with respect to both cpu and memory usage. THANK YOU! It's no longer peaking for minutes at a time. It's consistently low. My 15minute load average is below 1 now! Hurray. Memory use also seems much lower. Regarding the "not acked packets" problem, I have alrady been alerted about 5 peers with "severe" problems, one of which is a darknet peer. 2 of the others are listed as CONNECTED. And the other 2 are listed as BACKED OFF. All of them are running 1178. Also, I should repeat ;), One of my peers (ip addresses) is CONNECTED to me both in opennet and darknet. All in all, though, 1178 is a HUGE improvement! From toad at amphibian.dyndns.org Fri Nov 14 23:32:42 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 23:32:42 +0000 Subject: [freenet-support] Freenet 0.7 build 1178 (and 1176, 1177) In-Reply-To: <20081114182150.89ce7c25.dennisn@dennisn.dyndns.org> References: <200811141939.51728.toad@amphibian.dyndns.org> <20081114182150.89ce7c25.dennisn@dennisn.dyndns.org> Message-ID: <200811142332.53748.toad@amphibian.dyndns.org> On Friday 14 November 2008 23:21, Dennis Nezic wrote: > On Fri, 14 Nov 2008 19:39:45 +0000, Matthew Toseland > wrote: > > > Freenet 0.7 build 1178 is now available. > > Wow! What a difference. 1178 is like a totally different program, with > respect to both cpu and memory usage. THANK YOU! It's no longer peaking > for minutes at a time. It's consistently low. My 15minute load average > is below 1 now! Hurray. Memory use also seems much lower. > > Regarding the "not acked packets" problem, I have alrady been alerted > about 5 peers with "severe" problems, one of which is a darknet peer. 2 > of the others are listed as CONNECTED. And the other 2 are listed as > BACKED OFF. All of them are running 1178. > > Also, I should repeat ;), One of my peers (ip addresses) is CONNECTED > to me both in opennet and darknet. That's to be expected. We kill the connection, and purge the trackers etc, but we can reconnect afterwards. Also, it's quite possible that those peers were running an earlier version when they actually broke. However, it's also possible that we still have the underlying bug... I've not made much headway with finding it, next week we should know whether it's still active, since 1178 is mandatory on Sunday... > > All in all, though, 1178 is a HUGE improvement! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/b328baca/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 23:38:32 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 23:38:32 +0000 Subject: [freenet-support] Some downloads failing since updating to 1178 In-Reply-To: <491DF537.5090501@redline.ru> References: <491DF537.5090501@redline.ru> Message-ID: <200811142338.34161.toad@amphibian.dyndns.org> Argh. Are these simple downloads (CHK at .../filename), or parts of freesites (mutliple slashes, maybe USKs)?? On Friday 14 November 2008 22:01, Victor Denisov wrote: > Several downloads from my download queue failed to start after my node > autoupgraded to 1178 (some *did* restart normally). Error messages > (Reason column in the "Failed downloads") in the web interface vary: > > Temporary files error: invalid stored block lengths > Temporary files error: Corrupt GZIP trailer > Temporary files error: invalid literal/length code > Temporary files error: invalid distance code > Temporary files error: invalid block type > > The node gives me two options: Remove and Restart. If I click on > restart, the item fails almost immediately with the same error it had > before. > > I've migrated to salted-hash store when 1175 went out. I tried > restarting the node again and cleaning up ./tmp - not helped any. I have > plenty of disk space. Log files don't seem to contain anything related > to the issue I'm experiencing. > > Running on Windows XP x64 with Java 1.6.0_06, 64 bit. > > Regards, > Victor Denisov. > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/3398909f/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 23:34:51 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 23:34:51 +0000 Subject: [freenet-support] Former mail "Can't open again" is out of date. Need Friends. In-Reply-To: <848258.35880.qm@web28615.mail.ukl.yahoo.com> References: <848258.35880.qm@web28615.mail.ukl.yahoo.com> Message-ID: <200811142334.52550.toad@amphibian.dyndns.org> On Friday 14 November 2008 14:56, Markus Hahn wrote: > Dear Supporters, > > the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some "friends". > But still I don't know how to operate it from the command line (bash or dash). Thanks. Most basic functions of Freenet are controlled from the web interface (http://127.0.0.1:8888/). You might have to forward (ssh -L) port 8888 and 9481 to another machine, although in theory it should work with lynx/links. There are third party command line tools available for tasks such as inserting data... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/3d7fd332/attachment.pgp From toad at amphibian.dyndns.org Fri Nov 14 23:55:29 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Fri, 14 Nov 2008 23:55:29 +0000 Subject: [freenet-support] ARKs USKs and SSKs (from Frost) In-Reply-To: <491D4D2E.2020106@WhenGendarmeSleeps.org> References: <491D4D2E.2020106@WhenGendarmeSleeps.org> Message-ID: <200811142355.40072.toad@amphibian.dyndns.org> On Friday 14 November 2008 10:04, Volodya wrote: > Somebody has asked me to send this (i will post the original in Russian and then > the translation done by me) (please note that i don't really think that all of > this makes sense, i'm an interpreter) > > == Translation == > Using of USK for the implimentation of ARK has obvious downfalls. One of them is > that during the rapid change of IP, for example during the change of the version > of the node or during the repeated connection loss, number of ARK increases > rapidly, and during this process there is no attempt to check if previous > versions are still accessible; and they can "fall out" from the network, if > almost instantaneously other nodes are restarting. As a result, as it seems, > quite often "breaks" in the sequence of ARK appear with the length of more than > 4 versions, which is a requirement for the working of normal USK; this leads to > the search for the "new" ARK number giving no results. This is especially > important for the nodes working less than 24 hours a day and having a dynamic IP. > One solution may be a request for ARK far ahead, say a few times with the random > increase of a version number from 5 to 100 related to the existing one (of > course distributed not equally, but maybe as a reverse exponent). Or a dumb > request for 44 rather than 4 following versions. IMHO this is a weakness in USKs themselves, rather than a specific issue for ARKs. Solutions have been proposed but not yet implemented. IIRC we do look further ahead, but we throttle it increasingly heavily, so it takes a long time. > > Another bug problem of USK/SSK is related to the algorithm of attempting repeat > write to the existing SSK, when a specific version is provided. Node after > finding that another programme attempts to write SSK with the already existing > version immediately interrupts the request and notifies the programme. We attempt to find the data (via a USK fetcher). If it is already there and identical, we don't reinsert it. So it could be in the node's datastore and not on the network. > Unfortunately _ALL_ the programmes after that assume that information is already > on the network, and if no new information exists do nothing. In the best (but > not optimal) case they attempt to write the same information to the new version > of SSK. Correct behaviour of the programmes would be to ask the node for the > existing version of SSK in full and check the completeness and correctness of > the received, to exclude the existence of the unreadable SSK. In case of an > problem with the fetch of the data the need for the reinsert becomes clear. > Unfortunately even if one knows ahead of the time that the data has not changed, > programmes are forced to write a new version of SSK, or the node will once again > interrupt the request. > One optional solution may be the node allowing the rewrite of the current > version of SSK until it finishes successfully and only after letting the > programme know that the write has been successful as a rewrite of the data. > Or > beginning of the new request when programme asks the node how to behave if the > version already exists: repeat write (as the first solution), check the match > (the node, not the programme, asks for the current version and compares)or only > check the fetchability of the existing version of SSK (attempt to read SSK in > the full but without providing the data or writing it anywhere) - only check the > existence (or at least that there are enough blocks for full reconstruction). ARKs don't occupy lots of blocks. Having said that they do occupy one more block than necessary - for some reason we insert them with a text/plain mime type, they should be inserted with no MIME type. > This is important also for the working of ARK, as often restart of the node is > not a reason to reinsert the ARK version, but it is important that the existing > version is still in the network. Otherwise even neighbours working constantly on > the constant address: unchanged ARK of such a node can "fall off" the network, > but the node itself will not notice that even after the restart; but the > neighbours during the restart after changing IP will be unable to get that ARK. So basically, what you want is for the node to reinsert the ARK (at the old key) even if it is identical to the existing data. I dunno, maybe that's a good idea. It probably wouldn't get very far most of the time, because it would be terminated at the first node to have the data in its store... Anyone have a view? Other issues with ARKs and USKs: 1. ARKs are currently inserted with a MIME type, resulting in them occupying an SSK and a CHK. An SSK is all that is needed, and since I suspect we have overcapacity in SSKs, that should greatly improve ARKs' reliability. 2. It is hard to find the latest version of a USK when you've lost your place. IMHO the simplest, fastest, and most reliable solution to this is date-based hierarchical pointers (which would simply include the latest edition at a given time). Hence: USK at blah/site/12 -> SSK at blah/site-12 // the actual content But we also insert SSK at blah/site-___DATE___-2008 SSK at blah/site-___DATE___-2008-11 SSK at blah/site-___DATE___-2008-11-14 All of which contain the current edition number, "12". > > == End == > > -- > http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast > http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal > http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut > > "None of us are free until all of us are free." ~ Mihail Bakunin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081114/8c4089cf/attachment.pgp From vdenisov at redline.ru Sat Nov 15 00:17:04 2008 From: vdenisov at redline.ru (Victor Denisov) Date: Sat, 15 Nov 2008 03:17:04 +0300 Subject: [freenet-support] Some downloads failing since updating to 1178 In-Reply-To: <200811142338.34161.toad@amphibian.dyndns.org> References: <491DF537.5090501@redline.ru> <200811142338.34161.toad@amphibian.dyndns.org> Message-ID: <491E1500.7020209@redline.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> Argh. Are these simple downloads (CHK at .../filename), or parts of freesites >> (mutliple slashes, maybe USKs)?? All simple CHKs, inserted with Frost (judging by the redirects). Regards, Victor Denisov. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHhUA1O5++4rTuI0RAuaSAKCknxRlhjs1GXrec8vXKCNpzNMo5ACdHk8U IZ3SQUslfl4EZprfUVpF6r0= =PMOs -----END PGP SIGNATURE----- From mdcsystems at comcast.net Sat Nov 15 00:05:57 2008 From: mdcsystems at comcast.net (Mike Cook) Date: Sat, 15 Nov 2008 00:05:57 +0000 Subject: [freenet-support] (no subject) Message-ID: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> 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: My Node * Freenet 0.7 Build #1178 r23592M * Freenet-ext Build #24 r23199 From freenet at chello.at Sat Nov 15 01:12:02 2008 From: freenet at chello.at (freenet at chello.at) Date: Sat, 15 Nov 2008 2:12:02 +0100 Subject: [freenet-support] Wrapper does not start Message-ID: <32350958.1226711522489.JavaMail.root@viefep13> ---- Matthew Toseland schrieb: > On Friday 14 November 2008 01:09, freenet at chello.at wrote: > > Since last update on 13.11. Freenet fails to start. > > I get the following Message in wrapper.log: > > You let freenet auto-update itself, or you used update.sh/update.cmd? I used update.cmd > If you let Freenet auto-update itself, then please send me your wrapper.log, > as this is a serious bug we've been trying to gather more info on ... > > You can get your node back by running update.sh/update.cmd. I did it, but then the same error happens again. :( Is there no "rollback" for updates? From freenet at peterjoosten.nl Sat Nov 15 08:48:26 2008 From: freenet at peterjoosten.nl (Peter J.) Date: Sat, 15 Nov 2008 09:48:26 +0100 Subject: [freenet-support] (no subject) In-Reply-To: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> References: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> Message-ID: <200811150948.26570.freenet@peterjoosten.nl> On Saturday 15 November 2008 01:05:57 Mike Cook wrote: > 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: > > > My Node > * Freenet 0.7 Build #1178 r23592M > * Freenet-ext Build #24 r23199 > Got the same message with the same build of freenet. But I've got 4 peers reported to have severe problems. From freenet at peterjoosten.nl Sat Nov 15 08:54:33 2008 From: freenet at peterjoosten.nl (Peter J.) Date: Sat, 15 Nov 2008 09:54:33 +0100 Subject: [freenet-support] (no subject) In-Reply-To: <200811150948.26570.freenet@peterjoosten.nl> References: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> <200811150948.26570.freenet@peterjoosten.nl> Message-ID: <200811150954.33145.freenet@peterjoosten.nl> On Saturday 15 November 2008 09:48:26 Peter J. wrote: > On Saturday 15 November 2008 01:05:57 Mike Cook wrote: > > 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: > > > > > > My Node > > * Freenet 0.7 Build #1178 r23592M > > * Freenet-ext Build #24 r23199 > > > > Got the same message with the same build of freenet. But I've got 4 peers > reported to have severe problems. Ok I didn't read the other new messages on the list before I read this one. So it is to be expected that this message is gone after Sunday when the new version of freenet is mandatory? From guido-frn at unknownsite.de Sat Nov 15 13:21:02 2008 From: guido-frn at unknownsite.de (Guido Winkelmann) Date: Sat, 15 Nov 2008 14:21:02 +0100 Subject: [freenet-support] Some downloads failing since updating to 1178 In-Reply-To: <491DF537.5090501@redline.ru> References: <491DF537.5090501@redline.ru> Message-ID: <200811151421.02331.guido-frn@unknownsite.de> I can confirm the described behaviour. My system: Linux on x86_64, Java 1.6.0_07-b06. The downloads were started with frost, but they have not been inserted by Frost. Guido Am Freitag, 14. November 2008 23:01:27 schrieb Victor Denisov: > Several downloads from my download queue failed to start after my node > autoupgraded to 1178 (some *did* restart normally). Error messages > (Reason column in the "Failed downloads") in the web interface vary: > > Temporary files error: invalid stored block lengths > Temporary files error: Corrupt GZIP trailer > Temporary files error: invalid literal/length code > Temporary files error: invalid distance code > Temporary files error: invalid block type > > The node gives me two options: Remove and Restart. If I click on > restart, the item fails almost immediately with the same error it had > before. > > I've migrated to salted-hash store when 1175 went out. I tried > restarting the node again and cleaning up ./tmp - not helped any. I have > plenty of disk space. Log files don't seem to contain anything related > to the issue I'm experiencing. > > Running on Windows XP x64 with Java 1.6.0_06, 64 bit. > > Regards, > Victor Denisov. -- Truth as the authority instead of truth by authority! -- | _ | ASCII Ribbon Campaign Against HTML Emails. | ( ) | | X | | / \ | From toad at amphibian.dyndns.org Sat Nov 15 17:37:20 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Sat, 15 Nov 2008 17:37:20 +0000 Subject: [freenet-support] (no subject) In-Reply-To: <200811150954.33145.freenet@peterjoosten.nl> References: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> <200811150948.26570.freenet@peterjoosten.nl> <200811150954.33145.freenet@peterjoosten.nl> Message-ID: <200811151737.21303.toad@amphibian.dyndns.org> Correct. This should go away after 1178 is mandatory on Sunday, provided you restart your node at that point. However, the trend so far suggests that it won't go away and is still present. :< In any case we need to be told if it happens after Sunday. On Saturday 15 November 2008 08:54, Peter J. wrote: > On Saturday 15 November 2008 09:48:26 Peter J. wrote: > > On Saturday 15 November 2008 01:05:57 Mike Cook wrote: > > > 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: > > > > > > > > > My Node > > > * Freenet 0.7 Build #1178 r23592M > > > * Freenet-ext Build #24 r23199 > > > > > > > > Got the same message with the same build of freenet. But I've got 4 peers > > reported to have severe problems. > > > > Ok I didn't read the other new messages on the list before I read this one. So > it is to be expected that this message is gone after Sunday when the new > version of freenet is mandatory? > > > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081115/bda3b7f7/attachment.pgp From dennisn at dennisn.dyndns.org Sat Nov 15 20:18:33 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Sat, 15 Nov 2008 15:18:33 -0500 Subject: [freenet-support] Freenet 0.7 build 1178 (and 1176, 1177) In-Reply-To: <20081114182150.89ce7c25.dennisn@dennisn.dyndns.org> References: <200811141939.51728.toad@amphibian.dyndns.org> <20081114182150.89ce7c25.dennisn@dennisn.dyndns.org> Message-ID: <20081115151833.693c9530.dennisn@dennisn.dyndns.org> On Fri, 14 Nov 2008 18:21:50 -0500, Dennis Nezic wrote: > On Fri, 14 Nov 2008 19:39:45 +0000, Matthew Toseland > wrote: > > > Freenet 0.7 build 1178 is now available. I spoke too soon. It works fine for an hour or two, but then, at least for me, all communcation (net input/output) STOPS. (Well, ~100Bytes/sec both ways--but, for all intents and purposes, it's offline.) After almost exactly 3 hours, it begins Announcing itself (successfully, apparently) although nothing really changes. And this is repeatable. Restarting the node leads to the exact same behaviour. There are very few errors in the freenet logs. A couple per hour, maybe. But, the "common" one that I spotted freenet.node.PeerManager, UdpSocketHandler ERROR addPeerNodeStatus(): "node already in peerNodeStatuses" ... "status DISCONNECTED". But, it's ip address is still listed as CONNECTED, and data is still being transferred with it, although the port number in the log file is different than the one that is listed as connected. (I'm not sure if this is related.) From smallsister at xs4all.nl Sun Nov 16 11:08:45 2008 From: smallsister at xs4all.nl (SmallSister development) Date: Sun, 16 Nov 2008 12:08:45 +0100 Subject: [freenet-support] Broken freesites in #1178 Message-ID: <491FFF3D.2060602@xs4all.nl> Hello, I've noted that freesites that are recently updated (The Ultimate FreeNet Index) appear broken. My personal freesite (that was inserted with jSite after the announcement of the "tar.gz" sites) shows the same problem. Peter. From bbackde at googlemail.com Sun Nov 16 13:30:04 2008 From: bbackde at googlemail.com (bbackde at googlemail.com) Date: Sun, 16 Nov 2008 14:30:04 +0100 Subject: [freenet-support] Version 1179? Message-ID: Many of my peers seem to run 1179 since this morning. I got no notice about this version via mailing list, and my node (1178) doesn't offer me this new version for update. Is something broken? update.cmd also doesn't work, see my previous mail that was completely ignored ^^ -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________ From ukoepping at yahoo.de Sun Nov 16 15:46:33 2008 From: ukoepping at yahoo.de (Ulrich Koepping) Date: Sun, 16 Nov 2008 15:46:33 +0000 (GMT) Subject: [freenet-support] bug report: 2 peers forcibly disconnected due to not acknowledging packets Message-ID: <222463.86330.qm@web24008.mail.ird.yahoo.com> 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 From freenetwork at web.de Sun Nov 16 16:14:29 2008 From: freenetwork at web.de (freenetwork at web.de) Date: Sun, 16 Nov 2008 17:14:29 +0100 Subject: [freenet-support] Probably a bug: please report: 3 peers forcibly disconnected due to not acknowledging packets. Message-ID: <492046E5.6080605@web.de> build #1179, svn revision 23640 Probably a bug: please report: 3 peers forcibly disconnected due to not acknowledging packets. 3 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. From freenet at chello.at Sun Nov 16 18:12:48 2008 From: freenet at chello.at (freenet at chello.at) Date: Sun, 16 Nov 2008 19:12:48 +0100 Subject: [freenet-support] Wrapper does not start Message-ID: <22182787.1226859168678.JavaMail.root@viefep13> Since I updated to 1179, it works again. No problems with up- and downloads or freesites. From jordietus at yahoo.com Sun Nov 16 20:53:36 2008 From: jordietus at yahoo.com (jordi) Date: Sun, 16 Nov 2008 12:53:36 -0800 (PST) Subject: [freenet-support] bug? Message-ID: <508766.35313.qm@web50809.mail.re2.yahoo.com> I send this message as a probable bug seen in the messages page. 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: * 213.238.213.47:42602 * 72.73.181.44:7420 Version Information & Node Control Freenet 0.7 Build #1178 r23592M Freenet-ext Build #24 r23199 From Volodya at WhenGendarmeSleeps.org Mon Nov 17 07:42:48 2008 From: Volodya at WhenGendarmeSleeps.org (Volodya) Date: Mon, 17 Nov 2008 07:42:48 +0000 Subject: [freenet-support] Version 1179? In-Reply-To: References: Message-ID: <49212078.9000608@WhenGendarmeSleeps.org> bbackde at googlemail.com wrote: > Many of my peers seem to run 1179 since this morning. I got no notice > about this version via mailing list, > and my node (1178) doesn't offer me this new version for update. > Is something broken? update.cmd also doesn't work, see my previous > mail that was completely ignored ^^ > Same here. -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut "None of us are free until all of us are free." ~ Mihail Bakunin From Volodya at WhenGendarmeSleeps.org Mon Nov 17 07:46:21 2008 From: Volodya at WhenGendarmeSleeps.org (Volodya) Date: Mon, 17 Nov 2008 07:46:21 +0000 Subject: [freenet-support] Version 1179? In-Reply-To: <49212078.9000608@WhenGendarmeSleeps.org> References: <49212078.9000608@WhenGendarmeSleeps.org> Message-ID: <4921214D.5020909@WhenGendarmeSleeps.org> Volodya wrote: > bbackde at googlemail.com wrote: >> Many of my peers seem to run 1179 since this morning. I got no notice >> about this version via mailing list, >> and my node (1178) doesn't offer me this new version for update. >> Is something broken? update.cmd also doesn't work, see my previous >> mail that was completely ignored ^^ >> > > Same here. Sorry, just tried ./update.sh again, and it worked. -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut "None of us are free until all of us are free." ~ Mihail Bakunin From claude.dupuy at orange.fr Sun Nov 16 08:05:17 2008 From: claude.dupuy at orange.fr (Dupuy Claude) Date: Sun, 16 Nov 2008 09:05:17 +0100 Subject: [freenet-support] bugs Message-ID: <002c01c947c2$10b64ce0$0c01a8c0@pc1> 3 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: a.. 78.43.183.216:64821 b.. 12.202.88.205:10223 c.. 98.203.234.35:37281 Freenet 0.7 version #1178 r23592M Freenet-ext version #24 r23199 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081116/54c110b7/attachment.htm From dalej8 at o2.pl Sat Nov 15 12:01:43 2008 From: dalej8 at o2.pl (dalej8) Date: Sat, 15 Nov 2008 13:01:43 +0100 Subject: [freenet-support] bug Message-ID: <491EBA27.3010303@o2.pl> Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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: * 83.250.207.180:30547 Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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: * 75.172.65.161:55979 From dark at darkn3t.net Sat Nov 15 12:02:41 2008 From: dark at darkn3t.net (dark at darkn3t.net) Date: Sat, 15 Nov 2008 13:02:41 +0100 Subject: [freenet-support] Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. Message-ID: <91de73500811150402i3fad052i25616b3326a30482@mail.gmail.com> 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: - 85.25.130.157:9134 - 81.209.35.6:10232 Version du noeud - Freenet 0.7 version #1178 r23592M - Freenet-ext version #24 r23199 Informations sur la JVM - M?moire utilis?e par Java : 29.4 MiB - M?moire allou?e par Java : 59.6 MiB - M?moire maximum pour Java : 254 MiB - Processus en cours : 223/500 - Processeurs disponibles : 1 - Version de Java : 1.6.0_07 - Distributeur de la JVM : Sun Microsystems Inc. - Version de la JVM : 10.0-b23 - Nom de l'OS : Linux - Version de l'OS : 2.6.24.5-grsec-xxxx-grs-ipv6-32 - Architecture de l'OS : i386 Load limiting - Global window: 20.192453353961174 - Real global window: 1.3461635569307449 - CHK Request RTT=6,763s delay=0,334s bw=98107B/sec - SSK Request RTT=46,709s delay=2,313s bw=442B/sec - CHK Insert RTT=24,976s delay=1,236s bw=26511B/sec - SSK Insert RTT=20,472s delay=1,013s bw=1010B/sec - CHK window: freenet.node.ThrottleWindowManager at 1aa8b56 w: 2.5080165060084187, d:0.64041173=47719/74513, SSK window: freenet.node.ThrottleWindowManager at 1a1cf72 w: 0.7387861074483295, d:0.6570007=52156/79385 - Request window: freenet.node.ThrottleWindowManager at 3a5cc5 w: 0.9491558356793726, d:0.8450394=4608/5453, Insert window: freenet.node.ThrottleWindowManager at 1a0b7ca w: 2.9888353678397963, d:0.27093595=55/203 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081115/c7a28636/attachment.htm From nuzzle at sbcglobal.net Sat Nov 15 19:59:02 2008 From: nuzzle at sbcglobal.net (Ted Hexter) Date: Sat, 15 Nov 2008 11:59:02 -0800 (PST) Subject: [freenet-support] Bug Report Message-ID: <283583.15354.qm@web82103.mail.mud.yahoo.com> 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: * 24.213.86.235:29470 * 217.236.111.120:25601 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081115/92906506/attachment.htm From markushahnma at yahoo.de Sat Nov 15 23:42:11 2008 From: markushahnma at yahoo.de (Markus Hahn) Date: Sat, 15 Nov 2008 23:42:11 +0000 (GMT) Subject: [freenet-support] (no subject) Message-ID: <650097.5478.qm@web28613.mail.ukl.yahoo.com> Dear Supporters, I am a total newbie in freenet. Every time I start freenet I get the alert that my node lies behind a NAT-device or a Firewall and that I should forward my port-Number 11833. After some discovery-attempts in the administration tool of my router I found out that there is actually a firewall running. I am able to reach and open some of the sites I want to, but frequently I get the message that a site seems to be unreachable, sometimes concerning a site that opens some minutes later. I am totally new in this subject and all my real-world-friends are no-techies and no-nerds, so I still have no "firends" in the sense of trustworthy nodes to connect with or in the sense of darknet-members. Might this be the reason why some sites are closed for me? Should I try to manipulate the router in order to "forward" or should I turn off the firewall? Or is freenet running properly and the seemingly closed doors seem so due to the restrictions a newbie in darknet with a fresh node has to come around with? Thank you a lot for the support -------------- next part -------------- An HTML attachment was scrubbed... URL: http://emu.freenetproject.org/pipermail/support/attachments/20081115/e9872bf1/attachment.htm From freenet at peterjoosten.nl Mon Nov 17 19:27:13 2008 From: freenet at peterjoosten.nl (Peter J.) Date: Mon, 17 Nov 2008 20:27:13 +0100 Subject: [freenet-support] (no subject) In-Reply-To: <200811151737.21303.toad@amphibian.dyndns.org> References: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> <200811150954.33145.freenet@peterjoosten.nl> <200811151737.21303.toad@amphibian.dyndns.org> Message-ID: <200811172027.13446.freenet@peterjoosten.nl> On Saturday 15 November 2008 18:37:20 Matthew Toseland wrote: > Correct. This should go away after 1178 is mandatory on Sunday, provided > you restart your node at that point. However, the trend so far suggests > that it won't go away and is still present. :< In any case we need to be > told if it happens after Sunday. > Ok Matthew, Seems to be still there even with version 1179. 11 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: 70.72.215.120:40858 212.202.31.3:43592 217.196.213.98:24330 88.175.66.28:52590 87.179.226.176:50173 217.153.12.122:50554 212.75.37.89:53150 85.229.124.96:13598 96.250.239.134:64676 86.54.216.133:53061 79.202.89.5:39002 From freenet at peterjoosten.nl Mon Nov 17 19:32:30 2008 From: freenet at peterjoosten.nl (Peter J.) Date: Mon, 17 Nov 2008 20:32:30 +0100 Subject: [freenet-support] (no subject) In-Reply-To: <200811172027.13446.freenet@peterjoosten.nl> References: <111520080005.17236.491E12650008B5C00000435422147564029C030A9B9C979C0C0B03@comcast.net> <200811151737.21303.toad@amphibian.dyndns.org> <200811172027.13446.freenet@peterjoosten.nl> Message-ID: <200811172032.30898.freenet@peterjoosten.nl> On Monday 17 November 2008 20:27:13 Peter J. wrote: > On Saturday 15 November 2008 18:37:20 Matthew Toseland wrote: > > Correct. This should go away after 1178 is mandatory on Sunday, provided > > you restart your node at that point. However, the trend so far suggests > > that it won't go away and is still present. :< In any case we need to be > > told if it happens after Sunday. > > > > Ok Matthew, > > Seems to be still there even with version 1179. > > 11 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: > 70.72.215.120:40858 > 212.202.31.3:43592 > 217.196.213.98:24330 > 88.175.66.28:52590 > 87.179.226.176:50173 > 217.153.12.122:50554 > 212.75.37.89:53150 > 85.229.124.96:13598 > 96.250.239.134:64676 > 86.54.216.133:53061 > 79.202.89.5:39002 > > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or > mailto:support-request at freenetproject.org?subject=unsubscribe Also, node uptime is 3 hours now. From bbackde at googlemail.com Mon Nov 17 19:53:22 2008 From: bbackde at googlemail.com (bbackde at googlemail.com) Date: Mon, 17 Nov 2008 20:53:22 +0100 Subject: [freenet-support] Version 1179? In-Reply-To: <4921214D.5020909@WhenGendarmeSleeps.org> References: <49212078.9000608@WhenGendarmeSleeps.org> <4921214D.5020909@WhenGendarmeSleeps.org> Message-ID: Ok, thanks for your answer... update.CMD now downloaded 1178 (said it was a new version, but I had 1178 before) and since then update.CMD thinks I'm current enough. Still no online update offering. I keep waiting, maybe it works when 1180 is there... On Mon, Nov 17, 2008 at 08:46, Volodya wrote: > Volodya wrote: >> bbackde at googlemail.com wrote: >>> Many of my peers seem to run 1179 since this morning. I got no notice >>> about this version via mailing list, >>> and my node (1178) doesn't offer me this new version for update. >>> Is something broken? update.cmd also doesn't work, see my previous >>> mail that was completely ignored ^^ >>> >> >> Same here. > > Sorry, just tried ./update.sh again, and it worked. > > -- > http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast > http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal > http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut > > "None of us are free until all of us are free." ~ Mihail Bakunin > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________ From bbackde at googlemail.com Mon Nov 17 19:55:25 2008 From: bbackde at googlemail.com (bbackde at googlemail.com) Date: Mon, 17 Nov 2008 20:55:25 +0100 Subject: [freenet-support] Version 1179? In-Reply-To: <4921214D.5020909@WhenGendarmeSleeps.org> References: <49212078.9000608@WhenGendarmeSleeps.org> <4921214D.5020909@WhenGendarmeSleeps.org> Message-ID: Another thing: anyone also noticed that starting with 1178 freesites like the Frost freesite or Toads blog are not longer retrievable? I get a temporary files error ... maybe this is already fixed with 1179. On Mon, Nov 17, 2008 at 08:46, Volodya wrote: > Volodya wrote: >> bbackde at googlemail.com wrote: >>> Many of my peers seem to run 1179 since this morning. I got no notice >>> about this version via mailing list, >>> and my node (1178) doesn't offer me this new version for update. >>> Is something broken? update.cmd also doesn't work, see my previous >>> mail that was completely ignored ^^ >>> >> >> Same here. > > Sorry, just tried ./update.sh again, and it worked. > > -- > http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast > http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal > http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut > > "None of us are free until all of us are free." ~ Mihail Bakunin > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________ From freenet at peterjoosten.nl Mon Nov 17 20:04:04 2008 From: freenet at peterjoosten.nl (Peter J.) Date: Mon, 17 Nov 2008 21:04:04 +0100 Subject: [freenet-support] Version 1179? In-Reply-To: References: <4921214D.5020909@WhenGendarmeSleeps.org> Message-ID: <200811172104.04379.freenet@peterjoosten.nl> On Monday 17 November 2008 20:55:25 bbackde at googlemail.com wrote: > Another thing: anyone also noticed that starting with 1178 freesites > like the Frost freesite or Toads blog are not longer retrievable? > I get a temporary files error ... maybe this is already fixed with 1179. > Yes had that also with 1178 but with 1179 these errors are gone. From ukoepping at yahoo.de Mon Nov 17 20:33:32 2008 From: ukoepping at yahoo.de (Ulrich Koepping) Date: Mon, 17 Nov 2008 20:33:32 +0000 (GMT) Subject: [freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads Message-ID: <108966.50573.qm@web24005.mail.ird.yahoo.com> 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. From bbackde at googlemail.com Mon Nov 17 20:42:22 2008 From: bbackde at googlemail.com (bbackde at googlemail.com) Date: Mon, 17 Nov 2008 21:42:22 +0100 Subject: [freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads In-Reply-To: <108966.50573.qm@web24005.mail.ird.yahoo.com> References: <108966.50573.qm@web24005.mail.ird.yahoo.com> Message-ID: This seems to be fixed with 1179 (this is the latest version) but for some reason we get no online update and update.cmd doesn't work for me. Others reported that update.sh works on Linux... On Mon, Nov 17, 2008 at 21:33, Ulrich Koepping wrote: > 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 at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________ From dennisn at dennisn.dyndns.org Mon Nov 17 20:54:10 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Mon, 17 Nov 2008 15:54:10 -0500 Subject: [freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads In-Reply-To: References: <108966.50573.qm@web24005.mail.ird.yahoo.com> Message-ID: <20081117155410.48bf467c.dennisn@dennisn.dyndns.org> On Mon, 17 Nov 2008 21:42:22 +0100, bbackde at googlemail.com wrote: > This seems to be fixed with 1179 (this is the latest version) but for > some reason we get no online update > and update.cmd doesn't work for me. Others reported that update.sh > works on Linux... Are you sure? From what I'm hearing in the IRC channel (freenode, #freenet), I think it's still out there, and a tricky bug to debug--for example I haven't been able to reproduce the errors. Others found that disabling logging fixed/reduced the problem, while logging minor errors made it more prevalent--but upon closer inspection, I think that turned out to be wishful thinking. I think they're waiting to fix this, and other serious problems, before pushing out another release :/. From bbackde at googlemail.com Mon Nov 17 20:59:20 2008 From: bbackde at googlemail.com (bbackde at googlemail.com) Date: Mon, 17 Nov 2008 21:59:20 +0100 Subject: [freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads In-Reply-To: <20081117155410.48bf467c.dennisn@dennisn.dyndns.org> References: <108966.50573.qm@web24005.mail.ird.yahoo.com> <20081117155410.48bf467c.dennisn@dennisn.dyndns.org> Message-ID: Of course I'm not sure, I'm not even able to get 1179 ^^ I referred to the mail from Peter J. in the "Version 1179?" thread. He said the temporary files bug could be fixed. On Mon, Nov 17, 2008 at 21:54, Dennis Nezic wrote: > On Mon, 17 Nov 2008 21:42:22 +0100, bbackde at googlemail.com wrote: > >> This seems to be fixed with 1179 (this is the latest version) but for >> some reason we get no online update >> and update.cmd doesn't work for me. Others reported that update.sh >> works on Linux... > > Are you sure? From what I'm hearing in the IRC channel (freenode, > #freenet), I think it's still out there, and a tricky bug to debug--for > example I haven't been able to reproduce the errors. Others found that > disabling logging fixed/reduced the problem, while logging minor errors > made it more prevalent--but upon closer inspection, I think that turned > out to be wishful thinking. I think they're waiting to fix this, and > other serious problems, before pushing out another release :/. > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________ From dennisn at dennisn.dyndns.org Mon Nov 17 21:08:23 2008 From: dennisn at dennisn.dyndns.org (Dennis Nezic) Date: Mon, 17 Nov 2008 16:08:23 -0500 Subject: [freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads In-Reply-To: References: <108966.50573.qm@web24005.mail.ird.yahoo.com> <20081117155410.48bf467c.dennisn@dennisn.dyndns.org> Message-ID: <20081117160823.9776a545.dennisn@dennisn.dyndns.org> On Mon, 17 Nov 2008 21:59:20 +0100, bbackde at googlemail.com wrote: > Of course I'm not sure, I'm not even able to get 1179 ^^ You should be able to download the snapshot jar from http://downloads.freenetproject.org/alpha/ ... 1179 = r23606, and replace the one you're currently using. From luke771 at gmail.com Tue Nov 18 12:26:01 2008 From: luke771 at gmail.com (Luke771) Date: Tue, 18 Nov 2008 13:26:01 +0100 Subject: [freenet-support] (no subject) In-Reply-To: <650097.5478.qm@web28613.mail.ukl.yahoo.com> References: <650097.5478.qm@web28613.mail.ukl.yahoo.com> Message-ID: <20081118132601.44fd0792.luke771@gmail.com> On Sat, 15 Nov 2008 23:42:11 +0000 (GMT) Markus Hahn wrote: Sorry if I explain things that you know already, but I don't know what your general competence level is, so I'll assume you know very little, just in case (and it may be useful for someone else, too) > I am able to reach and open some of the sites I want to, but frequently I get the message that a site seems to be unreachable, sometimes concerning a site that opens some minutes later. This is expected on a newly estabilshed node. The first thing to do to get a new node to work better is to set the max store size and max memory usage (both in your config page at http://localhost:8888/config). But first lets talk about uptime quickly: Freenet needs to sun as much as possible. The optimal would be to let it run 24/7, but morning to night every day is also fairly good. What you DON'T want to do is 'start freenet - visit freesite - shut down freenet'. It won't work. Freesites will take ages to load (when they do) and you'll be damaging the netwrotk. Let freenet run as much as your computer runs, and if you don't have an always-up box, consider letting your computer run just for the sake of freenet. the more Freenet stays up, the better your node will work, and themore it will help the network. Back to configuration; as we said, you should set store size and max memory usage to higher values than the defaults. You may have done that when you went through the Freenet First.time Wizard, but if you kept the defaults your store size and memory usage are very low because the defaults must work for everyone including users running on a junkware boxes in countries where they don't consider 700MhZ and 256MB RAM a low-end machine. The values are different according to your box and the usage you make of it, but the rule of is 'the more the better'. See how much HDD space you can dedicate to Freenet and set your store size to that; some have dedicated Freenet disks 500GB or 1TB in size, others have 250+ GB freenet stores, but 50GB is already fairly good. Remember than the bigger the store the better your node will work, because more stuff will be cached (encrypted) locally and will be fetched way more quickly when request it. As for max memory usage, you can set this even higher than can afford in theory, becuse freenet won't allocate all the memory you give to it. High max mem values are needed in my experience because mem usage will peak sometimes and if it tries to use more memory than it's allowed to use, the node may crash. Those who operate machnes with 3 or more GB of RAM are known to set max memory usage up to 2GB. My node runs on box that only has 1GB of RAM, Freenet is set to use max 770MB of it, and the node works pretty well. I used to run nodes on virtual machines with max memory usage set to 256MB and they worked pretty well as long as I didn't queue too many or too large files for download/upload; therefore, if you are limited by the physical memory installed on your box, (for instance you can't set max mem. usage to anything higher than 256 or even 128MB) you will have to run few downloads/uploads at a time (wait for them to complete, then add more). Remember it's not the number of files, it's the total size. Bandwidth usage settings are kind of relative. If you have a good connection (10MB+ high upload BW) you can set your bandwidth usage as high as your total bandwidth and freenet will never use but a fraction of that, but if your connection is medium-low, you'll need to limit freenet BW usage. In my experience trying to help new users get started, I've seen that the difference between upload and download bandwidth may be a problem. ISP' tout "high speed connections" without ever mentioning anything about upload bandwidth. As an example, a connection that the ISP refers to as '12Mbit/s' never does what the ISP says it should: first of all 12MB/s (1.5MB/s) is a nominal value, the actual bandwidth rarely exceeds 2/3 of the nominal value stated by ISP (more often half of it), and most importnat, the higghly publicized 12Mbit/s is only the download bandwidth. They never say anything about upload speed. If you're lucky you have 2Mbit/s but ,more often 1Mbit/s fot 'high speed' connections and 512 or 256 Kbit/s for medium range connections. So, the point is, find out what your -upload- stream in KB/s is (find out what your ISP say your upstream is, then divide by 8 to get bytes; ISP's always talk about bits). Decide how much bandwidth you can afford to give freenet in upload and set that value under max bandwidth usage in config page. As for download bandwidth you may want to keep the defult -1, meaning 4x the upstream. If you are one of the few lucky that have high upload bandwidths (as high as download), you may want to set the same value for both upload and download. > I am totally new in this subject and all my real-world-friends are no-techies and no-nerds, so I still have no "firends" in the sense of trustworthy nodes to connect with or in the sense of darknet-members. Might this be the reason why some sites are closed for me? No. If you don't know anyone who runs Freenet, you just run Opennet (strangers) without adding anyone to your Daknet (friends). Freenet will work just as fine. > Should I try to manipulate the router in order to "forward" Yes you should. You can already access the router's web interface; now the point is how to configure a forward. Interfaces are different for different routers but they're all pretty straightforward if you know what you need to do, and in your case what you need to do is: FORWARD: FROM: TO: FOR PROTOCOL: udp only FORWARD: FROM: TO: FOR PROTOCOL: udp only yes, it's two ports, one for darknet (friends) and one for opennet (strangers). The port numbers of the ports you have to forwards are listed at the bottom of your Friends page, under 'ports used by the node', marked 'you may want to forward this port'. >or should I turn off the firewall? If for firewall you mean one of those annoying software firewalls that are so popular among windows users, that ask you whether to allow a program to connect and/or recieve connections, you want to allow Freenet to both connect to the internet and receive connections from the internet (some fiorewalls call the latter "act as a server") Observe that at least on some firewalls, you'll need to allow Java to make/recieve connections and not Freenet itself. (I think the executable that needs the permissions is javaw.exe but I'm not 100% sure, you may want to double check that) If you use the kind of firewall that simply open closes ports, you want to: ALLOW , DIRECTION: both PROTOCOL: udp > Or is freenet running properly and the seemingly closed doors seem so due to the restrictions a newbie in darknet with a fresh node has to come around with? Freenet seems to be running fine. It should work even without port forwarding nut it would be -MUCH- better if you do configure the port forwarding. From toad at amphibian.dyndns.org Tue Nov 18 12:26:17 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Tue, 18 Nov 2008 12:26:17 +0000 Subject: [freenet-support] Wrapper does not start In-Reply-To: <32350958.1226711522489.JavaMail.root@viefep13> References: <32350958.1226711522489.JavaMail.root@viefep13> Message-ID: <200811181226.17675.toad@amphibian.dyndns.org> On Saturday 15 November 2008 01:12, freenet at chello.at wrote: > ---- Matthew Toseland schrieb: > > On Friday 14 November 2008 01:09, freenet at chello.at wrote: > > > Since last update on 13.11. Freenet fails to start. > > > I get the following Message in wrapper.log: > > > > You let freenet auto-update itself, or you used update.sh/update.cmd? > > I used update.cmd > > > If you let Freenet auto-update itself, then please send me your wrapper.log, > > as this is a serious bug we've been trying to gather more info on ... > > > > You can get your node back by running update.sh/update.cmd. > > I did it, but then the same error happens again. :( > Is there no "rollback" for updates? Please try again. I apologise for the long turnaround. If it still doesn't work then send me a directory listing (ls -l / dir /w), a copy of wrapper.conf, and the output of the update script. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081118/8f1b9841/attachment.pgp From toad at amphibian.dyndns.org Tue Nov 18 12:45:30 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Tue, 18 Nov 2008 12:45:30 +0000 Subject: [freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads In-Reply-To: <20081117160823.9776a545.dennisn@dennisn.dyndns.org> References: <108966.50573.qm@web24005.mail.ird.yahoo.com> <20081117160823.9776a545.dennisn@dennisn.dyndns.org> Message-ID: <200811181245.40299.toad@amphibian.dyndns.org> On Monday 17 November 2008 21:08, Dennis Nezic wrote: > On Mon, 17 Nov 2008 21:59:20 +0100, bbackde at googlemail.com wrote: > > > Of course I'm not sure, I'm not even able to get 1179 ^^ > > You should be able to download the snapshot jar from > http://downloads.freenetproject.org/alpha/ ... 1179 = r23606, and > replace the one you're currently using. AFAIK 1179 doesn't do anything that could fix this. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081118/b2f286bc/attachment.pgp From toad at amphibian.dyndns.org Tue Nov 18 12:52:26 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Tue, 18 Nov 2008 12:52:26 +0000 Subject: [freenet-support] (no subject) In-Reply-To: <20081118132601.44fd0792.luke771@gmail.com> References: <650097.5478.qm@web28613.mail.ukl.yahoo.com> <20081118132601.44fd0792.luke771@gmail.com> Message-ID: <200811181252.27533.toad@amphibian.dyndns.org> Please, when replying to newbies, CC them, because they're often not subscribed to the list. I've bounced your message to the poster. On Tuesday 18 November 2008 12:26, Luke771 wrote: > On Sat, 15 Nov 2008 23:42:11 +0000 (GMT) > Markus Hahn wrote: > > > > > Sorry if I explain things that you know already, but I don't know what your general competence level is, so I'll assume you know very little, just in case (and it may be useful for someone else, too) > > > I am able to reach and open some of the sites I want to, but frequently I get the message that a site seems to be unreachable, sometimes concerning a site that opens some minutes later. > > This is expected on a newly estabilshed node. The first thing to do to get a new node to work better is to set the max store size and max memory usage (both in your config page at http://localhost:8888/config). > > But first lets talk about uptime quickly: Freenet needs to sun as much as possible. The optimal would be to let it run 24/7, but morning to night every day is also fairly good. What you DON'T want to do is 'start freenet - visit freesite - shut down freenet'. It won't work. Freesites will take ages to load (when they do) and you'll be damaging the netwrotk. Let freenet run as much as your computer runs, and if you don't have an always-up box, consider letting your computer run just for the sake of freenet. the more Freenet stays up, the better your node will work, and themore it will help the network. > > > Back to configuration; as we said, you should set store size and max memory usage to higher values than the defaults. > You may have done that when you went through the Freenet First.time Wizard, but if you kept the defaults your store size and memory usage are very low because the defaults must work for everyone including users running on a junkware boxes in countries where they don't consider 700MhZ and 256MB RAM a low-end machine. > > The values are different according to your box and the usage you make of it, but the rule of is 'the more the better'. See how much HDD space you can dedicate to Freenet and set your store size to that; some have dedicated Freenet disks 500GB or 1TB in size, others have 250+ GB freenet stores, but 50GB is already fairly good. Remember than the bigger the store the better your node will work, because more stuff will be cached (encrypted) locally and will be fetched way more quickly when request it. > > As for max memory usage, you can set this even higher than can afford in theory, becuse freenet won't allocate all the memory you give to it. High max mem values are needed in my experience because mem usage will peak sometimes and if it tries to use more memory than it's allowed to use, the node may crash. > Those who operate machnes with 3 or more GB of RAM are known to set max memory usage up to 2GB. > My node runs on box that only has 1GB of RAM, Freenet is set to use max 770MB of it, and the node works pretty well. > > I used to run nodes on virtual machines with max memory usage set to 256MB and they worked pretty well as long as I didn't queue too many or too large files for download/upload; therefore, if you are limited by the physical memory installed on your box, (for instance you can't set max mem. usage to anything higher than 256 or even 128MB) you will have to run few downloads/uploads at a time (wait for them to complete, then add more). Remember it's not the number of files, it's the total size. > > Bandwidth usage settings are kind of relative. If you have a good connection (10MB+ high upload BW) you can set your bandwidth usage as high as your total bandwidth and freenet will never use but a fraction of that, but if your connection is medium-low, you'll need to limit freenet BW usage. In my experience trying to help new users get started, I've seen that the difference between upload and download bandwidth may be a problem. ISP' tout "high speed connections" without ever mentioning anything about upload bandwidth. > > As an example, a connection that the ISP refers to as '12Mbit/s' never does what the ISP says it should: first of all 12MB/s (1.5MB/s) is a nominal value, the actual bandwidth rarely exceeds 2/3 of the nominal value stated by ISP (more often half of it), and most importnat, the higghly publicized 12Mbit/s is only the download bandwidth. They never say anything about upload speed. If you're lucky you have 2Mbit/s but ,more often 1Mbit/s fot 'high speed' connections and 512 or 256 Kbit/s for medium range connections. > > So, the point is, find out what your -upload- stream in KB/s is (find out what your ISP say your upstream is, then divide by 8 to get bytes; ISP's always talk about bits). Decide how much bandwidth you can afford to give freenet in upload and set that value under max bandwidth usage in config page. As for download bandwidth you may want to keep the defult -1, meaning 4x the upstream. If you are one of the few lucky that have high upload bandwidths (as high as download), you may want to set the same value for both upload and download. > > > > I am totally new in this subject and all my real-world-friends are no-techies and no-nerds, so I still have no "firends" in the sense of trustworthy nodes to connect with or in the sense of darknet-members. Might this be the reason why some sites are closed for me? > > No. If you don't know anyone who runs Freenet, you just run Opennet (strangers) without adding anyone to your Daknet (friends). Freenet will work just as fine. > > > Should I try to manipulate the router in order to "forward" > > Yes you should. You can already access the router's web interface; now the point is how to configure a forward. > Interfaces are different for different routers but they're all pretty straightforward if you know what you need to do, and in your case what you need to do is: > > FORWARD: FROM: TO: FOR PROTOCOL: udp only > FORWARD: FROM: TO: FOR PROTOCOL: udp only > > yes, it's two ports, one for darknet (friends) and one for opennet (strangers). The port numbers of the ports you have to forwards are listed at the bottom of your Friends page, under 'ports used by the node', marked 'you may want to forward this port'. > > >or should I turn off the firewall? > > If for firewall you mean one of those annoying software firewalls that are so popular among windows users, that ask you whether to allow a program to connect and/or recieve connections, you want to allow Freenet to both connect to the internet and receive connections from the internet (some fiorewalls call the latter "act as a server") > > Observe that at least on some firewalls, you'll need to allow Java to make/recieve connections and not Freenet itself. (I think the executable that needs the permissions is javaw.exe but I'm not 100% sure, you may want to double check that) > > If you use the kind of firewall that simply open closes ports, you want to: > ALLOW , DIRECTION: both PROTOCOL: udp > > > Or is freenet running properly and the seemingly closed doors seem so due to the restrictions a newbie in darknet with a fresh node has to come around with? > > Freenet seems to be running fine. It should work even without port forwarding nut it would be -MUCH- better if you do configure the port forwarding. > > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081118/4a69305b/attachment.pgp From toad at amphibian.dyndns.org Tue Nov 18 12:54:49 2008 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Tue, 18 Nov 2008 12:54:49 +0000 Subject: [freenet-support] Wrapper does not start In-Reply-To: <22182787.1226859168678.JavaMail.root@viefep13> References: <22182787.1226859168678.JavaMail.root@viefep13> Message-ID: <200811181254.49827.toad@amphibian.dyndns.org> On Sunday 16 November 2008 18:12, freenet at chello.at wrote: > Since I updated to 1179, it works again. > No problems with up- and downloads or freesites. Good luck. AFAIK nothing changed in 1179 that could possibly have fixed that bug. Also some people are still getting it. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/support/attachments/20081118/9bbbf299/attachment.pgp From bqz69 at telia.com Tue Nov 18 13:33:57 2008 From: bqz69 at telia.com (bqz69) Date: Tue, 18 Nov 2008 14:33:57 +0100 Subject: [freenet-support] (no subject) In-Reply-To: <20081118132601.44fd0792.luke771@gmail.com> References: <650097.5478.qm@web28613.mail.ukl.yahoo.com> <20081118132601.44fd0792.luke771@gmail.com> Message-ID: <200811181433.58073.bqz69@telia.com> On Tuesday 18 November 2008 13.26.01 Luke771 wrote: > On Sat, 15 Nov 2008 23:42:11 +0000 (GMT) > Markus Hahn wrote: > > > > > Sorry if I explain things that you know already, but I don't know what your > general competence level is, so I'll assume you know very little, just in > case (and it may be useful for someone else, too) > > > I am able to reach and open some of the sites I want to, but frequently I > > get the message that a site seems to be unreachable, sometimes concerning > > a site that opens some minutes later. > > This is expected on a newly estabilshed node. The first thing to do to get > a new node to work better is to set the max store size and max memory usage > (both in your config page at http://localhost:8888/config). > > But first lets talk about uptime quickly: Freenet needs to sun as much as ++++++++++ I like your answer, that's the way a lot more stuff of the internet should be explained (better more than less details), in order for ordinary people to learn. Thanks - *smile* (I am the author of www.minihowto.org, and I have tried to make documentation along your "lines" - it's not very easy?)