[freenet-support] Freenet 0.7 build 1186
Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory on Tuesday. Changes: - Fix a nasty race condition in the message handling code. Impact is uncertain but could be large - it broke an update-over-mandatory between nodes on the same computer in testing. - Implement (long overdue) update over mandatory for freenet-ext.jar. Normally this will fetch both the main jar and the ext jar at the same time, if the node is too old to update over Freenet, or if it takes more than 3 hours to update. - Include the earliest compatible version of freenet-ext.jar in the manifest for the main jar. We will use this to ensure compatibility when updating in a near future build. - Limit the size of the auto-detected datastore size to 256GB. This will ensure the Bloom filter is of a reasonable size (128MB at most), and avoid some crazy situations. Don't limit the Bloom filter size to 256MB any more, defaults to 1/2048th of the size of the store up to 2GB filter. - Make the datastore size default to 100MB. The first-time wizard will configure it to a larger size, but the resize will occur online, and this gains us a few seconds on the first startup by not having to wait so long for preallocating it. - Minor change to plugin loading and a minor bugfix to connection setup. Please upgrade! If you find any bugs, please report them on the bug tracker. The "not acknowledging packets even after 10 minutes" bug is sadly still with us, it will be fixed soon. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081129/2daaf22e/attachment.pgp>
[freenet-support] Newbie to 0.7
On Saturday 29 November 2008 08:38, Level 13 wrote: > I've installed 0.7 yesterday (finally :) but I'm not getting rid of > 0.5 just yet). I like the fact that it's not eating that much of the > computer resources as 0.5 (but then again, I've pretty much kept the > restrictive default settings about the memory and such). Welcome! And thanks. > > Now, to my questions... After one day, it still says: > UDP Darknet port X Status unknown > UDP Opennet port X Maybe port forwarded > Why is this so? Both ports ARE port-forwarded, whereas the Darknet is > not used yet (since I have "no friends" in a manner of speaking). > However, an occasional packet to one of the ports is filtered every > now and then, on either hardware firewall or the personal/software > firewall (I hear it's because UDP packets tend to have problems with > firewalls - or vice versa...). Other than that, browsing seems to work > fine. It is nontrivial to detect whether a port is forwarded or not, especially as some symmetric firewalls etc have long timeouts. W.r.t. dropped packets ... if you have a low MTU and a firewall that drops fragmented packets, this can be bad for Freenet. What is your MTU? > > Where is the setting for maximum number of connections the whole thing > is allowed to maintain (which was pretty obvious in 0.5)? Is it the > "Maximum number of Opennet peers", which is 20 at max? If so, how come > only 20 is the upper limit? 20 is indeed the upper limit at the moment. More is not always better. Darknet nodes are unlikely to have more than 20, this was part of the thinking. > > About accessing the node from elsewhere in the LAN -- isn't this > configured in the "Hostnames or IP addresses that are allowed to > connect to FProxy"? Because I put an internal IP of another computer > in my LAN there, but I can't access the site from it. You need to set the addresses to listen on as well. > > As for these two... > "Directories downloading is allowed to" > "Directories uploading is allowed to" > ...if I understand this correctly, putting the string "downloads" > there will use the path defined in "Default download directory" > setting (where e.g. I have "x:\download07" (without the quotes) -- is > this correct)? > What's the deal with "If this is set to "all" any user can download > any file to anywhere on your computer!" -- does it actually mean that > anyone who connects to my node will be able to read just about ANY > file on the system? Any user who has access to FCP. > > Oh, and BTW, I got this status message even after the auto-update to > the latest version: > > 12 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: > (12 IPs listed here). Known problem, sorry... will release a build at some point in the near future which we believe fixes it, at which point we will need to know if it hasn't been fixed. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081129/a1919e59/attachment.pgp>
[freenet-support] Newbie to 0.7
I've installed 0.7 yesterday (finally :) but I'm not getting rid of 0.5 just yet). I like the fact that it's not eating that much of the computer resources as 0.5 (but then again, I've pretty much kept the restrictive default settings about the memory and such). Now, to my questions... After one day, it still says: UDP Darknet port X Status unknown UDP Opennet port X Maybe port forwarded Why is this so? Both ports ARE port-forwarded, whereas the Darknet is not used yet (since I have "no friends" in a manner of speaking). However, an occasional packet to one of the ports is filtered every now and then, on either hardware firewall or the personal/software firewall (I hear it's because UDP packets tend to have problems with firewalls - or vice versa...). Other than that, browsing seems to work fine. Where is the setting for maximum number of connections the whole thing is allowed to maintain (which was pretty obvious in 0.5)? Is it the "Maximum number of Opennet peers", which is 20 at max? If so, how come only 20 is the upper limit? About accessing the node from elsewhere in the LAN -- isn't this configured in the "Hostnames or IP addresses that are allowed to connect to FProxy"? Because I put an internal IP of another computer in my LAN there, but I can't access the site from it. As for these two... "Directories downloading is allowed to" "Directories uploading is allowed to" ...if I understand this correctly, putting the string "downloads" there will use the path defined in "Default download directory" setting (where e.g. I have "x:\download07" (without the quotes) -- is this correct)? What's the deal with "If this is set to "all" any user can download any file to anywhere on your computer!" -- does it actually mean that anyone who connects to my node will be able to read just about ANY file on the system? Oh, and BTW, I got this status message even after the auto-update to the latest version: 12 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: (12 IPs listed here).
[freenet-support] Newbie to 0.7
I've installed 0.7 yesterday (finally :) but I'm not getting rid of 0.5 just yet). I like the fact that it's not eating that much of the computer resources as 0.5 (but then again, I've pretty much kept the restrictive default settings about the memory and such). Now, to my questions... After one day, it still says: UDP Darknet port X Status unknown UDP Opennet port X Maybe port forwarded Why is this so? Both ports ARE port-forwarded, whereas the Darknet is not used yet (since I have no friends in a manner of speaking). However, an occasional packet to one of the ports is filtered every now and then, on either hardware firewall or the personal/software firewall (I hear it's because UDP packets tend to have problems with firewalls - or vice versa...). Other than that, browsing seems to work fine. Where is the setting for maximum number of connections the whole thing is allowed to maintain (which was pretty obvious in 0.5)? Is it the Maximum number of Opennet peers, which is 20 at max? If so, how come only 20 is the upper limit? About accessing the node from elsewhere in the LAN -- isn't this configured in the Hostnames or IP addresses that are allowed to connect to FProxy? Because I put an internal IP of another computer in my LAN there, but I can't access the site from it. As for these two... Directories downloading is allowed to Directories uploading is allowed to ...if I understand this correctly, putting the string downloads there will use the path defined in Default download directory setting (where e.g. I have x:\download07 (without the quotes) -- is this correct)? What's the deal with If this is set to all any user can download any file to anywhere on your computer! -- does it actually mean that anyone who connects to my node will be able to read just about ANY file on the system? Oh, and BTW, I got this status message even after the auto-update to the latest version: 12 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: (12 IPs listed here). ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Newbie to 0.7
On Saturday 29 November 2008 08:38, Level 13 wrote: I've installed 0.7 yesterday (finally :) but I'm not getting rid of 0.5 just yet). I like the fact that it's not eating that much of the computer resources as 0.5 (but then again, I've pretty much kept the restrictive default settings about the memory and such). Welcome! And thanks. Now, to my questions... After one day, it still says: UDP Darknet port X Status unknown UDP Opennet port X Maybe port forwarded Why is this so? Both ports ARE port-forwarded, whereas the Darknet is not used yet (since I have no friends in a manner of speaking). However, an occasional packet to one of the ports is filtered every now and then, on either hardware firewall or the personal/software firewall (I hear it's because UDP packets tend to have problems with firewalls - or vice versa...). Other than that, browsing seems to work fine. It is nontrivial to detect whether a port is forwarded or not, especially as some symmetric firewalls etc have long timeouts. W.r.t. dropped packets ... if you have a low MTU and a firewall that drops fragmented packets, this can be bad for Freenet. What is your MTU? Where is the setting for maximum number of connections the whole thing is allowed to maintain (which was pretty obvious in 0.5)? Is it the Maximum number of Opennet peers, which is 20 at max? If so, how come only 20 is the upper limit? 20 is indeed the upper limit at the moment. More is not always better. Darknet nodes are unlikely to have more than 20, this was part of the thinking. About accessing the node from elsewhere in the LAN -- isn't this configured in the Hostnames or IP addresses that are allowed to connect to FProxy? Because I put an internal IP of another computer in my LAN there, but I can't access the site from it. You need to set the addresses to listen on as well. As for these two... Directories downloading is allowed to Directories uploading is allowed to ...if I understand this correctly, putting the string downloads there will use the path defined in Default download directory setting (where e.g. I have x:\download07 (without the quotes) -- is this correct)? What's the deal with If this is set to all any user can download any file to anywhere on your computer! -- does it actually mean that anyone who connects to my node will be able to read just about ANY file on the system? Any user who has access to FCP. Oh, and BTW, I got this status message even after the auto-update to the latest version: 12 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: (12 IPs listed here). Known problem, sorry... will release a build at some point in the near future which we believe fixes it, at which point we will need to know if it hasn't been fixed. pgpMdaSaZMs6q.pgp Description: PGP signature ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Freenet 0.7 build 1186
Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory on Tuesday. Changes: - Fix a nasty race condition in the message handling code. Impact is uncertain but could be large - it broke an update-over-mandatory between nodes on the same computer in testing. - Implement (long overdue) update over mandatory for freenet-ext.jar. Normally this will fetch both the main jar and the ext jar at the same time, if the node is too old to update over Freenet, or if it takes more than 3 hours to update. - Include the earliest compatible version of freenet-ext.jar in the manifest for the main jar. We will use this to ensure compatibility when updating in a near future build. - Limit the size of the auto-detected datastore size to 256GB. This will ensure the Bloom filter is of a reasonable size (128MB at most), and avoid some crazy situations. Don't limit the Bloom filter size to 256MB any more, defaults to 1/2048th of the size of the store up to 2GB filter. - Make the datastore size default to 100MB. The first-time wizard will configure it to a larger size, but the resize will occur online, and this gains us a few seconds on the first startup by not having to wait so long for preallocating it. - Minor change to plugin loading and a minor bugfix to connection setup. Please upgrade! If you find any bugs, please report them on the bug tracker. The not acknowledging packets even after 10 minutes bug is sadly still with us, it will be fixed soon. pgplBydJowJd5.pgp Description: PGP signature ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Freenet 0.7 build 1187
Freenet 0.7 build 1187 is now available. Mostly minor changes but one was important for newly installed nodes: - Maybe fix darknet peers losing their IP addresses (bug 2688). We were losing IPs on connect and on rekeying (every hour!). - Keep a -1 setting for the Bloom filter size as -1. New nodes start off with a 100MB store (prior to 1186 with a 1GB store). The old behaviour would set the Bloom filter size once to 1/2048th of the store size: 50K, or 500K for pre-1186. Then the post-install wizard would change the store size, but *not* the Bloom filter size, resulting in far more false positives than needed, so far more disk access than needed. - Allow MIME types on redirects in ClientPutComplexDir (useful for some client apps). - Italian update from Luke771, and a couple of explanations improved. pgp19VihLD2Rh.pgp Description: PGP signature ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
