[freenet-support] compile error FMS
Hi, I try to compile FMS 0.3.57on OSX 10.6.6 and I get this error: Linking CXX executable fms Undefined symbols: "_libiconv_close", referenced from: CharsetConverter::~CharsetConverter()in charsetconverter.o CharsetConverter::~CharsetConverter()in charsetconverter.o CharsetConverter::SetConversion(std::basic_string, std::allocator > const&, std::basic_string, std::allocator > const&)in charsetconverter.o "_libiconv", referenced from: CharsetConverter::Convert(std::basic_string, std::allocator > const&, std::basic_string, std::allocator >&)in charsetconverter.o "_libiconv_open", referenced from: CharsetConverter::SetConversion(std::basic_string, std::allocator > const&, std::basic_string, std::allocator > const&)in charsetconverter.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [fms] Error 1 make[1]: *** [CMakeFiles/fms.dir/all] Error 2 make: *** [all] Error 2 How do I fix this? Or can I get it somewere prebuild? Jelbert ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Call for seednodes and explanation of current problems
On Sat, Feb 5, 2011 at 9:12 PM, artur wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > how much (extra) bandwidth is needed for a seed node? > > My connection has a static IP and my Server is up 24/7 without any > forced 24h disconnects... > > But I can't spend all the bandwidth for freenet. That’s why I would like > to know how much extra traffic is generated through being a seednode. > > > artur Well, the bandwidth would just be taken from uploads Freenet would otherwise be doing, so entirely up to you what you set it to. Note - unless you are inserting a lot of files into Freenet you won't notice the bandwidth being diverted to seednode activity. I would suggest a node with at least 50KiB (.4 Mbps) upload setting. However, the more seednodes there are the less traffic each individual seednode has to handle. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Call for seednodes and explanation of current problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, how much (extra) bandwidth is needed for a seed node? My connection has a static IP and my Server is up 24/7 without any forced 24h disconnects... But I can't spend all the bandwidth for freenet. That’s why I would like to know how much extra traffic is generated through being a seednode. artur Am 05.02.2011 19:39, schrieb Matthew Toseland: > We need more seednodes. I will explain the broader situation below. If you > can run a seednode - which means you need a forwarded port, a reasonably > static IP address (or dyndns name), and a reasonable amount of bandwidth > (especially upstream), and a reasonably stable node, please send me your > opennet noderef (from the strangers page in advanced mode), and enable "Be a > seednode" in the advanced config. Thanks. > > Details: > > One of the problems Freenet has at the moment is that bootstrapping a new > node can take an awfully long time - 20 minutes or more sometimes. It is not > clear why; we seem to either get rejected by seednodes (most of the time), or > they return nothing, maybe a few "not wanted" notices, or they return lots of > noderefs and we manage to announce. > > This might be due to bugs. 1343 fixed a bug that apparently badly affected > some seednodes. However it appears most seednodes have upgraded now. > > There doesn't seem to be a problem with losing connections - backoff yes but > once a node is connected it seems to mostly stay connected. > > The most likely answer seems to be that we just don't have enough seednodes > to cope with the load. > > It is also possible that this is due to an attack. It did come on relatively > suddenly a few weeks ago (it was bad before but it got much worse), and it > seems to have got significantly worse in the last week. It is not clear how > we would identify an attack if that was the problem; there are no obvious > signs so far. > > It is also possible it is a client-side bug. Testing of the master branch > would be useful, it has some small changes. > > > > ___ > Devl mailing list > d...@freenetproject.org > http://freenetproject.org/cgi-bin/mailman/listinfo/devl -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNTgOIAAoJEMCbH/uYbXaWiOsH/jLbeh7EnDL6gSq0BDwi/tcE Yl6NFZkSYwmakgQc0csneqvf7KnNhXP3ZbmQsh3beEd2CRn1zIdTbAeeh+e3Dyf9 pYqLK6ZaZs5vRSaV5Aj2f+TXF4zgCudExpv1crCq6kbXiqTvcdiOqN4MXsXphagS 4kM+UYzocXXzrPlwZ5uzQDJ303LOu5KmC/pjqfCa9ufiqX3Psmm/xetJQo5Z7+6f +0rCnjUfeKzA5YCWe0QpKyVvlNqre5GvXBJiDC1V/3xm5lnK0kV+DX2GgI51OPoB K2hJWRNh14w91rH1x3RaZOF83fF8EsPXNmtQWPr9rOI+nMYctUBuKRsDE1m2xh8= =OH/L -END 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Run problem
Hi I have just installed Freenet but encounter problems when I try to run. PLease see error reports attached Could this be a firewall problem? Or could there be another problem? Thanks & Rgds Peter -- next part -- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/support/attachments/20110205/b18439d6/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: Freenet Launcher error.JPG Type: image/jpeg Size: 16715 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20110205/b18439d6/attachment.jpe> -- next part -- A non-text attachment was scrubbed... Name: The Freenet Wrapper error.JPG Type: image/jpeg Size: 15036 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20110205/b18439d6/attachment-0001.jpe>
[freenet-support] Freenet 0.7.5 build 1343 and 1344
Freenet 0.7.5 build 1344 is out. Please upgrade, it will be mandatory on Monday, and contains some important fixes to announcement and the low level code: - Fix a race condition in sending packets, which may or may not have caused serious problems. - Boost the priority of noderef transfers in both announcements and path folding. - Prevent local announcements from being routed back to the announcer. - Indicate in the logs when our announcements are rejected by the seednode. Please upgrade! Thanks. You may want to upgrade manually if your node is having big problems, using the update.sh or update.cmd script (there is an option in the system tray in Windows). Note that this is visible to the outside world as it contacts our servers. You should definitely do this if you run a seed node. Please report whatever problems you run into. Unfortunately Freenet continues to have major problems, particularly with announcement / bootstrapping a new node, which may or may not be fixed by the above... signature.asc Description: This is a digitally signed message part. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Call for seednodes and explanation of current problems
We need more seednodes. I will explain the broader situation below. If you can run a seednode - which means you need a forwarded port, a reasonably static IP address (or dyndns name), and a reasonable amount of bandwidth (especially upstream), and a reasonably stable node, please send me your opennet noderef (from the strangers page in advanced mode), and enable "Be a seednode" in the advanced config. Thanks. Details: One of the problems Freenet has at the moment is that bootstrapping a new node can take an awfully long time - 20 minutes or more sometimes. It is not clear why; we seem to either get rejected by seednodes (most of the time), or they return nothing, maybe a few "not wanted" notices, or they return lots of noderefs and we manage to announce. This might be due to bugs. 1343 fixed a bug that apparently badly affected some seednodes. However it appears most seednodes have upgraded now. There doesn't seem to be a problem with losing connections - backoff yes but once a node is connected it seems to mostly stay connected. The most likely answer seems to be that we just don't have enough seednodes to cope with the load. It is also possible that this is due to an attack. It did come on relatively suddenly a few weeks ago (it was bad before but it got much worse), and it seems to have got significantly worse in the last week. It is not clear how we would identify an attack if that was the problem; there are no obvious signs so far. It is also possible it is a client-side bug. Testing of the master branch would be useful, it has some small changes. signature.asc Description: This is a digitally signed message part. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe