Re: freenet activity
Do you mean preventing other people from accessing the default localhost:? And by that, I guess you mean other local users on your computer? On Wed, 27 Nov 2019 15:14:13 +0100, Momo Roberts wrote: > Hi there. > > Is there a way to secure the freenet Page except using the IP range ? > > greetz > > Momo > > > > Am 27.11.2019 um 14:14 schrieb Arne Babenhauserheide: > > Hi Jelbert, > > > > > > Jelbert Holtrop writes: > > > >> I decided to install freenet again. > >> An article in the newspaper inspired me to look at non oppressed > >> internet solutions. When I look at Enzo’s index I see it has been > >> generated on June 20, 2016, that is a long time ago. Is freenet > >> dead? If so are there other developments of darknet systems? > >> Or if freenet is not dead where did evryone go? > > > > Freenet is not dead, but Enzo’s index no longer updates. > > > > Have a look at some of the other Indexes. > > > > You’ll also find activity in FMS and Sone. > > > > Best wishes, > > Arne > > >
Re: Freenet infinite restart
Can you paste your wrapper.log file, at least the last bits of it where you saw that error message. How much memory do you have in your box? On Tue, 24 Sep 2019 09:54:49 -0400, kobatofu leixi wrote: > I did a fresh install, and it ran fine for a day, until I got > java.langoutofmemory heap space error. And now it has started the > infinite loop again. I deleted that client crypt file and it is still > the same > > On Mon, Sep 23, 2019 at 6:03 PM Krzysztof wrote: > > > Try to delete client.dat.crypt file. It may help. > > > > Regards > > > > On 9/23/19 4:23 AM, kobatofu leixi wrote: > > > Freenet will open and run until > > > "INFO | jvm 1| 2019/09/22 22:12:22 | Deleted 0 of 0 > > > temporary files (0 non-temp files in temp directory) in 0s" > > > this point in the log, where it will stop doing anything until it > > > times itself out waiting for a signal from the JVM, and then will > > > restart over and over, until it gives up on the 5th retry. It was > > > working fine a couple days ago. I tried increasing the > > > java.exit.timeout in conf to no avail. > >
Re: [freenet-support] Error messages in wrapper log
I assume you mean the Database corrupted message? I wonder how serious it is -- if freenet was able to recover from it. Can you download files? The generic answer to such database corruptions is to get rid of (or move) node.db4o*, which will also get rid of your download/upload queues. On Fri, 08 Feb 2013 07:52:28 -0600, Mel wrote: Hello, The newer versions of Freenet are giving errors that I am not sure are safe. I have checked some of the archives but could not find the exact answer. A portion of my wrapper log is below. This is on a Vista 32bit machine with all updates as far as I can tell. The main questions are the warning about the wrapper jar and JVM being different, and having only some level of anonymity. Thanks for your help. MW STATUS | wrapper | 2013/02/05 13:01:33 | -- Wrapper Started as Console STATUS | wrapper | 2013/02/05 13:01:33 | Java Service Wrapper Community Edition 32-bit 3.3.5 STATUS | wrapper | 2013/02/05 13:01:33 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2013/02/05 13:01:33 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2013/02/05 13:01:33 | STATUS | wrapper | 2013/02/05 13:01:33 | Launching a JVM... INFO | jvm 1| 2013/02/05 13:01:41 | WrapperManager: Initializing... INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: WARNING - The Wrapper jar file currently in use is version 3.3.1 INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: while the version of the Wrapper which launched this JVM is INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: 3.3.5. INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: The Wrapper may appear to work correctly but some features may INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: not function correctly. This configuration has not been tested INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: and is not supported. INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: INFO | jvm 1| 2013/02/05 13:01:47 | freenet.jar built with freenet-ext.jar Build #29 rv29 running with ext build 29 rv29 INFO | jvm 1| 2013/02/05 13:01:47 | Creating config from freenet.ini INFO | jvm 1| 2013/02/05 13:01:47 | Creating logger... INFO | jvm 1| 2013/02/05 13:01:47 | Set interval to 10 and multiplier to 1 INFO | jvm 1| 2013/02/05 13:01:47 | Starting executor... INFO | jvm 1| 2013/02/05 13:01:47 | Finding old log files. New log file is C:\Users\Mel\AppData\Local\Freenet\logs \freenet-1432-2013-02-05-13.log.gz INFO | jvm 1| 2013/02/05 13:01:47 | Created log files INFO | jvm 1| 2013/02/05 13:01:47 | Initializing Node using Freenet Build #1432 rbuild01432 and | freenet-ext Build #29 rv29 with Oracle Corporation JVM version 1.7.0_13 running on x86 Windows Vista 6.0 INFO | jvm 1| 2013/02/05 13:01:47 | Set fproxy max length to 2306867 and max length with progress to 5767168 = 5767168 INFO | jvm 1| 2013/02/05 13:01:47 | Starting FProxy on 127.0.0.1,0:0:0:0:0:0:0:1: INFO | jvm 1| 2013/02/05 13:01:48 | INFO: Native CPUID library 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from resource INFO | jvm 1| 2013/02/05 13:01:48 | INFO: Optimized native BigInteger library 'net/i2p/util/jbigi-windows-pentium3.dll' loaded from resource INFO | jvm 1| 2013/02/05 13:01:48 | SHA1: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | MD5: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-256: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-384: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-512: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:49 | Not creating node.db4o for now, waiting for config as to security level... INFO | jvm 1| 2013/02/05 13:01:49 | FNP port created on 0.0.0.0:59903 INFO | jvm 1| 2013/02/05 13:01:49 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 1| 2013/02/05 13:01:49 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 1| 2013/02/05 13:01:49 | In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE PEERS! They can eavesdrop on your requests with relatively little difficulty at present (correlation attacks etc). INFO | jvm 1| 2013/02/05 13:01:49 | Trying to read node file backup ... INFO | jvm 1| 2013/02/05 13:01:49 | Creating new cryptographic keys... INFO | jvm 1| 2013/02/05 13:01:49 | Creating PeerManager INFO | jvm 1| 2013/02/05 13:01:49 | No darknet peers file found. INFO | jvm 1| 2013/02/05 13:01:49 | Memory is 494 MiB (518979584 bytes) INFO | jvm 1| 2013/02/05 13:01:49 | Setting standard 500 thread limit. This should be enough for most nodes but more memory is usually a good thing. INFO | jvm 1| 2013/02/05 13:01:49 |
Re: [freenet-support] Error messages in wrapper log
Woops. I should have finished reading the original message. That corrupt database message is still odd though! On Fri, 8 Feb 2013 17:02:24 -0500, Dennis Nezic wrote: I assume you mean the Database corrupted message? I wonder how serious it is -- if freenet was able to recover from it. Can you download files? The generic answer to such database corruptions is to get rid of (or move) node.db4o*, which will also get rid of your download/upload queues. On Fri, 08 Feb 2013 07:52:28 -0600, Mel wrote: Hello, The newer versions of Freenet are giving errors that I am not sure are safe. I have checked some of the archives but could not find the exact answer. A portion of my wrapper log is below. This is on a Vista 32bit machine with all updates as far as I can tell. The main questions are the warning about the wrapper jar and JVM being different, and having only some level of anonymity. Thanks for your help. MW STATUS | wrapper | 2013/02/05 13:01:33 | -- Wrapper Started as Console STATUS | wrapper | 2013/02/05 13:01:33 | Java Service Wrapper Community Edition 32-bit 3.3.5 [...] ___ 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] [freenet.uservoice.com] New message: 'Hello from germany =0Awhere are the fre...'
On Wed, 30 Jan 2013 06:29:34 +, no-re...@freenet.uservoice.com wrote: Hello from germany where are the freenet server located. when they are in the United what about the patriot act - the law that exposes all fundamental rights in order to protect them. dieter https://freenetproject.org/faq.html#legal (It's a p2p network, so every node is a server.) As with any disruptive individual-empowering (anti-state) technology (bitcoin, the internet, etc), there is always a race between users, and the violent statist psychopaths who currently control us -- and usually (always?), users win. So although it's not guaranteed that Freenet will slide under the radar to mass adoption before statists realize it's threat, it is very likely IMHO. Of course, never underestimate the brutality and inconsistency of the State. If they feel like pulling your plug, or tapping into it, they eagerly will. ___ 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] freenet not working
On Sat, 17 Nov 2012 14:14:21 +0100, jordi wrote: Hi, some time ago, my freenet node does not work fine. I hoped the last update solved this but now it's worst. Some times I have more than 30 strangers connected but suddently the node disconnects from them. I see lots of erros in the logs. I send some information, but please tell me which files do you need to help. For a start, you can check your wrapper.log file -- perhaps output a thread dump when you think it's broken (via the web/fproxy interface, in the Statistics section, Generate a Thread Dump) -- the output will also get dumped into wrapper.log. If none of that is informative, you can enable more detailed logging in the Logs section. Be careful to scrub any logs[1] of sensitive information before sending them. [1] Why can't they be scrubbed by default again? Like, I think, how Tor does it? ___ 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] Unable to figure out your site/question
On Tue, 6 Nov 2012 23:14:59 -0500, Dennis Nezic wrote: On Fri, 2 Nov 2012 13:35:50 -0700 (PDT), Ian Michaels wrote: Well, I wanted to get an answer to my question, and I'm embarrassed to say I couldn't figure out your site because of all the big words. Well, my question is: Even if Freenet itself is legal, doesn't it just let people do what everywhere they want? Correct me if I'm wrong, but it seems like Freenet would just let someone watch child porn as much as they want without repercussions. Exactly! Pretty awesome, right? (Freedom of speech/expression applies equally to the speech that you hate, as to the speech that you love. I'm sure that was mentioned somewhere in the FAQ too.) ___ 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] Unable to figure out your site/question
On Fri, 2 Nov 2012 13:35:50 -0700 (PDT), Ian Michaels wrote: Well, I wanted to get an answer to my question, and I'm embarrassed to say I couldn't figure out your site because of all the big words. Well, my question is: Even if Freenet itself is legal, doesn't it just let people do what everywhere they want? Correct me if I'm wrong, but it seems like Freenet would just let someone watch child porn as much as they want without repercussions. Exactly! Pretty awesome, right? ___ 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] Datastore resize
On Fri, 28 Sep 2012 10:10:11 +0100, Matthew Toseland wrote: On Tuesday 25 Sep 2012 02:38:07 Pascal wrote: Changed my datastore size from 750g to 850g just over 5 hours ago. It now shows Datastore(CHK-store) resize in progress: 108040/10717960. At this rate it will take about 3 weeks just to finish CHK-store. Does it them take another 3 weeks to do CHK-cache? (They were the same size beforehand). Datastore resizing is slow. Especially if it's already mostly full. :( 3-weeks slow? ___ 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] Can't run Freenet
On Sun, 23 Sep 2012 19:54:05 -0700, Mitch Kampf wrote: Hi: I've used freenet in the past without any problems. This time after a 5 month period of inactivity, I tried to launch it again and got a Wrapper Terminated unexpectedly message followed by a Freenet Launcher was unable to connect to the frenet node at port message. I uninstalled freenet, downloaded a fresh copy and reinstalled it, same messages. I turned off my firewall on my computer, and again, same messages. could my Router be blocking this? Probably not. Usually the last bunch of lines in the wrapper.log file in your Freenet directory should give you a good clue. (Aside: why isn't this in the FAQ? :P) ___ 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] db4o11-7.4 AbstractMethodError
On Wed, 15 Aug 2012 14:29:15 +0100, Matthew Toseland wrote:
On Wednesday 15 Aug 2012 05:05:44 Dennis Nezic wrote:
On Tue, 14 Aug 2012 23:50:03 -0400, Steve Dougherty wrote:
On 08/14/2012 10:52 PM, Dennis Nezic wrote:
On Tue, 14 Aug 2012 11:40:49 -0400, Steve Dougherty wrote:
On 08/14/2012 08:56 AM, Dennis Nezic wrote:
On Fri, 10 Aug 2012 15:47:35 -0400, Steve Dougherty wrote:
Any idea what may have changed before this problem started
happening? What version of ant are you using to build?
That's what I'm pulling my hair trying to find out! I only
upgraded a few system packages on my machine, like glib,
libffi, ... -- and nothing much else! But how can a seemingly
unrelated system package have such a huge effect in a Java
environment??
I haven't changed my jdk (although recently I did test with
others, sun-jdk and icedtea-bin), I haven't changed my ant, I
haven't changed my db4o's, I recompiled all of Freenet's
(direct) dependencies. This is incredibly frustrating. I mean,
1407 WAS working before, and now it's not :S.
Here are the types of AbstractMethodError's that arise:
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator
()Ljava/util/Iterator;
at freenet.client.async.ClientRequestScheduler.loadKeyListeners
(ClientRequestScheduler.java:114) [code]
ObjectSetHasKeyListener results = Db4oBugs.query (container,
HasKeyListener.class); for (HasKeyListener l : results) {
--- ** 114 [/code]
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator
()Ljava/util/Iterator;
at
freenet.client.async.PersistentStatsPutter.restorePreviousData
(PersistentStatsPutter.java:44) [code]
ObjectSetBandwidthStatsContainer BSCresult =
container.query (BandwidthStatsContainer.class); for
(BandwidthStatsContainer candidate : BSCresult) { --- **
44 [/code]
So what did you do to establish that your database is not
corrupted? These are internal db4o errors.
Hmm. So it does seem as though my datastore was corrupted.
Deleting it, and making my node create a new one got me up and
running again. Thanks Steve!
The odd thing is a bunch of us[1] have been getting this
error / corruption since about the time build1409 came out. I
sure hope it's just a freak coincidence :S.
[1] https://bugs.gentoo.org/show_bug.cgi?id=429716
Your _datastore_ was corrupted, not your node.db4o(.crypt)?! What
exactly did you do to get your node running again?
Correct. The very first thing I tried (which usually worked before
with db4o errors), was to delete my node.db4o.crypt file. That had
no effect this time. Instead, deleting datastore/*, or starting
with a fresh installation, with the wizard, got the node running.
Drastic, I know. (Although, Tommy in the bug report mentioned he
was able to reproduce the error even with a clean wizard
installation :S.)
That is not consistent with the error message you gave, which is
clearly a db4o problem.
Are you sure about that? Is there no way a corrupt datastore could
corrupt the db4o file? What do you suppose created that db4o Abstract
Method Error? (Considering the fact that deleting it, and letting
freenet make a new one still caused it.)
___
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] Poor instructions
On Sat, 18 Aug 2012 18:07:19 +1000, Peter Kunzli wrote: I am saying there is no button to click. I just get stupid geek written notices that I can do nothing about. It is no good saying something isn't working if a solution is not offered. That is very strange. You should be seeing an Update Now! button right beside that message. Unless, for some strange reason, your node isn't able to download the newer versions. What version are you currently using? How long do you keep your node running for? -- it'll take a few minutes to fetch it. How many peers are you connected to? In fact, IMHO, no. Program updating and maintaining should be your operating system's responsibility. But we digress. Operating Systems do not update independent programmes mate! The operating system provides a platform for programmes to interface with me. I suppose technically I meant it's the distribution's responsibility -- your package manager's -- definitely not a program's, IMHO. My operating system will not update independent programmes on their own. So, my implication was that you may want to consider using a better distribution :). Just a consideration. The programme needs to update itself. (My OS takes care of updating my Freenet node.) How does it do that? Easy. The same way it handles every single other program on my computer. There is a package for the program, and a big community of people watching out for updates and such. The operating system updates itself but not other programmes. Eg adobe tell me there is an update, so does my media player, So, you don't really seem to be using any package manager -- that is, *you* are left with the tedious job of figuring out what needs updating, and figuring out how to update each thing individually -- each of them probably have their own quirky way of doing things, etc. This is one of the areas where Linux (the Linux community) shines. Nevertheless, Freenet does tell you that there is an update. And it is /supposed/ to give you an Update Now! button. So, we have to figure out why your node isn't downloading the newest versions. My one does. freenet just says it is too old. The operating system has nothing to do with it. Also the download prioritisation has disappeared in the new version I downloaded. It just needs a bit of real help, it can't be that hard to offer help options with a warning message, after all the programmer has offered a dialogue box to tell us there is a problem, so obviously they know what that problem is. Ergo they can offer a solution to the said problem. So, regarding the updating issue, this is already supposed to happen :). -Original Message- From: Dennis Nezic [mailto:denn...@dennisn.dyndns.org] Sent: Saturday, 18 August 2012 12:15 PM To: support@freenetproject.org Cc: Peter Kunzli Subject: Re: [freenet-support] Poor instructions On Fri, 17 Aug 2012 06:54:11 +1000, Peter Kunzli wrote: Hi, I have been using Freenet for a long time (thanks), but your instructions and help are appalling. You say there is a problem, but never offer a solution, just some string of geek jargon that is meaningless to anyone who is not a programmer. I find it easier to just uninstall (losing all pending downloads etc) then re-install. I have not once found a solution to a problem I have had. Examples are notices saying that my node is too old and if I don't upgrade I will be left in the dust whatever that means. I cannot update, the bloody programme is supposed to do it for me! In fact, IMHO, no. Program updating and maintaining should be your operating system's responsibility. But we digress. There is no check for updates button. Freenet constantly checks for updates on it's own, and notifies you via that message you mentioned above. I'm not sure if it's supposed to auto-update on it's own, or if you have to click a button to do it manually. (My OS takes care of updating my Freenet node.) Are you saying you tried clicking, and it didn't work? ___ 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] Poor instructions
On Fri, 17 Aug 2012 06:54:11 +1000, Peter Kunzli wrote: Hi, I have been using Freenet for a long time (thanks), but your instructions and help are appalling. You say there is a problem, but never offer a solution, just some string of geek jargon that is meaningless to anyone who is not a programmer. I find it easier to just uninstall (losing all pending downloads etc) then re-install. I have not once found a solution to a problem I have had. Examples are notices saying that my node is too old and if I don't upgrade I will be left in the dust whatever that means. I cannot update, the bloody programme is supposed to do it for me! In fact, IMHO, no. Program updating and maintaining should be your operating system's responsibility. But we digress. There is no check for updates button. Freenet constantly checks for updates on it's own, and notifies you via that message you mentioned above. I'm not sure if it's supposed to auto-update on it's own, or if you have to click a button to do it manually. (My OS takes care of updating my Freenet node.) Are you saying you tried clicking, and it didn't work? ___ 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] db4o11-7.4 AbstractMethodError
On Fri, 10 Aug 2012 15:47:35 -0400, Steve Dougherty wrote:
Any idea what may have changed before this problem started happening?
What version of ant are you using to build?
That's what I'm pulling my hair trying to find out! I only upgraded a
few system packages on my machine, like glib, libffi, ... -- and
nothing much else! But how can a seemingly unrelated system package
have such a huge effect in a Java environment??
I haven't changed my jdk (although recently I did test with others,
sun-jdk and icedtea-bin), I haven't changed my ant, I haven't changed
my db4o's, I recompiled all of Freenet's (direct) dependencies. This is
incredibly frustrating. I mean, 1407 WAS working before, and now it's
not :S.
Here are the types of AbstractMethodError's that arise:
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator()Ljava/util/Iterator;
at freenet.client.async.ClientRequestScheduler.loadKeyListeners
(ClientRequestScheduler.java:114)
[code]
ObjectSetHasKeyListener results =
Db4oBugs.query (container, HasKeyListener.class);
for (HasKeyListener l : results) { --- ** 114
[/code]
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator()Ljava/util/Iterator;
at freenet.client.async.PersistentStatsPutter.restorePreviousData
(PersistentStatsPutter.java:44)
[code]
ObjectSetBandwidthStatsContainer BSCresult =
container.query (BandwidthStatsContainer.class);
for (BandwidthStatsContainer candidate : BSCresult) { --- ** 44
[/code]
___
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] db4o11-7.4 AbstractMethodError
On Tue, 14 Aug 2012 11:40:49 -0400, Steve Dougherty wrote:
On 08/14/2012 08:56 AM, Dennis Nezic wrote:
On Fri, 10 Aug 2012 15:47:35 -0400, Steve Dougherty wrote:
Any idea what may have changed before this problem started
happening? What version of ant are you using to build?
That's what I'm pulling my hair trying to find out! I only upgraded
a few system packages on my machine, like glib, libffi, ... -- and
nothing much else! But how can a seemingly unrelated system
package have such a huge effect in a Java environment??
I haven't changed my jdk (although recently I did test with
others, sun-jdk and icedtea-bin), I haven't changed my ant, I
haven't changed my db4o's, I recompiled all of Freenet's (direct)
dependencies. This is incredibly frustrating. I mean, 1407 WAS
working before, and now it's not :S.
Here are the types of AbstractMethodError's that arise:
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator
()Ljava/util/Iterator;
at freenet.client.async.ClientRequestScheduler.loadKeyListeners
(ClientRequestScheduler.java:114) [code] ObjectSetHasKeyListener
results = Db4oBugs.query (container, HasKeyListener.class); for
(HasKeyListener l : results) { --- ** 114 [/code]
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator
()Ljava/util/Iterator;
at freenet.client.async.PersistentStatsPutter.restorePreviousData
(PersistentStatsPutter.java:44) [code]
ObjectSetBandwidthStatsContainer BSCresult = container.query
(BandwidthStatsContainer.class); for (BandwidthStatsContainer
candidate : BSCresult) { --- ** 44 [/code]
So what did you do to establish that your database is not corrupted?
These are internal db4o errors.
Hmm. So it does seem as though my datastore was corrupted. Deleting it,
and making my node create a new one got me up and running again. Thanks
Steve!
The odd thing is a bunch of us[1] have been getting this error /
corruption since about the time build1409 came out. I sure hope it's
just a freak coincidence :S.
[1] https://bugs.gentoo.org/show_bug.cgi?id=429716
___
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] db4o11-7.4 AbstractMethodError
On Tue, 14 Aug 2012 23:50:03 -0400, Steve Dougherty wrote:
On 08/14/2012 10:52 PM, Dennis Nezic wrote:
On Tue, 14 Aug 2012 11:40:49 -0400, Steve Dougherty wrote:
On 08/14/2012 08:56 AM, Dennis Nezic wrote:
On Fri, 10 Aug 2012 15:47:35 -0400, Steve Dougherty wrote:
Any idea what may have changed before this problem started
happening? What version of ant are you using to build?
That's what I'm pulling my hair trying to find out! I only
upgraded a few system packages on my machine, like glib,
libffi, ... -- and nothing much else! But how can a seemingly
unrelated system package have such a huge effect in a Java
environment??
I haven't changed my jdk (although recently I did test with
others, sun-jdk and icedtea-bin), I haven't changed my ant, I
haven't changed my db4o's, I recompiled all of Freenet's
(direct) dependencies. This is incredibly frustrating. I mean,
1407 WAS working before, and now it's not :S.
Here are the types of AbstractMethodError's that arise:
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator
()Ljava/util/Iterator;
at freenet.client.async.ClientRequestScheduler.loadKeyListeners
(ClientRequestScheduler.java:114) [code]
ObjectSetHasKeyListener results = Db4oBugs.query (container,
HasKeyListener.class); for (HasKeyListener l : results) {
--- ** 114 [/code]
java.lang.AbstractMethodError:
com.db4o.internal.query.ObjectSetFacade.iterator
()Ljava/util/Iterator;
at
freenet.client.async.PersistentStatsPutter.restorePreviousData
(PersistentStatsPutter.java:44) [code]
ObjectSetBandwidthStatsContainer BSCresult = container.query
(BandwidthStatsContainer.class); for (BandwidthStatsContainer
candidate : BSCresult) { --- ** 44 [/code]
So what did you do to establish that your database is not
corrupted? These are internal db4o errors.
Hmm. So it does seem as though my datastore was corrupted. Deleting
it, and making my node create a new one got me up and running
again. Thanks Steve!
The odd thing is a bunch of us[1] have been getting this error /
corruption since about the time build1409 came out. I sure hope
it's just a freak coincidence :S.
[1] https://bugs.gentoo.org/show_bug.cgi?id=429716
Your _datastore_ was corrupted, not your node.db4o(.crypt)?! What
exactly did you do to get your node running again?
Correct. The very first thing I tried (which usually worked before with
db4o errors), was to delete my node.db4o.crypt file. That had no effect
this time. Instead, deleting datastore/*, or starting with a fresh
installation, with the wizard, got the node running. Drastic, I know.
(Although, Tommy in the bug report mentioned he was able to reproduce
the error even with a clean wizard installation :S.)
Do you think you could try git-bisect to determine whichcommit
introduced this problem, or are you not able to reproduce it at will?
So far my node is running. The only way I can think of reproducing it
is by going back to the 1407 that I was using for months -- probably
recreate my datastore with it -- and then upgrade to 1409 again :S.
___
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] db4o11-7.4 AbstractMethodError
On Fri, 10 Aug 2012 11:08:34 -0400, Steve Dougherty wrote: My guess is that this is caused by a corrupt node.db4o(.crypt). Nope. It's something a lot more bizarre and sinister than that. ___ 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] db4o11-7.4 AbstractMethodError
What's causing this? jvm 1| WrapperManager Error: Error in WrapperListener.start callback.java.lang.AbstractMethodError: com.db4o.internal.query.ObjectSetFacade.iterator()Ljava/util/Iterator; jvm 1| WrapperManager Error: java.lang.AbstractMethodError: com.db4o.internal.query.ObjectSetFacade.iterator()Ljava/util/Iterator; jvm 1| WrapperManager Error: at freenet.client.async.PersistentStatsPutter.restorePreviousData(PersistentStatsPutter.java:44) jvm 1| WrapperManager Error: at freenet.node.NodeClientCore.init(NodeClientCore.java:224) jvm 1| WrapperManager Error: at freenet.node.Node.init(Node.java:1745) jvm 1| WrapperManager Error: at freenet.node.NodeStarter.start(NodeStarter.java:175) jvm 1| WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4006) jvm 1| Shutting down... Recompiling build1407, which worked for me before, no longer works. Nor the newer builds. Recompiling with sun-jdk and icedtea-bin doesn't make a difference. Recompiling java-service-wrapper, all the db4o deps, ant made no difference. Double-u Tee Eff? ___ 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] Can't access Freenet
On Thu, 2 Aug 2012 16:07:11 +0100, Matthew Toseland wrote: [...] - Post your wrapper.log. You might want to look for anything incriminating (e.g. look for @ to find keys), [...] How about not logging anything incriminating by default? No port numbers, no keys, no nothing like that? ___ 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] New install help
On Tue, 29 May 2012 06:09:16 -0400, Neuman1812 wrote: Just installed 0.7.5 on Ubuntu 12.04 Unable to start the service. The following is my wrapper log. Any help would be great. [...] INFO | jvm 1| 2012/05/29 05:51:16 | Exception in thread main java.lang.NoClassDefFoundError: freenet/node/NodeStarter Looks like a mis-configured wrapper.conf. Try to find that config file (on Gentoo it's in /etc/freenet-wrapper.conf ... it could also be called wrapper.conf in freenet's directory?), and double-check that wrapper.working.dir is where freenet's stuff is supposed to be? ___ 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] New install help
On Tue, 29 May 2012 09:48:50 -0400, Neuman1812 wrote: Here's My wrapper.conf its the wrapper.conf that came with the install.. I made no changes to it. My freenet directory is located in a truecrypt volume that is mounted ... The directory path is /media/truecrypt1/freenet The conf is /media/truecrypt1/freenet/wrapper.conf wrapper.working.dir=../ So that looks a bit suspicious to me, although I've never used the Ubuntu package. Try changing that to the full path of where the freenet*.jar files are, or maybe try ./ (i.e. the current directory, isn't the wrapper.conf file normally in the same dir as the run.sh wrapper script?) ___ 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] Wrapper unexpected termination
On Mon, 28 May 2012 04:23:39 -0400 (EDT), morrisspoo...@aol.com wrote: I sent a log through yesterday regarding problems with freenet ever since I installed a new router. The wrapper I attatched was too big so I thing the message was bounced. May I re start my query from now ny saying that ever since installing a new router my freenet wrapper terminates and I have to re install. You can try cutting out just the last part of the log, like, from the last Launching a JVM to the end. That should be a lot shorter. Usually the culprit is a lack of memory or disk(space). So, how has the memory and diskspace changed after switching the hardware? ___ 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] Wrapper unexpected termination
On Mon, 28 May 2012 15:11:48 -0400 (EDT), morrisspoo...@aol.com wrote: Hi Dennis and thanks for the reply. No change to disk space or memory they are fine. Here is tha last park of the wrapper log from the last failed instalation. [...] INFO | jvm 1| 2012/05/28 08:38:11 | Defragmenting persistent downloads database. [...] INFO | jvm 1| 2012/05/28 08:38:26 | Defragment completed. 13.6 MiB (14320632) - 13.6 MiB (14319872) (0% shrink) [...] WrapperManager Error: at com.db4o.reflect.generic.GenericArrayReflector.set (GenericArrayReflector. java:103) WrapperManager Error: at com.db4o.internal.handlers.array.ArrayHandler.readInto (ArrayHandler.java:418) Looks like some kind of node.db4o* corruption -- another kinda common bug we seem to encounter. I have had at least one a while ago. I'm not sure if the defragmenting of it just before had anything to do with it. The simplest solution is to delete your node.db4(.crypt?|*) file. You'll lose the downloads/uploads that you had queued, but that should get the node back up and running at least :s. ___ 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] 1407 fails to start after auto-update
On Sat, 19 May 2012 17:00:09 +1200, Austin wrote: Hi Dennis, On Friday 18 May 2012 you wrote: On Fri, 18 May 2012 18:25:35 +1200, Austin wrote: On Wed, 9 May 2012 15:00:14 +1200, Austin wrote: I'm running build 1407 (which auto-updated itself from whatever I had before, 1405 I think) and it now fails to start up. Please see wrapper log at: http://www.sendspace.com/file/o9gvmq Hmm... so it's failing while trying to create a free blocks cache, every single time at the exact same place... 16384/21859. (Hopefully someone else will know something more. Double-check you're not running out of diskspace?) Hmm, doesn't look as though anyone else can help, so I'm stuck with no way to run Freenet ... :( Maybe you can test it without your current node.db4o* file(s). Try moving them out of freenet's directory (temporarily -- you can put them back later), and see if that gets things running? Hey, that worked! :) Many thanks for the suggestion. I don't know what the node.db4o* files are - there was in fact only one, and moving it elsewhere fixed the problem. I guess from that, it may be disk-space related after all. My /usr/local/freenet is a symlink to a directory on a different filesystem, precisely because there is not enough room on the 'real' /usr/local drive. My understanding was that any file or directory created under /usr/local/freenet would actually be created in the directory to which the link points. Is Freenet somehow creating files or directories elsewhere, i.e. not in /usr/local/freenet? The node.db4o files store things like your uploads/downloads -- so, you should make a copy of the links of those things before deleting it, if possible :p. Regarding the disk-space, it probably is storing your node.db4o files in the proper symlinked place, but you also have to consider the ./persistent-* directory (and possibly the ./datastore directory if you're resizing your datastore), cuz those can get pretty big too. ___ 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] 1407 fails to start after auto-update
On Sat, 19 May 2012 09:16:37 -0400, Dennis Nezic wrote: On Sat, 19 May 2012 17:00:09 +1200, Austin wrote: Hi Dennis, On Friday 18 May 2012 you wrote: On Fri, 18 May 2012 18:25:35 +1200, Austin wrote: On Wed, 9 May 2012 15:00:14 +1200, Austin wrote: I'm running build 1407 (which auto-updated itself from whatever I had before, 1405 I think) and it now fails to start up. Please see wrapper log at: http://www.sendspace.com/file/o9gvmq Hmm... so it's failing while trying to create a free blocks cache, every single time at the exact same place... 16384/21859. (Hopefully someone else will know something more. Double-check you're not running out of diskspace?) Hmm, doesn't look as though anyone else can help, so I'm stuck with no way to run Freenet ... :( Maybe you can test it without your current node.db4o* file(s). Try moving them out of freenet's directory (temporarily -- you can put them back later), and see if that gets things running? Hey, that worked! :) Many thanks for the suggestion. I don't know what the node.db4o* files are - there was in fact only one, and moving it elsewhere fixed the problem. I guess from that, it may be disk-space related after all. My /usr/local/freenet is a symlink to a directory on a different filesystem, precisely because there is not enough room on the 'real' /usr/local drive. My understanding was that any file or directory created under /usr/local/freenet would actually be created in the directory to which the link points. Is Freenet somehow creating files or directories elsewhere, i.e. not in /usr/local/freenet? The node.db4o files store things like your uploads/downloads -- so, you should make a copy of the links of those things before deleting it, if possible :p. Regarding the disk-space, it probably is storing your node.db4o files in the proper symlinked place, but you also have to consider the ./persistent-* directory (and possibly the ./datastore directory if you're resizing your datastore), cuz those can get pretty big too. (Or maybe it's temporarily dumping things in /tmp ?) ___ 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] 1407 fails to start after auto-update
On Fri, 18 May 2012 18:25:35 +1200, Austin wrote: On Wed, 9 May 2012 15:00:14 +1200, Austin wrote: I'm running build 1407 (which auto-updated itself from whatever I had before, 1405 I think) and it now fails to start up. Please see wrapper log at: http://www.sendspace.com/file/o9gvmq Hmm... so it's failing while trying to create a free blocks cache, every single time at the exact same place... 16384/21859. (Hopefully someone else will know something more. Double-check you're not running out of diskspace?) Hmm, doesn't look as though anyone else can help, so I'm stuck with no way to run Freenet ... :( Maybe you can test it without your current node.db4o* file(s). Try moving them out of freenet's directory (temporarily -- you can put them back later), and see if that gets things running? ___ 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] 1407 fails to start after auto-update
On Wed, 9 May 2012 15:00:14 +1200, Austin wrote: I'm running build 1407 (which auto-updated itself from whatever I had before, 1405 I think) and it now fails to start up. Please see wrapper log at: http://www.sendspace.com/file/o9gvmq Hmm... so it's failing while trying to create a free blocks cache, every single time at the exact same place... 16384/21859. (Hopefully someone else will know something more. Double-check you're not running out of diskspace?) ___ 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] Counter on a freepage
On Sat, 3 Mar 2012 13:27:19 -0500, Juiceman wrote: On Sat, Mar 3, 2012 at 9:22 AM, Jep j...@jep-z11.xs4all.nl wrote: There is no way to include a simple counter on a web page in Freenet as far as I can see. It would require some kind of scripting that the content filter would allow I reckon. Is it feasible to implement such? A strict method the filter allows, perhaps, writing to a log file within the freesite container. Another thing, not very important but still. The content filter strips out anything that would make favicons work. For instance, rel=shortcut icon is not accepted. I can't see how 'local' favicons, icons within the freesite, could be a danger to anonymity, so if that limitation could be taken out of the filter? Allowing just /favicon.ico would do the trick. Is there any documentation on the FN content filter? I believe .ICOs are blocked due to a Microsoft vulnerability Something about a divide-by-zero overflow. Ah, here it is. http://www.kb.cert.org/vuls/id/290961 Quote from the page: There is an integer division by zero vulnerability in the way the ICO parsing component of GDI+ (Gdiplus.dll) handles ICO files with a Heightvalue of zero in the InfoHeader section of the ICO file. By introducing a specially crafted ICO file to the vulnerable component, a remote attacker could trigger an integer division by zero denial-of-service condition. I imagine a simple filter could be written that checks that none of the dimensions are declared 0. Of course, I can say it's simple because I am not the one coding it ;-) . Aren't there tonnes of these kinds of bugs... ie. I don't think it's Freenet's responsibility to manage all the other possibly bugged packages on one's system. If anyone is using such a bugged version of Microsoft, they'll get screwed no matter what bandaids Freenet tries to apply. ___ 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] Offline installer fails
On Sun, 12 Feb 2012 09:26:34 -0600, Yfrwlf wrote: On 02/12/2012 08:19 AM, Evan Daniel wrote: So is there a ZI package yet? That sounds nice, you could make the ZI package/feed depend on JDK so there were no longer any unfulfilled dependencies on the user's end regardless of platform, since it would be automatically installed. Instead of the existing installer, you could have some of those things done with a web-based first run setup wizard. Upgrades could be handled by ZI updates instead of custom updaters, too. I don't know if redoing all that is worth it in exchange for certain perks though, since Freenet has already implemented so many of its own systems to make up for not having those systems exist across platforms. Perhaps ZI is too late to the party. :) It's not too late. The more packages, the more availability, the better. I prefer using Gentoo and it's ebuilds, so ZI is mostly irrelevant for me -- but I'm sure many people still need it. ___ 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] command line tools
On Sun, 12 Feb 2012 11:55:51 -0800, Kevin Banjo wrote: is there a command line tool to upload a file to freenet and return its CSK? One DIY possibility is Freenet's telnet interface with an expect script. (man expect). Another, probably, is via Freenet's FCP interface, possibly via netcat (man nc) or something like that? ___ 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] Offline installer fails
On Sat, 21 Jan 2012 02:05:34 -0600, Yfrwlf wrote: On 01/20/2012 04:53 PM, Dennis Nezic wrote: On Fri, 20 Jan 2012 15:50:03 -0600, Yfrwlf wrote: On 01/20/2012 03:26 PM, Dennis Nezic wrote: On Fri, 20 Jan 2012 15:12:24 -0600, Yfrwlf wrote: On 01/20/2012 10:05 AM, Evan Daniel wrote: On Fri, Jan 20, 2012 at 9:56 AM, Yfrwlfyfr...@gmail.com wrote: On 01/20/2012 07:05 AM, Dennis Nezic wrote: On Fri, 20 Jan 2012 22:10:39 +1300, Austin wrote: Originally tried the JavaWebStart installer, and had problems with disk space. Moved /usr/local to a bigger partition, then downloaded the offline installer: http://freenet.googlecode.com/files/new_installer_offline_1405.jar as per the web site instructions; also the sig file new_installer_offline_1405.jar.sig which I verified with gpg. Then ran java -jar new_installer_offline.jar All went OK until Processing step 2/15, Setting the Updater up, which reported Process execution failed and asked Continue Anyway?. I continued, but every step after that failed. Cleared out the target directory and tried again, same result. Can't find any installation log, is there one somewhere? Grateful for any suggestions as to what to try next. System is Debian Linux 2.6, amd64 (Intel i7 870), 8GB RAM. Java OpenJDK 1.6.0_18 (Side note: Why isn't there a debian package for freenet yet?) Well with the only dependency being Java I could understand why there are no packages. If there needed to be though it should be Zero Install so that it's cross-distro and cross-platform. Using Zero Install won't make it so I can apt-get install freenet. That needs a Debian package, hosted on the Debian repositories. The request is for a Debian package on Debian repos, not to make it easier to install Freenet on Debian. Evan Okay. Developers would love to not have to spend the time making a package for every distro and distro verison though, and running 0launchprogram's url to download and run a program from the command line is an option, though not as simple, but hopefully after it gets a software store for ZI collections that will become an option as well. The whole point of community distros is precisely to help program developers in this regard. Gentoo users, for example, maintain a freenet package completely on their own. It seems like you're trying to wish away the whole concept of distros. (Actually, trying to impose your own preferred yet-another-package-manager :p.) Yes, everyone loves re-packaging the same program over and over and over again, tons of fun. :P ZI is a package manager that can run on top of or beside existing package managers because it allows co-existence with other package managers. You can install it on any distro. That makes it one of the few cross-distro and cross-platform (Mac, Windows, BSD etc too) package managers out there, and thus much more capable of becoming a real actual god-forbid Linux standard to allow users and developers more freedom to share programs. So, your proposition that it's useless is totally absurd. Why anyone would go ye I have to make 50 billion different packages for the same program because there are no standards! is totally beyond my comprehension. There is no actual justification for having multiple formats/standards/managers. You want to choose one standardized system, and then throw all the features you need into the managers which are compatible with that system. [snip] From my perspective, it is useless. I already have a great package manager, and a freenet package. You also don't seem to understand the purpose of different linux distributions. The reason you need 50 billion different packages for the same program, is the same reason 50 billion linux distros exist, and the same reason why having a single standard is quite naive and absurd -- people are different. (Decentralization and independent testing that distros provide are also invaluable.) (Open-source) program developers should not be in the business of distribution. Anywho, the point is there really should exist apt-get freenet by now. And 0launch freenetwhatever too :P. You can have different bundles of software on ISOs, and even programs with different default configurations, that's good and I have no problem with that. You are naively assuming the only difference between packages is configuration files. That's simply not the case. Some people would like to compile packages to minimize size. Other people to maximize speed. Still other people for other special reasons. Believe it or not, things are the way they currently are for valid reasons. That has no bearing whatsoever though on having a standardized package management solution. In terms of practical importance, standardized packages are waay down on the priority list. The reason a debian freenet package doesn't yet exist has very little to do
Re: [freenet-support] unable to connect after new installation of freenet on a fit-pc and ubuntu 8.04
On Fri, 6 Jan 2012 23:53:53 + (UTC), user1 wrote: Hardware fit-PC 1.0: CPU: AMD Geode LX800 500MHz Chipset: AMD CS5536 Display: Integrated Geode LX display controller up to 1920x1440 Memory: 256MB DDR 333MHz soldered on-board Hard disk: 2.5” IDE 60GB Ports: 2 x RJ45 Ethernet ports 100Mbps 2 x USB 2.0 HiSpeed 480Mbps RJ11 RS-232 (cable available from CompuLab) VGA DB15 Stereo line-out audio (headphones) Stereo line-in audio / Mic I have now reduced the size of memory usage from 512mb to 256mb but still have the same problem ? (You only have 256MB physical memory, right? I'm guessing your machine was swapping a /lot/ before, if Freenet alone was using more than your max?) Anywho, reducing freenet's java memory usage will probably make things worse -- it'll make it max-out sooner. Try reducing the size of your datastore. (To test that this is in fact the problem, you can put it back to it's original size, and theoretically, you should get the same uptimes back?) I have reduced datastore from 30 to 20 gb and it still does not work properly. What bothers me is how it was running for a couple years without problems before. From what I gathered here, the main/only thing you changed was your datastore size? Surely if you put that back to normal, things should work like before? Here is my wrapper log: http://dl.dropbox.com/u/5177370/user1-wrapper.log.zip Wonder if my hardware is too light for freenet server use now? Hmm, okay, I guess that wasn't too helpful :p. But, many clues can be gleaned nevertheless. The first hang was caused by Resizing datastore, although I'm not sure if it was due to insufficient memory, or I/O bottleneck. (Perhaps you can monitor your free memory and uptime values next time.) After that first hang, it looks like your node wasn't even able to restart itself -- it could be a wrapper problem, or perhaps a node bug caused by the original failed datastore-resizing attempt. Magically, 8 hours later, it does manage to restart, but 15 minutes in, it hangs again during datastore maintenance -- again, probably due to insufficient memory. You said you reduced memory from 512mb to 256mb -- put it back to 512, if you can :p. Alternatively, you can test with a fresh/new datastore, to avoid resizing overhead, which I believe is costly? ___ 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] unable to connect after new installation of freenet on a fit-pc and ubuntu 8.04
On Tue, 3 Jan 2012 16:23:43 + (UTC), user1 wrote: On Tue, 03 Jan 2012 04:41:11 +, user1 wrote: On Mon, 02 Jan 2012 22:45:36 -0500, Dennis Nezic wrote: So it does work, for a little bit? :) The last few lines of your freenet/wrapper.log file should be informative. My guess is you're running out of memory -- so I bet there's a huge thread dump at the end of that file, at the top of which there is a little line saying out of memory, or something. Perhaps increasing your datastore increased your memory requirements too far. Try a smaller datastore size. Does not show out of memory But says: Error JVM appears hung: Timed out waiting for signal from JVM JVM did not exit on request Unable to start JVM Then I have to restart and same repeats At most I had 7 nodes connected for a very short period Hardware fit-PC 1.0: CPU: AMD Geode LX800 500MHz Chipset: AMD CS5536 Display: Integrated Geode LX display controller up to 1920x1440 Memory: 256MB DDR 333MHz soldered on-board Hard disk: 2.5” IDE 60GB Ports: 2 x RJ45 Ethernet ports 100Mbps 2 x USB 2.0 HiSpeed 480Mbps RJ11 RS-232 (cable available from CompuLab) VGA DB15 Stereo line-out audio (headphones) Stereo line-in audio / Mic I have now reduced the size of memory usage from 512mb to 256mb but still have the same problem ? (You only have 256MB physical memory, right? I'm guessing your machine was swapping a /lot/ before, if Freenet alone was using more than your max?) Anywho, reducing freenet's java memory usage will probably make things worse -- it'll make it max-out sooner. Try reducing the size of your datastore. (To test that this is in fact the problem, you can put it back to it's original size, and theoretically, you should get the same uptimes back?) ___ 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] unable to connect after new installation of freenet on a fit-pc and ubuntu 8.04
On Tue, 3 Jan 2012 03:13:24 + (UTC), user1 wrote: I am using ubuntu 8.04 and fit-pc will not let me upgrade to newer ubuntu version. Are you referring to Freenet or Ubuntu? :p I have reinstalled freenet with a bigger new datastore It is supposed just to run as a freenet server It has been running for a couple of years without problems When i reboot it starts all right and I want to let it run 24 hours/day After maybe an hour is says Unable to connect try again So it does work, for a little bit? :) The last few lines of your freenet/wrapper.log file should be informative. My guess is you're running out of memory -- so I bet there's a huge thread dump at the end of that file, at the top of which there is a little line saying out of memory, or something. Perhaps increasing your datastore increased your memory requirements too far. Try a smaller datastore size. Then I have to restart and same repeats At most I had 7 nodes connected for a very short period Hardware fit-PC 1.0: CPU: AMD Geode LX800 500MHz Chipset: AMD CS5536 Display: Integrated Geode LX display controller up to 1920x1440 Memory: 256MB DDR 333MHz soldered on-board Hard disk: 2.5” IDE 60GB Ports: 2 x RJ45 Ethernet ports 100Mbps 2 x USB 2.0 HiSpeed 480Mbps RJ11 RS-232 (cable available from CompuLab) VGA DB15 Stereo line-out audio (headphones) Stereo line-in audio / Mic Cool machine. How much? :D ___ 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] Corrupted node.db4o.crypt causes exceptions
On Tue, 13 Dec 2011 18:02:05 +0100, Roland Häder wrote: Hi, I hope I don't need to delete my node.db4o.crypt file, while the node was running, I got tons of exceptions like in exception1.log. After I tried to restart (with one-time defrag, in hope it will drop invalid entries) I got another one as in exception2.log. Node release: Freenet 0.7.5 Build #1405 build01405 Freenet-ext Build #29 rv29 Perhaps try sending a copy of your report to the freenet.devel mailing list? I'm not sure if any devs read this regularly. ___ 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] Freenet speed local threats
On Sun, 11 Dec 2011 01:04:09 -0500, Chris wrote: [...] I would put money on them taking advantage of zero day exploits and/or the courts to force the Tor project, the Freenet project, the i2p project, or any other similar project to modify the code and insert a back door. Germany did this many years ago with one project and successfully identified a user. It was none of the above projects although the ability to force upon developers code changes that go out to all users has occurred. They were targeting one individual too that appeared to be a fairly low-value target. The only thing that might stop this from happening to other projects is where the developers are operating in one country and the government attempting to force the change is in another. Another thing that might stop this from happening is open source software, and at least a bunch of coders reviewing and signing any code before it gets released. (I'm actually not sure how many coders have to currently sign -- surely it's not just Toad?) Do you have a link or more info on that German case? Was it open-source software? Did the developer willingly co-operate, or did they use some kind of backwards legal mechanism to force him? I wonder how much I can buy Toad for. Everyone has a price ;-). The whole point of opennet is to be able to connect to anybody you want :P. And if your ISP is compromised, this becomes even more trivial -- they can block all but their own seednodes, so you're forced to only connect to their bugged nodes as peers. This should become apparent to the user How would you propose to differentiate between a bugged node and a normal node? and if is not made apparent that is a problem with freenet (or whichever project you would be suggesting). Yes it is. And that's why it's in the FAQ :p. You should take a bit more time, and read it more carefully: Combined with harvesting and adaptive search attacks, [the bootstrapping attack] explains why opennet is regarded by many core developers as hopelessly insecure. If you want good security you need to connect only to friends. [...] In darknet, you *explicitly* specify who to connect to (hopefully a trusted friend), and you don't connect to anybody else. So, to infiltrate this setup, the bad guys would have to physically compromise your friends' nodes, one by one. To infiltrate opennet, they just have to type on a keyboard in the comfort of their homes. If you could trust your friends there wouldn't be any need for freenet. The problem is you can't trust anybody. If you can't trust anybody, then what do you hope to achieve? Who do you hope to communicate with -- if everyone is your enemy? ___ 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] Freenet speed local threats
On Sun, 11 Dec 2011 16:36:53 -0500, Chris wrote: How many users actually compile it themselves? Me, and all other Gentoo users :-). How many examine the diffs? I do, rarely :s. [...] How would you propose to differentiate between a bugged node and a normal node? This is why you have authentication and checks against any inability to connect to nodes. There is no such authentication that would help here. And you would be able to connect to any node normally -- except the compromised nodes would still find a way to become your peers and surround you. (I'm not sure exactly what criteria need to be met for your node to accept a stranger's offer, but I'm sure a dedicated adversary can easily meet them.) You are looking at the issue wrong. It doesn't matter which nodes are bugged. If a user can't connect to higher than normal percentage of nodes it should send up a red flag for one. They will be able to. You can keep track of nodes as well and check out which nodes are new and which have been added over time. The number of new nodes coming online shouldn't exceed a certain threshold. If there are 5,000 and on average the number of nodes increase by 2 a week then 100 new nodes coming online should send up a red flag. I don't know what the actual numbers are or the range. Maybe some weeks do see 100 nodes and others only 2. There is probably a number though that could increase the time it takes to pull off such an attack. There is no such metric -- a slashdot article, for example, could easily trigger such a gauge. Moreover, you're not understanding the attack enough -- the bad guys don't need to control too many bugged nodes -- just a few which they will find a way to peer with you. By the way, here is one freesite that tries to measure how many nodes are on the network: USK@85gZTCiQO9IEPDAGvjktO9d-ZMS1lIABR6JB85m4ens,VGDItiCVzCcWAay51faZzcIfAepzeHpzXYvChlueWYE,AQACAAE/stats/1533/ and if is not made apparent that is a problem with freenet (or whichever project you would be suggesting). Yes it is. And that's why it's in the FAQ :p. You should take a bit more time, and read it more carefully: Combined with harvesting and adaptive search attacks, [the bootstrapping attack] explains why opennet is regarded by many core developers as hopelessly insecure. If you want good security you need to connect only to friends. I don't think you understand how it works that well. I suspect if some of your friends are compromised you won't be. Did you even read the Correlation attacks subsection, from http://freenetproject.org/faq.html#attack ? I don't doubt that some developers think opennet mode is hopelessly insecure. It's not that they think it's hopelessly insecure. It really is :p. I mean, it might still be good enough -- but there are actual, well-known, unsolvable problems with the opennet idea. Which that FAQ should have explained :p. I think the best way to organize a revolt or guerrilla war fare in todays world would probably be to anonymously organize multiple small groups. I strongly disagree. The battle (no matter which one you pick, probably) is ultimately in the minds of the boring violence-phobic masses -- the majorities. If you don't have popular support, you're doomed no matter what you try to do. The best way to organize a revolt is to talk to your friends and family and convince them peacefully and rationally. (And freenet is a great tool for this! :D.) ___ 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] Freenet speed local threats
On Sun, 11 Dec 2011 20:05:36 -0500, Chris wrote: On Sun, 11 Dec 2011 16:36:53 -0500, Chris wrote: How many users actually compile it themselves? Me, and all other Gentoo users :-). How many examine the diffs? I do, rarely :s. [...] How would you propose to differentiate between a bugged node and a normal node? This is why you have authentication and checks against any inability to connect to nodes. There is no such authentication that would help here. And you would be able to connect to any node normally -- except the compromised nodes would still find a way to become your peers and surround you. (I'm not sure exactly what criteria need to be met for your node to accept a stranger's offer, but I'm sure a dedicated adversary can easily meet them.) I think you are wrong here. I think authentication could work to a degree provided certain conditions are true/consistent enough. I am assuming certain things such as there being enough nodes that come online daily and stay online permanently. It may not work if the number of nodes which come online and then go offline is high. I'm no expert here although in theory you should be able to use authentication to verify that old nodes are still under the control of the person they were under prior. Chances are the initial nodes you trust aren't going to be compromised by your adversary. First of all, on opennet, the peers you are connected to change every few minutes/hours. They are not static. They constantly change to make routing more efficient, via swapping. I was not suggesting the bad guys actually compromise other people's nodes -- the far easier and more likely scenario is they simply have *their own bugged nodes*, and try to become your peer. (And I think, (not absolutely sure), for a dedicated attacker, this is pretty easy.) The adversary would have to slowly bring on new nodes then and would be limited to a particular number of nodes per day (however many is typical). If they try bringing on too many new nodes at once an alert should go up. So, again, *their nodes* (just a few... 10-20?) will initiate peering with your node. And there is nothing you or anyone can do about it. This is the problem with connecting to strangers -- ie. opennet. Although, I guess this can be (already is?) mitigated somewhat if we only allow a certain percentage of our peers to come from external (swap, etc) requests -- but then it would simply become a question of time before you initiate peering with their nodes -- and they will have many, including big and popular seednodes. For instance say there are 5000 nodes already, and there are never more than 20 new nodes that come on per day then the adversary would need 8 months to add 5000 nodes. If they brought on 40 nodes a day it would be apparent that an attack was underway. How would you tell the difference between freenet becoming more popular, and the bad guys slowly infiltrating the opennet? Also, you assume they only have a few days to perform the attack -- how do you know most of the current nodes aren't them right now? The way to do this really is to monitor the data and figure out what the statistics are or have been over time and then base it off this information. If there is a change in those statistics it could indicate an attack. This is being done. But it won't help in this case at all. (Even if I wanted to dump thousands of bugged nodes into the network, I could simply post a Slashdot article, and join that upsurge.) You are looking at the issue wrong. It doesn't matter which nodes are bugged. If a user can't connect to higher than normal percentage of nodes it should send up a red flag for one. They will be able to. They will be able to what? They will be able to connect to normal nodes too. Of course, from your perspective, they're *all* equal strangers. (On opennet.) I don't doubt that some developers think opennet mode is hopelessly insecure. It's not that they think it's hopelessly insecure. It really is :p. I mean, it might still be good enough -- but there are actual, well-known, unsolvable problems with the opennet idea. Which that FAQ should have explained :p. I'm not arguing it is or isn't. Everything is relative though. No, everything is not relative :P. Opennet *is* pretty easily exploitable by design. This isn't a problem with freenet in particular -- but of any untrustworthy network. (Opennet does actually have a minimal amount of trust in it -- via the seednodes. But it's easily exploitable. A darknet is the way to go. (The only reason why the opennet is still around is because people are lazy and complacent.)) I think the best way to organize a revolt or guerrilla war fare in todays world would probably be to anonymously organize multiple small groups. I strongly disagree. The battle (no matter which one you pick, probably) is ultimately in the minds of the boring
Re: [freenet-support] Freenet speed local threats
On Sun, 11 Dec 2011 22:26:50 -0500, Chris wrote: [...] If you go out and publicly denounce a rouge government you are liable to get yourself shot long before you have any chance to gather support. The Internet is a great platform to anonymously gather support. When everybody comes out at once to support a cause you won't be shot. There will be too many others for them to notice. This is why I specifically said that your friends and family are where the battle is really at -- not some impersonal public demonstration in front of the bad guys' palace. (If your friends are online, then Freenet is useful. If you expect to teach online strangers, then I believe you will probably fail. Speaking from (extensive!) personal experience :p.) I don't believe rogue governments exist. They are all supported by the majority -- probably via ignorance -- but supported nonetheless. ___ 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] Freenet speed local threats
On Fri, 9 Dec 2011 17:29:33 -0500, Chris wrote: [...] Many users have a persistent local threat that they need to be aware of. Leaving a server running is not an option as it could be compromised by an adversary. Removable media can reduce that threat. [...] I was not referring to zero day exploits actually. The key word here was local real-world threats. Such as an adversary gaining physical access to the server/machine running freenode. If the bad guys have physical access, and care, it's game over. I suppose you can try setting secret tripwires that might notify you if the machine was tampered with (both in software, and in hardware.) Those might give you a fighting chance. Although you'll also need to make sure your room wasn't bugged with pin-hole cameras and other spy-ware. It's a lost battle, regardless. Removable media may not eliminate the threat although there is less opertunity for a more sophisticated targeted attack. A software keylogger inserted into the MBR or similar would not be possible if the boot medium is never available to the attacker. But it will be available if you ever decide to boot, happily recording everything. Again, if you think your machine was actually tampered with, you should assume it's unusable. On the other hand a physical keylogger may still be possible and maybe even a software based keylogger although more difficult to disguise/install without being noticed. Of course. You should expect a variety of key loggers installed, in code, under your keyboard keys, acoustic key loggers stuck somewhere inside the machine (that can acoustically determine which key you're pressing), and a bunch throughout your room in pin holes in your walls and ceiling. I can think of at least a few different ways of getting a keylogger onto a system without having access to the boot drive or having to install a physical device. I would still need physical access to the computer. At least one method would not even require BIOS modification and would work on any x86 machine. So you're already aware that there is not much hope if the bad guys get physical access? :p [...] Lets give a scenario: We have to assume that a persons Internet connection is being monitored. This might be via a sophisticated non-governmental actor (such as by breaking WEP/WPA) or by a government act such as monitoring at the telco. The adversary should also be assumed to be unethical in that there are no rules In that case, if you're using only opennet-mode, you should assume you're screwed :p. They can replace all your opennet peered nodes, and see exactly what you're doing, more or less. This is why darknet-mode was created -- they would need to physically infiltrate all your friend's computers, which isn't impossible, but MUCH more difficult. and can physically modify or otherwise install a software based monitoring solution on any boot media they have access to. Then you're *definitely* screwed, regardless, as explained above. The first question is how many peers need to be compromised to identify the content being transmitted? All of them, to be 100% sure. Compromising opennet peers is trivial -- with a dedicated-enough adversary. Compromising darknet is a lot harder. If a few of your freenode peers can be compromised and the adversary can monitor your Internet connection and local area network can they identify the contents which are being requested/sent by you? This assumes that they can't bug the physical machine that you are using to run freenode. As long as you still have one uncompromised peer, I guess they can't be sure what traffic you're generating locally, and what you're simply relaying for that peer (or that peer's peers, etc). But if they're able to compromise all-but-one of your peers, it's pretty darn close to game-over :p. If I was an unethical bad guy, I'd arrest you and that peer, separate you into isolation-cells, and play psychological games until one of you confesses. Or perhaps torture. (Although, if that other peer doesn't have anything to hide, or isn't your friend, I'd easily jump to the conclusion that you're the one I'm looking for :). If you add a server with freenode (which can be bugged) to your local LAN that is then added as one of your peers does this compromise the security? The point of adding a server with freenode to peer with on the local LAN would be to speed up requests since the machine that is actually used for browsing freesites (such as a laptop) can't be left on all the time (as doing so gives an adversary opportunity to bug it). This means it has to run from a removable boot medium that can be accounted for at all times. Overlooking the above points about physically-tampered machines (we *really* shouldn't overlook them), I think this setup essentially means that you can expect one of your lan peers to be compromised. But, as long as your router isn't bugged, and as long as that peer isn't the
Re: [freenet-support] Freenet speed local threats
On Sat, 10 Dec 2011 20:06:10 -0500, Chris wrote: On Fri, 9 Dec 2011 17:29:33 -0500, Chris wrote: [...] Many users have a persistent local threat that they need to be aware of. Leaving a server running is not an option as it could be compromised by an adversary. Removable media can reduce that threat. [...] I was not referring to zero day exploits actually. The key word here was local real-world threats. Such as an adversary gaining physical access to the server/machine running freenode. If the bad guys have physical access, and care, it's game over. I suppose you can try setting secret tripwires that might notify you if the machine was tampered with (both in software, and in hardware.) Those might give you a fighting chance. Although you'll also need to make sure your room wasn't bugged with pin-hole cameras and other spy-ware. It's a lost battle, regardless. This is completely dependent on who the adversary is, the level of sophistication, mistakes they may make, the resources they may have, how badly they want you, what they know about you, and what other precautions have been taken. A pin-hole camera for instance should not be enough to compromise a good setup. How do you figure? (The camera can see everything you're typing and your screen, right? If you have any additional biometric login requirements, they can easily be gotten from you later.) Nor should a MBR level key logger installation. These two things are easier to do than a BIOS level modification. A BIOS level modification gets a lot more complicated as each system uses a different BIOS. When there is no generic solution to a problem or that solution is more cumbersome it may not exist. If it does exist it may be used much more selectively and there will almost certainly be fewer adversaries who have access to it. You may not be a target of a significantly high level adversary (where such levels may exist). Removable media may not eliminate the threat although there is less opertunity for a more sophisticated targeted attack. A software keylogger inserted into the MBR or similar would not be possible if the boot medium is never available to the attacker. But it will be available if you ever decide to boot, happily recording everything. If the adversary does not have access to your boot medium how do you think they are going to install it? When you do boot it should not exist. There are few places that a keylogger or device can be installed. BIOS, optical drive, USB port, PC card slot, firewire, network etc. These are all things that can be checked. The only exception is the BIOS. The BIOS differs from machine to machine which should increase the cost of the adversary to produce a solution. I have never heard of a BIOS level bug. There have been conceptual modifications to suggest it may be possible although nothing in practice to show it could be done easily. Again, if you think your machine was actually tampered with, you should assume it's unusable. Nobody is arguing that a knowingly compromised machine or one that there is reason to suspect could have been compromised should be used. But any machine that the adversary has physical access to should be suspected to have been compromised. A BIOS-level bug, as you explain, is one great way. Personally, I would prefer lower-tech spy solutions. Of course, you can assume your adversary is weak, but that's a risky assumption. On the other hand a physical keylogger may still be possible and maybe even a software based keylogger although more difficult to disguise/install without being noticed. Of course. You should expect a variety of key loggers installed, in code, under your keyboard keys, acoustic key loggers stuck somewhere inside the machine (that can acoustically determine which key you're pressing), and a bunch throughout your room in pin holes in your walls and ceiling. None of which can't be avoided. As far as I know. Please explain. I can think of at least a few different ways of getting a keylogger onto a system without having access to the boot drive or having to install a physical device. I would still need physical access to the computer. At least one method would not even require BIOS modification and would work on any x86 machine. So you're already aware that there is not much hope if the bad guys get physical access? :p I disagree. Most bad guys aren't as sophisticated as one might think. Including the ones coding the bugs and exploits used. They will create a bug and assume it works. In reality it only works if x, y, and z are true. Provided you have taken sufficient precautions this rarely is the case. Most adversaries need not be sophisticated at all. They merely need to carry out a set of instructions found somewhere. Be it they ordered a physical keylogger online or followed an instruction set of procedures that works for
Re: [freenet-support] Freenet speed local threats
On Fri, 9 Dec 2011 05:26:19 -0500, Chris wrote: I am looking into setting up a distribution where Tor or freenet is used to create a secure and anonymous environment for communicating. Very cool. I've done that too :-). One of the issues with freenet is that it is slow. I haven't used it in many years and do understand it has gotten much better. I also am aware that after a few days it gets faster as popular data is retained and gets 'cached' on your node and nearby nodes based on what those around you are doing. What I'm trying to figure out is what happens when your node is not on 24/7 and you can only connect infrequently for several hours at a time. It runs at esssentially the same speed (minus the benefits of immediate local caching, of course) -- which is pretty slow but manageable. It may take a few seconds / a minute longer to fetch things, but that's still a minute longer than the censored web provides, so either way users will have to adjust their expectations. Booting into the network will also take an additional minute or so, which always-on nodes don't have to worry about. Many users have a persistent local threat that they need to be aware of. Leaving a server running is not an option as it could be compromised by an adversary. Removable media can reduce that threat. The keyword being *reduce* :p. We all have that concern and fear, of unforeseen zero-day linux exploits, etc. (We already know they exist in Window$ :). Ideally you would want to make extra sure you have enough contingency planning (proper permissioning / stable and patched software / firewalls / perhaps caged virtual machines / sentry programs / whatever your paranoia desires), so such fears are minimized. They will never be eliminated though. What I'm looking to find out is if you run a freenode from a removable media and then run a local server running freenode to use as one of your peers (which could be on all the time) does this post a threat? Besides the obvious risks of either of those machines being compromised (by any number of ways: physically, buggy software, leaky software, etc), traffic analysis will always be a threat with Tor, and also with Freenet if bad guys have somehow managed to occupy all your peer connections. But besides these well known threats, I think it's pretty safe. But not perfectly safe. If no local server is run that you peer with how is the speed if you only connect every few days? Is running freenet for a few hours to several hours going to be sufficient or will it be unbearably slow? It's bearable. (After it takes a few minutes to connect to the network.) I suppose it's similar to fetching a freesite you never fetched before -- perhaps a bit faster. With Tor speeds are frequently severely limited. Especially with .onion nodes. Some non-onion servers can be accessed with significant speed though for sustained periods (15-300... maybe faster). That's probably not a Tor-specific problem -- but simply the less powerful server behind the onioning. I don't think there are any youtube-sized .onion servers. ___ 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] Lots of questions about Frost and Thaw
On Fri, 09 Dec 2011 10:13:39 -0800, Walter Barnes wrote: On 12/8/2011 11:06 AM, Dennis Nezic wrote: On Thu, 08 Dec 2011 09:12:01 -0800, Walter Barnes wrote: [...] Do I even need Frost? If you want a forum on freenet, then sure, it is one of at least three different forum systems. It's a standalone Java program (that operates over your freenet node in the background.) FMS is a similar, newer and better standalone program, written in C. Freetalk is an even newer system, written as a Java plugin to your node, and installed/accessed via your node's control panels (normally) -- although I hear it (still) has performance issues. Thanks Denis but I'm just looking for ways to access Frost message boards. That's fair enough. Although, you should be aware that the other two newer systems were built specifically because Frost can be trivially DOS-ed and rendered unusable. (They use webs of trust, instead of allowing anybody/anything to post.) ___ 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] Lots of questions about Frost and Thaw
On Thu, 08 Dec 2011 09:12:01 -0800, Walter Barnes wrote: [...] Do I even need Frost? If you want a forum on freenet, then sure, it is one of at least three different forum systems. It's a standalone Java program (that operates over your freenet node in the background.) FMS is a similar, newer and better standalone program, written in C. Freetalk is an even newer system, written as a Java plugin to your node, and installed/accessed via your node's control panels (normally) -- although I hear it (still) has performance issues. Naturally, none of these systems talk to each other. We can hack up sophisticated mathematical elliptical curve ciphers and complex routing algorithms for ad-hoc network topologies, but creating compatible protocols is simply beyond us. ___ 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] Announcement to version 1404 peers not working
On Tue, 15 Nov 2011 02:22:06 +0100, Roland Häder wrote: Hello, I got this in wrapper.log (grep Announce wrapper.log). Announcement to ...: not accepted (version 1404) . And for some more nodes the same: [...] Can someone please look what is wrong here? What do you need else to investigate this (strange looking) error message? Perhaps your problem is related to Jep's mentioned here a few days ago. What operating system are you using? ___ 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] Getting onto the network
On Sat, 12 Nov 2011 14:31:25 +0100, Jep wrote:
Dsoslglece :
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet
folder, including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience,
restart FN every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first
time wizard and reconfigure. But also then it can take hours until
the node finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
false: 25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives
hit: 20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
hit: 16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives
hit: 14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives
hit: 12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing
else as it seems.
Sounds crazy, but what system are you using ? in the last 2 or 3
years, I experimented from time to time, and with some updates,
temporary troubles… but normally everything seems smooth, even
connecting to strange nodes and so on (iMac intel core duo, 10.7)
XP sp3 updated often, java 6 update 29(build 1.6.0_29-b11), no
software firewall, no realtime virus scanner, no realtime
antimalware. Would my box be infected with a rootkit, I should have
noticed in that time somehow.
Everything runs okay once connected usually, apart from with current
build the node losing its peers down to zero at times, bringing me to
connection hell.
But normally, once connected it stays that way until winz forces me
to reboot, which is at least once a week.
Today, after a sys restart, zilch up til nothing happens.
What are your bandwidth settings / total possible connected peers?
(Maybe either your connection settings are making your peers drop you
for some bizarre reason, or maybe your ISP is somehow blocking you --
are you using a chinese ISP (proxy)? :P Also, is your freenet port
forwarded? (Does fproxy say it is, if it ever connects?) Are you sure
you're using the latest version of Freenet? (Using an obsolete version
would have similar symptoms.)
___
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] [freenet.uservoice.com] New message: 'could this project be able to help rebui…'
On Fri, 11 Nov 2011 07:04:38 +0100, David ‘Bombe’ Roden wrote: Hi Dennis, could this project be able to help rebuild the internet in the advent of a society breakdown or in an apocylypse No. I think the question only asked if it *could help* -- not if Freenet alone would /necessarily/ achieve anything. It can not help to _rebuild_ the internet because it _requires_ the internet. Simple as that. :) Not necessarily -- any two or more nodes connected in any way -- wireless signals / sneakernet / etc -- could begin a local freenet that can be used to organize and communicate things. Electricity would be a requirement, though -- but surely a generator or solar panel or wind mill would still be accessible, somewhere? ___ 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] [freenet.uservoice.com] New message: 'could this project be able to help rebui…'
On Thu, 10 Nov 2011 19:51:36 +0100, David ‘Bombe’ Roden wrote: Hi reply, could this project be able to help rebuild the internet in the advent of a society breakdown or in an apocylypse No. I think the question only asked if it *could help* -- not if Freenet alone would /necessarily/ achieve anything. So, yes, I think a robust communication system /could/ /help/ :). ___ 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] [freenet.uservoice.com] New message: 'could this project be able to help rebui…'
On Thu, 10 Nov 2011 03:26:32 +, no-re...@uservoice.com wrote: Customer Feedback for Freenet Project Inc. freenet.uservoice.com [freenet.uservoice.com] New Bug Report gmosph...@yahoo.com sent a message from https%3A%2F% 2Ffreenetproject.org%2Flists.html [https%3A%2F%2Ffreenetproject.org% 2Flists.html] could this project be able to help rebuild the internet in the advent of a society breakdown or in an apocylypse Yes. ___ 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] please help
On Fri, 4 Nov 2011 18:27:13 + (UTC), Fred Vishio wrote: Dennis Nezic dennisn@... writes: What operating system are you using? Perhaps you can find where Freenet was installed, and copy/paste (or attach) the wrapper.log file from in there? Or just read it -- the last few lines should probably tell you what went wrong. i use windows 7 im really confused about what its talking about and sorry i dont know how to attach. [...] Could not start web interface: java.net.SocketException: Permission denied: listen failed [...] Looks like a permissions problem. Hopefully an MS-Window$ user will be able to help resolve it. But that doesn't necessarily have to stop me from handwaving -- perhaps you need to be an Administrator or some special networks-capable user to launch daemons. ___ 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] please help
On Thu, 3 Nov 2011 20:46:05 -0400, Fred Vishio wrote: When I try to run freenet it says that the freenet wrapper terminated unexpectedly. When I click ok another window pops up and says the launcher couldn't connect to the freenet node at port . it tells me to try to reinstall on both windows. I have reinstalled many times and it doesn't help. What operating system are you using? Perhaps you can find where Freenet was installed, and copy/paste (or attach) the wrapper.log file from in there? Or just read it -- the last few lines should probably tell you what went wrong. ___ 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] [freenet.uservoice.com] New message: 'i searched for privacy and to implement …'
On Fri, 21 Oct 2011 09:06:03 +, no-re...@uservoice.com wrote: Customer Feedback for Freenet Project Inc. freenet.uservoice.com [freenet.uservoice.com] New Bug Report davidsil...@gmx.com sent a message from http%3A%2F% 2Ffreenetproject.org%2F [http%3A%2F%2Ffreenetproject.org%2F] i searched for privacy and to implement anonymity on internet, and came across your software.having downloaded it and installed it, just tried it out and it seems to host paedophile networks??? this is scary shit and i realise you protect anonymity for everyone, but surely not for these purposes?! Any suggestions or excusese? explain or risk being exposed! Read the fucking FAQ, http://freenetproject.org/faq.html#childporn (You know what's even more scary shit, IMHO? People using brutal force to censor pixels and letters.) ___ 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] http fproxy ports are not closed
On Thu, 22 Sep 2011 07:09:58 +0200, David ‘Bombe’ Roden wrote: On WOCHENTAG, tT. MONAT 23:21:53 Dennis Nezic wrote: And, I still don't quite understand why you can't check the status of a socket, or be notified of wget's FIN signal (It did send one, didn't it, or am I missing something?) -- isn't that fundamental to any tcp connection?? As Matthew already told you, finding out whether a socket has been disconnected can only be done by reading from or writing to the socket. We don’t do either until the request is finished. There’s your answer and it won’t change if you ask more often. What determines whether a request is finished? When I browse freesites normally, those requests expire gracefully. Also, this bug (something fishy is definitely going on) is stranger than I described, because I'm not exactly sure what creates those abandoned open threads/sockets -- it's not simply a wget request, nor one that ends in a failure (500 Internal Error) -- those all end well. :S. A thread dump says they (all 50+ of them) are locked in FProxyFetchWaiter: HTTP socket handler@15723301 (1994) daemon prio=10 tid=0x08a5f800 nid=0x76b6 in Object.wait () [0xb1ffe000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait (Native Method) at java.lang.Object.wait (Object.java:485) at freenet.clients.http.FProxyFetchWaiter.getResult (FProxyFetchWaiter.java:28) - locked 0x6dc52720 (a freenet.clients.http.FProxyFetchWaiter) at freenet.clients.http.FProxyToadlet.innerHandleMethodGET (FProxyToadlet.java:663) at freenet.clients.http.FProxyToadlet.handleMethodGET (FProxyToadlet.java:459) at sun.reflect.GeneratedMethodAccessor15.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:597) at freenet.clients.http.ToadletContextImpl.handle (ToadletContextImpl.java:550) at freenet.clients.http.SimpleToadletServer$SocketHandler.run (SimpleToadletServer.java:989) at freenet.support.PooledExecutor$MyThread.realRun (PooledExecutor.java:233) at freenet.support.io.NativeThread.run (NativeThread.java:130) ___ 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] http fproxy ports are not closed
On Sun, 18 Sep 2011 20:23:35 -0400, Dennis Nezic wrote: On Fri, 9 Sep 2011 09:05:55 -0400, Dennis Nezic wrote: On Fri, 9 Sep 2011 13:00:30 +0100, Matthew Toseland wrote: On Wednesday 07 Sep 2011 21:35:44 Dennis Nezic wrote: On Wed, 7 Sep 2011 17:50:36 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 15:34:30 Dennis Nezic wrote: On Fri, 2 Sep 2011 14:40:22 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 13:20:39 Dennis Nezic wrote: On Fri, 2 Sep 2011 00:23:00 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. All those HTTP socket handlers are still open and consuming freenet threads. They were initiated by wget localhost:/USK... type calls -- and they probably failed because the sites were old. Normal browser access to control localhost: does still close the socket properly. Well what are they doing then? Still running the requests? This is a fundamental problem with fetching stuff over HTTP from Freenet with a low timeout - if your tool moves on to add more requests, the old requests haven't failed, they are still going. They will go on forever? Fproxy will never close them? (Sounds pretty easy to DDOS that?) And why didn't this happen before? No, they go on until they complete. There is a limit on the total number of connections handling requests, iirc the default is 100. Well, I just checked -- all the 80 connections that were opened a week ago are still open and still in CLOSE_WAIT. What does until they complete mean? The thread on Freenet's side will continue until it fetches the data. After that it *should* close the socket. So, to DOS freenet, I simply need to ask it to fetch old / not-fully-existent content? Also, if I kept my wget spider running, it could easily use 213 or over, like it did when I first reported the problem, and eventually not let me back into fproxy :s. How does that fit into the 100 request limit? Fproxy stops accepting more connections after 100 are running. How does that explain the 213 I originally saw? And why wasn't I able to access fproxy, without restarting my node? And why didn't this happen to me before with earlier builds -- I've had my spider running for months. (Why isn't there a time limit, or an hop-limit again?) There is. ? Having said that it may eventually be possible to detect connection closed - in 0.5 there was a hack for it. I think tcp's CLOSE_WAIT means fproxy should have already gotten a close signal, no? Surprisingly enough, we are not directly generating TCP packets here... Huh? I meant, (I'm guessing), didn't my wget already send a FIN tcp message to fproxy at some point, which is what put those connections into CLOSE-WAIT? (a la http://www.tcpipguide.com/free/t_TCPConnectionTermination-2.htm ), or am I missing something? As I said before, we are not writing TCP packets directly. We are using a socket API. It is therefore somewhat painful to get notified when the socket is closed, if we are not actually reading from it - which we won't be while handling a request. I believe things have been fixed in 1404. (Many threads (~50) do linger for a while -- I'm not sure if this occurred before as well, but they do eventually close. With the past few builds they remained open forever
Re: [freenet-support] http fproxy ports are not closed
On Fri, 9 Sep 2011 09:05:55 -0400, Dennis Nezic wrote: On Fri, 9 Sep 2011 13:00:30 +0100, Matthew Toseland wrote: On Wednesday 07 Sep 2011 21:35:44 Dennis Nezic wrote: On Wed, 7 Sep 2011 17:50:36 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 15:34:30 Dennis Nezic wrote: On Fri, 2 Sep 2011 14:40:22 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 13:20:39 Dennis Nezic wrote: On Fri, 2 Sep 2011 00:23:00 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. All those HTTP socket handlers are still open and consuming freenet threads. They were initiated by wget localhost:/USK... type calls -- and they probably failed because the sites were old. Normal browser access to control localhost: does still close the socket properly. Well what are they doing then? Still running the requests? This is a fundamental problem with fetching stuff over HTTP from Freenet with a low timeout - if your tool moves on to add more requests, the old requests haven't failed, they are still going. They will go on forever? Fproxy will never close them? (Sounds pretty easy to DDOS that?) And why didn't this happen before? No, they go on until they complete. There is a limit on the total number of connections handling requests, iirc the default is 100. Well, I just checked -- all the 80 connections that were opened a week ago are still open and still in CLOSE_WAIT. What does until they complete mean? The thread on Freenet's side will continue until it fetches the data. After that it *should* close the socket. So, to DOS freenet, I simply need to ask it to fetch old / not-fully-existent content? Also, if I kept my wget spider running, it could easily use 213 or over, like it did when I first reported the problem, and eventually not let me back into fproxy :s. How does that fit into the 100 request limit? Fproxy stops accepting more connections after 100 are running. How does that explain the 213 I originally saw? And why wasn't I able to access fproxy, without restarting my node? And why didn't this happen to me before with earlier builds -- I've had my spider running for months. (Why isn't there a time limit, or an hop-limit again?) There is. ? Having said that it may eventually be possible to detect connection closed - in 0.5 there was a hack for it. I think tcp's CLOSE_WAIT means fproxy should have already gotten a close signal, no? Surprisingly enough, we are not directly generating TCP packets here... Huh? I meant, (I'm guessing), didn't my wget already send a FIN tcp message to fproxy at some point, which is what put those connections into CLOSE-WAIT? (a la http://www.tcpipguide.com/free/t_TCPConnectionTermination-2.htm ), or am I missing something? As I said before, we are not writing TCP packets directly. We are using a socket API. It is therefore somewhat painful to get notified when the socket is closed, if we are not actually reading from it - which we won't be while handling a request. I believe things have been fixed in 1404. (Many threads (~50) do linger for a while -- I'm not sure if this occurred before as well, but they do eventually close. With the past few builds they remained open forever!) ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org
Re: [freenet-support] http fproxy ports are not closed
On Fri, 9 Sep 2011 13:00:30 +0100, Matthew Toseland wrote: On Wednesday 07 Sep 2011 21:35:44 Dennis Nezic wrote: On Wed, 7 Sep 2011 17:50:36 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 15:34:30 Dennis Nezic wrote: On Fri, 2 Sep 2011 14:40:22 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 13:20:39 Dennis Nezic wrote: On Fri, 2 Sep 2011 00:23:00 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. All those HTTP socket handlers are still open and consuming freenet threads. They were initiated by wget localhost:/USK... type calls -- and they probably failed because the sites were old. Normal browser access to control localhost: does still close the socket properly. Well what are they doing then? Still running the requests? This is a fundamental problem with fetching stuff over HTTP from Freenet with a low timeout - if your tool moves on to add more requests, the old requests haven't failed, they are still going. They will go on forever? Fproxy will never close them? (Sounds pretty easy to DDOS that?) And why didn't this happen before? No, they go on until they complete. There is a limit on the total number of connections handling requests, iirc the default is 100. Well, I just checked -- all the 80 connections that were opened a week ago are still open and still in CLOSE_WAIT. What does until they complete mean? The thread on Freenet's side will continue until it fetches the data. After that it *should* close the socket. So, to DOS freenet, I simply need to ask it to fetch old / not-fully-existent content? Also, if I kept my wget spider running, it could easily use 213 or over, like it did when I first reported the problem, and eventually not let me back into fproxy :s. How does that fit into the 100 request limit? Fproxy stops accepting more connections after 100 are running. How does that explain the 213 I originally saw? And why wasn't I able to access fproxy, without restarting my node? And why didn't this happen to me before with earlier builds -- I've had my spider running for months. (Why isn't there a time limit, or an hop-limit again?) There is. ? Having said that it may eventually be possible to detect connection closed - in 0.5 there was a hack for it. I think tcp's CLOSE_WAIT means fproxy should have already gotten a close signal, no? Surprisingly enough, we are not directly generating TCP packets here... Huh? I meant, (I'm guessing), didn't my wget already send a FIN tcp message to fproxy at some point, which is what put those connections into CLOSE-WAIT? (a la http://www.tcpipguide.com/free/t_TCPConnectionTermination-2.htm ), or am I missing something? As I said before, we are not writing TCP packets directly. We are using a socket API. It is therefore somewhat painful to get notified when the socket is closed, if we are not actually reading from it - which we won't be while handling a request. ___ 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] http fproxy ports are not closed
On Wed, 7 Sep 2011 17:50:36 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 15:34:30 Dennis Nezic wrote: On Fri, 2 Sep 2011 14:40:22 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 13:20:39 Dennis Nezic wrote: On Fri, 2 Sep 2011 00:23:00 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. All those HTTP socket handlers are still open and consuming freenet threads. They were initiated by wget localhost:/USK... type calls -- and they probably failed because the sites were old. Normal browser access to control localhost: does still close the socket properly. Well what are they doing then? Still running the requests? This is a fundamental problem with fetching stuff over HTTP from Freenet with a low timeout - if your tool moves on to add more requests, the old requests haven't failed, they are still going. They will go on forever? Fproxy will never close them? (Sounds pretty easy to DDOS that?) And why didn't this happen before? No, they go on until they complete. There is a limit on the total number of connections handling requests, iirc the default is 100. Well, I just checked -- all the 80 connections that were opened a week ago are still open and still in CLOSE_WAIT. What does until they complete mean? Also, if I kept my wget spider running, it could easily use 213 or over, like it did when I first reported the problem, and eventually not let me back into fproxy :s. How does that fit into the 100 request limit? (Why isn't there a time limit, or an hop-limit again?) Having said that it may eventually be possible to detect connection closed - in 0.5 there was a hack for it. I think tcp's CLOSE_WAIT means fproxy should have already gotten a close signal, no? Surprisingly enough, we are not directly generating TCP packets here... Huh? I meant, (I'm guessing), didn't my wget already send a FIN tcp message to fproxy at some point, which is what put those connections into CLOSE-WAIT? (a la http://www.tcpipguide.com/free/t_TCPConnectionTermination-2.htm ), or am I missing something? ___ 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] http fproxy ports are not closed
On Fri, 2 Sep 2011 00:23:00 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. All those HTTP socket handlers are still open and consuming freenet threads. They were initiated by wget localhost:/USK... type calls -- and they probably failed because the sites were old. Normal browser access to control localhost: does still close the socket properly. ___ 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] http fproxy ports are not closed
On Fri, 2 Sep 2011 14:40:22 +0100, Matthew Toseland wrote: On Friday 02 Sep 2011 13:20:39 Dennis Nezic wrote: On Fri, 2 Sep 2011 00:23:00 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. All those HTTP socket handlers are still open and consuming freenet threads. They were initiated by wget localhost:/USK... type calls -- and they probably failed because the sites were old. Normal browser access to control localhost: does still close the socket properly. Well what are they doing then? Still running the requests? This is a fundamental problem with fetching stuff over HTTP from Freenet with a low timeout - if your tool moves on to add more requests, the old requests haven't failed, they are still going. They will go on forever? Fproxy will never close them? (Sounds pretty easy to DDOS that?) And why didn't this happen before? Having said that it may eventually be possible to detect connection closed - in 0.5 there was a hack for it. I think tcp's CLOSE_WAIT means fproxy should have already gotten a close signal, no? ___ 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] http fproxy ports are not closed
On Wed, 31 Aug 2011 15:02:14 -0400, Dennis Nezic wrote: On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. Upon further consideration, I think it might actually be a bug. For one thing, this never happened with earlier pre-1401ish versions. For another thing, why are there so many sockets open, when my wget client has long since closed and exited? (it has been about half an hour now -- I'll provide updates if they ever do close.) CLOSE_WAIT apparently means fproxy got the FIN signal from my wget, but didn't close it's end? I'm still not sure exactly how this bizarre behavior (of not closing sockets) starts -- because if I restart freenet, and do a simple wget transaction, the socket does get properly closed. ___ 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] http fproxy ports are not closed
netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. ___ 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] http fproxy ports are not closed
On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote: netstat (netstat -pnat | grep java) shows 213 connections to my fproxy at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I could no longer access fproxy -- probably because of some thread or connection limit. I'm not exactly sure how to reproduce this -- it's not simply a matter of opening a connection to fproxy. False alarm. I think my freenet wget spider got out of control. Apologies. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] How to update Freenet manually?
On Sat, 20 Aug 2011 05:14:32 +, Moses wrote: Hi, I am in a network that blocked the domain freenetproject.org so I can't update Freenet directly by running update.cmd in the Freenet directory. And also, can't keeps Freenet running 24 hours a day. So how to update Freenet to the latest build. or change update.cmd to use a Freenet mirror? Is tor.eff.org also blocked? Perhaps you can use tor to access the uncensored web. Or other open proxies? Is http://code.google.com/p/freenet/downloads/list blocked? If you trust toad/any of the freenet devs, you could find their GPG key, (make sure it's their's) and ask them to send you the file directly, then verify their signature of the sent file. (You can also consider using linux distros, which use their own mirrors for packages :). I'm sure there are many other creative (and not so creative) possibilities. ___ 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] Freenet 0.7.5 build 1393
On Mon, 8 Aug 2011 19:29:27 +0100, Matthew Toseland wrote: Freenet 0.7.5 build 1393 is now available, please upgrade, it will be mandatory on Wednesday. Changes include: Is it mandatory already? That bug I mentioned about a week ago here, high (crippling) IO came back, coincidentally around the time 1393 got released, and I had trouble connecting. (I update manually via my distro.) ___ 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] Wondering about darknets security
On Tue, 26 Jul 2011 14:15:35 +0100, Matthew Toseland wrote: Basically, you are vulnerable to your peers (those other freenet nodes your node connects to). They know your IP address - they have to to connect to you. They can identify you. As you rightly point out, your peers can also, with a fair bit of work, and on various plausible assumptions, identify much of what you are doing on Freenet. When will premix routing and tunneling and onion routing be implemented? ___ 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] Wondering about darknets security
On Thu, 28 Jul 2011 11:51:12 -0400, Evan Daniel wrote: [...] To summarize: Lowest security, easiest to set up: run opennet. Marginal improvement: run a hybrid Opennet/Darknet node. Mostly this should be treated as a transition point to full Darknet, or a way to help out your Darknet-only friends. Better security, somewhat harder to set up: run Darknet, and connect to anyone you personally know and don't believe to be cooperating with the Bad Guys. Still better security, even harder to set up: Be more picky about your Darknet peers. Best security: Immolate your computer on a pyre of thermite, and go live in a cave somewhere. [...] I couldn't find the immolate-option during the installation wizard. ___ 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] Anecdotal: High IO when unable to connect to peers
This is somewhat anecdotal and sparse on details, but probably something significant. I have noticed that whenever I have trouble connecting to peers, ie. when my version becomes too old to connect to the mainstream nodes (I update my node manually -- gentoo package), the disk IO skyrockets and my computer becomes bogged down (uptime values of 15 +), and I'm forced to kill the node. With the latest mandatory 1388, (and my 1386), I'm actually not exactly sure if it's a peer-connectivity (with some kind of disk-io hook? -- perhaps related to the node trying to fetch the newer jars), or if it's normal while the node is starting up. Either way, I can't start 1386 now, due to really high IO. I'll test again when I get 1388 to install. ___ 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] [freenet.uservoice.com] New message: 'Could you please set the colour atribute…'
On Sun, 17 Jul 2011 17:21:31 +, no-re...@uservoice.com wrote: Could you please set the colour atribute where you have set the background colour. I'm using a dark theme and can't read the main site easily because the background is set to white while the colour attribute is left undefined (white by (my) default). Ahh... /that/ age-old problem. IMHO it's a losing battle trying to get designers to do things properly. Just force your colors in your browser. (I'm sure they can all do it, either in their preferences, or their stylesheets.) ___ 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] help
- Forwarded Message - From: cem sarrac csar...@yahoo.com To: support@freenetproject.org support@freenetproject.org Sent: Saturday, June 25, 2011 5:07 PM Subject: help WrapperManager Error: Error in WrapperListener.start callback.java.lang.IllegalArgumentException: No enum const class freenet.support.Logger$LogLevel.WARN_NG Looks like you have an invalid logger argument WARN_NG. Were you playing around with logging? My guess: remove instances of that from your freenet.ini file, and try starting freenet again. ___ 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] help regarding freesites!
On Sat, 11 Jun 2011 18:26:14 +0530, Madhurya Kakati wrote: Hi, If I insert a freesite using jsite tool or a flog using floghelper tool will the site remain available even if my node is offline? Yes. Freenet basically is a free (as in free beer) web hosting service, that can even handle massively popular sites; for free. The data is stored redundantly across many *other* nodes -- not your own. (Freenet also incidentally provides anonymity and is immune to censorship.) ___ 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] Freenet node troubles
On Mon, 30 May 2011 15:31:17 -0600, Pablo Arroyo wrote: Hello, I wish you could help me with some problems I am facing with my Freenet node. I have looked all over the FAQs and googling, but get no right answers. Please excuse me, I am not a native English speaker. The main problem I am facing is that after accidentally uninstalling freenet, and then installing it again, Freenet fails to connect. If I try to start freenet, I will get Firefox failed to connect to 127.0.0.1:. Then after 8-10 seconds, freenet stops running. I am guessing this is a problem caused by the port used by Freenet before and after installing it, but I could be wrong, since I am not an expert. Please, could you guide me in how to change the ports Freenet connects to, or guide me to a solution for my porblems? I appreciate your time in reading this, I know you have other stuff to attend to. I really wish you could reply to my message, it would be very kind of you. Thanks a lot, a former Freenet user wanting to use this amazing service again. Have a look at your wrapper.log file in your Freenet directory -- it will probably tell you (near the end of the file) what the problem is. ___ 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] High disk IO
On Wed, 11 May 2011 17:48:36 +0100, Matthew Toseland wrote: On Wednesday 11 May 2011 02:31:51 Dennis Nezic wrote: On Fri, 6 May 2011 15:55:59 -0400, Dennis Nezic wrote: On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote: On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote: For the past several builds, I'm not sure exactly when the issue started, before build01364 at least, my node experiences quite high disk IO, which bogs down my computer. I think once I left it alone, and it resolved itself after a few hours, but usually I have to restart Freenet to make my server more useable. My vmstat 5 reports bi (bytes-in, that is: reading) between 4000-1. (Under 100 after I stop Freenet.) My graphs[1] show it to be suspiciously periodic, although that might just be a coincidence. Is there some kind of background (periodic) database/datastore task that might be causing this? My wrapper.log shows no output during these events, nor does fproxy say that anything is going on. Active downloads/uploads? Yep ... a few active downloads -- about 30MBs each. (One got completed much earlier in the day -- but nothing unusual was happening during the problem peaks.) It happened again last night [2][3], suspiciously almost exactly 24 hours after the last time. I didn't stop my node this time, and it fixed itself (at least the plateau) after over 2 hours, although disk IO was still quite high throughout the night [2] and early morning. [1] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io.jpg [2] That's what she said. [3] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io-2.jpg It definitely seems daily/periodic... it seems to occur pretty much every single day at 8pm. It just happened an hour ago, for example, and resulted in load average: 7.09, 6.12, 5.38 which seriously bogged down my system, so I had to kill/restart my node :\. Ideas? Maybe you could get a stack dump during that period? My stack dumps didn't show anything glaringly wrong. (No (or just once a) BLOCKED threads.) However, I think the problem has to do with FMS -- shutting down FMS stopped the high-IO. (The reason why I originally suspected Freenet was involved, however, was because stopping my node also seemed to stop the IO a few seconds afterwards.) I'm still not sure whether it's purely an FMS bug (perhaps having to do with my 150MB fms.db3 file), or some kind of FMS-Freenet interaction. I will try to investigate further. ___ 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] High disk IO
On Fri, 6 May 2011 15:55:59 -0400, Dennis Nezic wrote: On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote: On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote: For the past several builds, I'm not sure exactly when the issue started, before build01364 at least, my node experiences quite high disk IO, which bogs down my computer. I think once I left it alone, and it resolved itself after a few hours, but usually I have to restart Freenet to make my server more useable. My vmstat 5 reports bi (bytes-in, that is: reading) between 4000-1. (Under 100 after I stop Freenet.) My graphs[1] show it to be suspiciously periodic, although that might just be a coincidence. Is there some kind of background (periodic) database/datastore task that might be causing this? My wrapper.log shows no output during these events, nor does fproxy say that anything is going on. Active downloads/uploads? Yep ... a few active downloads -- about 30MBs each. (One got completed much earlier in the day -- but nothing unusual was happening during the problem peaks.) It happened again last night [2][3], suspiciously almost exactly 24 hours after the last time. I didn't stop my node this time, and it fixed itself (at least the plateau) after over 2 hours, although disk IO was still quite high throughout the night [2] and early morning. [1] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io.jpg [2] That's what she said. [3] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io-2.jpg It definitely seems daily/periodic... it seems to occur pretty much every single day at 8pm. It just happened an hour ago, for example, and resulted in load average: 7.09, 6.12, 5.38 which seriously bogged down my system, so I had to kill/restart my node :\. Ideas? ___ 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] High disk IO
On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote: On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote: For the past several builds, I'm not sure exactly when the issue started, before build01364 at least, my node experiences quite high disk IO, which bogs down my computer. I think once I left it alone, and it resolved itself after a few hours, but usually I have to restart Freenet to make my server more useable. My vmstat 5 reports bi (bytes-in, that is: reading) between 4000-1. (Under 100 after I stop Freenet.) My graphs[1] show it to be suspiciously periodic, although that might just be a coincidence. Is there some kind of background (periodic) database/datastore task that might be causing this? My wrapper.log shows no output during these events, nor does fproxy say that anything is going on. Active downloads/uploads? Yep ... a few active downloads -- about 30MBs each. (One got completed much earlier in the day -- but nothing unusual was happening during the problem peaks.) It happened again last night [2][3], suspiciously almost exactly 24 hours after the last time. I didn't stop my node this time, and it fixed itself (at least the plateau) after over 2 hours, although disk IO was still quite high throughout the night [2] and early morning. [1] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io.jpg [2] That's what she said. [3] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io-2.jpg ___ 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] High disk IO
For the past several builds, I'm not sure exactly when the issue started, before build01364 at least, my node experiences quite high disk IO, which bogs down my computer. I think once I left it alone, and it resolved itself after a few hours, but usually I have to restart Freenet to make my server more useable. My vmstat 5 reports bi (bytes-in, that is: reading) between 4000-1. (Under 100 after I stop Freenet.) My graphs[1] show it to be suspiciously periodic, although that might just be a coincidence. Is there some kind of background (periodic) database/datastore task that might be causing this? My wrapper.log shows no output during these events, nor does fproxy say that anything is going on. [1] http://dennisn.dyndns.org/guest/pubstuff/freenet-periodic-high-io.jpg ___ 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] /tmp/ is flooded with bloom* and libNativeThread* files
On Sat, 30 Apr 2011 18:47:25 +0200, Roland Häder wrote: So I guess freenet kills itself by filling up the whole RAM disk with tons of bloom-xxx.tmp and libNativeThread-amd64xx.tmp files? Please check this out, why freenet is not deleting its temporary files. I still get leftover(?) bloom-*.tmp files, sometimes, possibly when I restart after a JVM did not exit on request, terminated, but not always, on a normal disk /tmp folder. ___ 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] headless install on OpenSolaris
On Sun, 1 May 2011 23:18:07 -0500, Daxter wrote: After running the last command, the text below was printed over the period of 10-20 minutes. I'm not sure what's going wrong, [...] java.io.IOException: No space left on device Perhaps you don't have enough space on your freenet device? :p ___ 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] JVM restart every few minutes - prng.seed missing
On Sat, 16 Apr 2011 01:26:49 +0200, ml-...@gmx.de wrote: FProxy shows me 'There isn't enough entropy available' for hours. It looks like the wrapper restart the jvm every few minutes. If the problem is with entropy, you can try running a large I/O operation, like find / or something. You might also want to try rngd (rng-tools).[1] You can find how much entropy your system has available by: cat /proc/sys/kernel/random/entropy_avail, with 100-200 or less probably being too low [1] http://linux.die.net/man/8/rngd ___ 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] JVM restart every few minutes - prng.seed missing
On Sat, 16 Apr 2011 01:26:49 +0200, ml-...@gmx.de wrote: '(freenet.crypt.Yarrow, WrapperListener_start_runner, ERROR): IOE trying to read the seedfile from disk : /opt/freenet/prng.seed (No such file or directory)' Also, you might want to make sure that that file /opt/freenet/prng.seed exists and has proper permissions for freenet to read it? :p ___ 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] Freetalk is out! (build 1360)
On Tue, 29 Mar 2011 13:36:43 +0100, Matthew Toseland wrote: Freetalk and WebOfTrust are now loadable from the Plugins page on the fproxy web interface. Can it communicate with FMS? ___ 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] Freenet 0.7.5 build 1362
On Thu, 31 Mar 2011 01:15:45 +0100, Matthew Toseland wrote: Freenet 0.7.5 build 1362 is now available. This is a relatively minor build (2 builds actually, including 1361). Changes: - New versions of WebOfTrust and Freetalk. - Fixes needed by WebOfTrust, Freetalk or FlogHelper (the last is not yet official but will be very soon). - German translation update. - New theme, rabbit-hole. Do any of the changes have to do with Freenet, or just the plugins? (Aren't plugins supposed to be separate things?) ___ 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] Bloom filter files
Are they important/helpful? I still sometimes get 6 leftover 500KB /tmp/bloom-***.tmp files. My wrapper.log says something like: Initializing CHK Datastore (460332 keys) Bloomfilter (freenet.support.CountingBloomFilter@..) for CHK-store is loaded. Datastore(CHK-store) is dirty. ___ 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] Bloom filter files
On Tue, 15 Mar 2011 23:03:45 +, Matthew Toseland wrote: On Tuesday 15 Mar 2011 21:22:00 Dennis Nezic wrote: Are they important/helpful? I still sometimes get 6 leftover 500KB /tmp/bloom-***.tmp files. My wrapper.log says something like: Initializing CHK Datastore (460332 keys) Bloomfilter (freenet.support.CountingBloomFilter@..) for CHK-store is loaded. Datastore(CHK-store) is dirty. They are created when we rebuild the bloom filters. When the store-io branch eventually lands, these will be no more. Are those files still necessary? If not, why are they still there? (Where are the bloom filters stored anyways, btw?) ___ 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] [freenet.uservoice.com] New message: 'I have a fibre line as well as 10 TB of …'
On Sat, 12 Mar 2011 11:16:40 -0600, no-re...@uservoice.com wrote: I have a fibre line as well as 10 TB of sapce I can devote to freenet. Would be swell if I could devote 10TB rather than the max of 300GB I wonder if all of Freenet can fit in those 10TB :D. Or if the size of Freenet can be mathematically estimated from a few random node samples. ___ 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] [freenet.uservoice.com] New message: 'I have a fibre line as well as 10 TB of …'
On Sat, 12 Mar 2011 13:56:31 -0500, Dennis Nezic wrote: On Sat, 12 Mar 2011 11:16:40 -0600, no-re...@uservoice.com wrote: I have a fibre line as well as 10 TB of sapce I can devote to freenet. Would be swell if I could devote 10TB rather than the max of 300GB I wonder if all of Freenet can fit in those 10TB :D. Or if the size of Freenet can be mathematically estimated from a few random node samples. Handwaving, since nodes are supposed to specialize over a specific key range, and assuming keys are equally distributed across the entire key-space, perhaps your 3% datastore utilization is a result of a small freenet. Ie. a node can only store (specialized-key-range-percentage * sizeof-freenet) gigs of data. If that's the case, the only way to increase your datastore would be to broaden your key-storing-range, but I don't think that would help, since freenet routing currently requires key specialization. Further handwaving, I wonder if it would be such a bad idea to support supernodes, with broader key specializations. For example, would it be a bad thing for a node to store the entire freenet? ___ 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] attention users of both freenet networks
On Tue, 01 Mar 2011 14:20:03 +0100, Jep wrote: Matthew Toseland : On Thursday 24 Feb 2011 23:27:01 Nomen Nescio wrote: you have a right to know USK@1WZPo6qZmlCpi6rZWjtz~kig1gcpcnzh5drmqpW9L8Q,ksaFFDkSJfnOXB3ppYhQ2R14z3W QCYxGqXNERCYcHD0,AQACAAE/wordsoftoad/-1/ I'm only going to say this once. First off, it was nearly 5 years ago. Second, I made it clear in the post and the extensive discussion at the time that Hereticnet and Freenet are (hypothetically) *two* *different* *networks*, using different (albeit related) software. No need to defend, Matthew. The idea of internal censorship may be a lousy one, at least it sounds like that to me. But the conclusion our anonymous crusader starts out with: 'proof of his hypocrisy' and you not to be trusted, is pretty ridicilous. Were you indeed not to be trusted, you wouldn't have done this brainstorming about a sort of censorship-from-the-inside in the open, and were you out on implementing whatever backdoor in FN in order to expose users, you'd surely not published about it at all. That's exactly what I would do, if I was a malicious uber-coder, to win your trust :D. ___ 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] local cache
On Tue, 1 Mar 2011 14:40:54 +0100, folkert wrote: Hi, Is it possible to somehow look into the local cache/datastore of a freenetnode to determine what files it hosts? Both metadata and data. Yes, of course. But everything is sliced up and encrypted, so you can only know what it is if the file has been published, so that you know what the chunks belong to. ___ 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] local cache
On Tue, 1 Mar 2011 09:20:50 -0500, Dennis Nezic wrote: On Tue, 1 Mar 2011 14:40:54 +0100, folkert wrote: Hi, Is it possible to somehow look into the local cache/datastore of a freenetnode to determine what files it hosts? Both metadata and data. Yes, of course. But everything is sliced up and encrypted, so you can only know what it is if the file has been published, so that you know what the chunks belong to. (Or even if it hasn't been publically published, if you already have the file (with the same filename), since non-random CHK files are unique to a specific file.) ___ 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] seednode
On Tue, 1 Mar 2011 20:06:37 +0100, folkert wrote: Is a seednode doing 25KB/s (and hardly any inserts) usefull for freenet? And am I right that this bandwidth is shared with the rest of the local freenet activity? Ok I discussed it with my hoster (excellent hoster by the way: www.soleus.nu) and got a green light for 50KB/s. So if I set node.opennet.acceptSeedConnections=true and node.inputBandwidthLimit=25600 node.outputBandwidthLimit=25600 and we've got us a new seed-node doing no more than 50KB/s? Freenet doesn't strictly obey the incoming bandwidth limit, given the nature of the UDP protocol. But, it will try to. ___ 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] attention users of both freenet networks
On Sat, 26 Feb 2011 09:06:31 +0100, David ‘Bombe’ Roden wrote: On Saturday 26 February 2011 01:01:34 Dennis Nezic wrote: USK@1WZPo6qZmlCpi6rZWjtz~kig1gcpcnzh5drmqpW9L8Q,ksaFFDkSJfnOXB3ppYhQ2R14z 3WQCYxGqXNERCYcHD0,AQACAAE/wordsoftoad/-1/ I can't access this freesite. Despite hours of trying. (Other freesites seem to work fine.) That’s because an edition hint of -1 will never look for edition 0. Thanks! Regarding the site, I just hope nobody quotes anything I said 5 years ago :P. (The community-censorship idea proposed was retarded, yes.) ___ 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] attention users of both freenet networks
On Sat, 26 Feb 2011 21:11:20 +0100, David ‘Bombe’ Roden wrote: On Saturday 26 February 2011 16:04:41 Dennis Nezic wrote: The community-censorship idea proposed was retarded, yes. On the contrary, some form of community-based censorship can be required for smaller communities to run Freenet in order to keep a “clean” network (by whatever standards). Well, clean and anonymity (free speech) are mutually exclusive. I guess one first has to be clear about one's priorities. ___ 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] Bitcoin
On Thu, 24 Feb 2011 17:33:40 +, Matthew Toseland wrote: On Sunday 09 Jan 2011 14:06:15 ma...@anikin.us wrote: Hi, You should consider taking donations in Bitcoin and other anonymous/pseudonanymous currencies in addition to USD. There are a lot of like-minded people in the anonymous digital currency community. We now accept bitcoin, in case you missed the announcement. Very cool. ___ 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] safe?
On Sun, 20 Feb 2011 21:05:14 +0100, folkert wrote: which file is the database? can I (securely) delete it every time and will it then still remember the options set? and is it possible to select where it stores this messages database? The sqlite3 (fms.db3) file. It contains all your options/identities, as well as saved forum messages and trust lists. It probably would be handy if it could be stored already encrypted on disk, but as you suggest, it's not essential. I don't think you can change where it gets saved -- not even via (sym)linking. (Because, I think, when it defragments the database, it recreates and overwrites the existing db.) ___ 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] couple of questions
On Fri, 18 Feb 2011 15:34:46 +0100, folkert wrote: Odd: I always get a password error. There is a known bug[0] that makes it impossible to login with a username containing a -, even though accounts can be created with those names. Aah ok, that indeed is then the issue. That was one of the issues. The other was an incorrect hostname and portnumber for FCP. So my freemail address is: folk...@vanheusden.com.freemail (Just a side note, IMHO short freemail addresses are a bug, and shouldn't be allowed in future versions. They are trivial to spoof, and increase the odds that things won't work (by having another rare (KSK) key to fetch.)) ___ 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] idea
On Fri, 18 Feb 2011 19:01:10 +0100, folkert wrote: What about that the freenet daemon periodically (configurable/disable-ble of course) announces itself on the lan(s) to which it is connected? That way freenet-nodes can interconnect and speed up distribution of data. Data distribution on Freenet doesn't work like that. Data segments are actually spread all across Freenet, ideally with no particular peer having a large portion of a large splitfile. I don't think having fast random LAN connections would speed things up -- the bottleneck will still be the LAN's connection to the Internet. (Not to mention the fact that it would be at least somewhat less secure. (Better chance of traffic analysis and such tricks against you.)) ___ 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] idea
On Fri, 18 Feb 2011 21:35:00 +0100, folkert wrote: Well I was thinking maybe in the future we're all using mesh networking over wifi (or whatever wireless protocol we then have). http://en.wikipedia.org/wiki/Mesh_networking Freenet-Darknet should work wonderfully over such a network :). (Well, assuming you're not roaming. And that the meshes aren't too isolated :p). Ok, that was not your point :-) Ok currently maybe not too many nodes in the net but maybe this changes when governments restrict access to what you can browse. Here in Europe governments already start talking about installing filters. This is why you /don't/ want any kind of broadcasting, or any other kind of leak of identifiable traffic. Just encrypted non-identifiable noise. Currently only for kiddy porn but I'm afraid that when such a filter is in place the step to block certain political views or so is much smaller. Obviously. Their (Statist's) worst enemy is the free flow of information. It is also a matter of convenience. If I visit some conference I don't want to be hassled with the need of configuring all kinds of software just to get work done. It's a tradeoff -- ease-of-use and anonymity. ___ 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] couple of questions
On Wed, 16 Feb 2011 13:10:17 +0100, folkert wrote:
I believe the long address (and possibly short address) are
originally stored in the Inbox of Freemail's imap server, if you
manage to connect to it.
Connecting to it is challenging. Evolution refuses it, mutt too.
set imap_user=myusername
set spoolfile={172.29.0.1:3143}INBOX
set folder={172.29.0.1:3143}~/mail
Those spoolfile and folder values look a little funny to me. I think
they should be something like
set spoolfile=imap://127.0.0.1/INBOX
set record=imap://127.0.0.1/INBOX.Trash
Odd: I always get a password error.
That's progress :). The password is whatever you set it to when you
created your Freemail account. (It is listed in Freemail's
data/myusername/accprops file, as an md5 hash. You can verify you have
the right one, or hack in a new one :p, by: echo -n 'mypwd' | md5sum.)
___
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] couple of questions
On Tue, 15 Feb 2011 22:01:59 +0100, folkert wrote:
I've got a couple of questions:
1. when creating an e-mail account, it always says it cannot
create the short address. so what is then my freenet e-mail
address?
I believe the long address (and possibly short address) are
originally stored in the Inbox of Freemail's imap server, if you
manage to connect to it.
Connecting to it is challenging. Evolution refuses it, mutt too.
set imap_user=myusername
set spoolfile={172.29.0.1:3143}INBOX
set folder={172.29.0.1:3143}~/mail
Those spoolfile and folder values look a little funny to me. I think
they should be something like
set spoolfile=imap://127.0.0.1/INBOX
set record=imap://127.0.0.1/INBOX.Trash
(Assuming you're running Freemail locally, or have a local ssh tunnel
to it. You can't use other ip-addresses because Freemail by default
binds only to 127.0.0.1, as set in it's globalconfig file. For good
reason! :p)
(You also probably need to set smtp_url.)
2. maybe it is nice to have some kind of address directory in
which one can register his/her address together with some
(personal- or other) info. maybe with a picture or so. whatever.
Great idea!
No idea how to implement that de-centralized. Also you don't want to
depend on 1 server keeping it up-to-date.
One way might be to have a spider, or person, collect vcard or any
other kind of information from freesites / freetalk/fms forums / etc,
and then make a freesite-directory :).
How does the freenet forum work?
There are 2.5 current independent forum systems in the wild. FMS,
Freetalk and Frost. They work well. (FMS the best. /me ducks/ :).
4. maybe it is an idea to add a list of listening ports to the
'list of plugins'-page
You mean the ports that plugins (like Freemail) might use?
Correct!
Good idea. In the meantime, you can run netstat -pna | grep java,
assuming Freenet is the only java app running.
___
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] Please test the new load management branch
On Sun, 30 Jan 2011 00:30:09 +, Matthew Toseland wrote: Please get the snapshot (update.cmd testing / update.sh testing), and test it. I want to know if it causes serious problems, and also any other bugs you run into. I know there will be various errors, but I am still interested in the more severe ones. For people building from source: The tag is: testing-build-1340-maybe-merge-new-load-management-pre1 The branch is: merge-new-load-management The git rev is 47edfe611a1f088b51fccb36d3e7710e28c3d2b8 (that commit does matter despite it appearing to be a logging fix). THANKS! Freenet 0.7.5 Build #1339 testing-build-1340-maybe-merge-new-load-management-pre1 nodeUptime: 21h46m bwlimitDelayTime: 1200ms nodeAveragePingTime: 422ms backedOffPercent: 3.2% (This value can vary a lot, from 2 to 8% in the same min.) pInstantReject: 0.0% Session Transfer Rate averages seem low. Which is probably resulting in my transfers taking longer than before. The Output Rate session average, for example, is less than half of what I set it to. (There still hasn't been any flooding though ;p, since 1339. So kudos for that.) The Input Rate average at about 80% my limit. Resent Bytes / Sessian Total Output = 17% Outher Output = 10% Total non-request overhead = 20% Preemptive Rejection Reasons 605 SUB_MAX_PING_TIME 505 Insufficient input bandwidth 432 Input bandwidth liability: fairness between peers 304 Output bandwidth liability: fairness between peers 152 MAX_PING_TIME Local Preemptive Rejection Reasons 4224Insufficient input bandwidth 1593Input bandwidth liability: fairness between peers 789 SUB_MAX_PING_TIME 726 MAX_PING_TIME 234 Output bandwidth liability: fairness between peers Routing Backoff Reason (bulk) Count Avg. Time Total Time SendSyncTimeout 32 42.923s 22m53s Timeout 12 33.892s 6m46s AcceptedTimeout 747 9.450s 1h57m AfterInsertAcceptedTimeout 6 8.268s 49.612s ForwardRejectedOverload226 6.087s 2m38s ForwardRejectedOverload 13964.862s 1h53m Timeout330 3.934s 1m58s TransferFailedInsert108 3.202s 5m45s FatalTimeout38 2.499s 1m34s ForwardRejectedOverload583 2.359s 3m15s TransferFailedRequest5 356 2.230s 13m13s TimedOutAwaitingDataInsert 4 1.871s 7.485s Timeout22 1.366s 2.732s ForwardRejectedOverload323 1.211s 27.865s InsertTimeoutNoFinalAck 54 1.154s 1m2s TransferFailedRequest7 85 1.025s 1m27s AfterInsertAcceptedRejectedTimeout 1 0.877s 0.877s TransferFailedRequest9 1 0.713s 0.713s ForwardRejectedOverload43 0.415s 1.247s Routing Backoff Reason (realtime) Count Avg. Time Total Time SendSyncTimeout 32 53.974s 28m47s AcceptedTimeout 526 10.333s 1h30m FatalTimeoutForked 1 6.498s 6.498s ForwardRejectedOverload 730 5.666s 1h8m FatalTimeout268 3.199s 14m17s TransferFailedRequest5 12111.962s 39m36s TransferFailedInsert3 1.227s 3.682s ForwardRejectedOverload2202 1.173s 3m56s TransferFailedRequest7 16 0.894s 14.306s Transfer Backoff Reason (bulk) Count Avg. Time Total Time SENDER_DIED 325 1m18s 7h3m RequestSenderGetOfferedTransferFailed 1 6.398s 6.398s Transfer Backoff Reason (realtime) Count Avg. Time Total Time SENDER_DIED 619 4m18s 1d20h Group P(Success) Count All requests23.798% 108,940 Local CHKs 53.452% 25,466 Remote CHKs 16.266% 10,451 Local SSKs 28.819% 34,671 Remote SSKs 1.622% 38,352 Block transfers (Bulk) 94.785% 13,690 Block transfers (RT)70.935% 4,483 Block transfers (Local) 88.368% 15,406 Transfers timed out 91.970% 1,893 Bulk sends 99.409% 1354 ___ 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] Freenet 0.7.5 build 1339
On Sat, 29 Jan 2011 01:54:47 +, Matthew Toseland wrote: Build 1339 is out. Please upgrade asap, it will be mandatory on Monday. The main change in this build is that backoff is now separate for realtime versus bulk requests. This means, hopefully, that if the performance problems recently have been caused by realtime requests causing lots of backoff, this will only affect realtime requests. It is investigating a theory, one of several, regarding the recent problems. I am sorry that the network has behaved so badly recently, I am working on it, but it is not easy. Please upgrade, and please report any and all problems you find. There is a thread on FMS where I am trying to get a better understanding of what problems people are seeing. So far the main reported issues seem to be: - Realtime requests (e.g. fproxy) are slow, and cause all or most peers to get backed off. - Downloads are very slow. - Bootstrapping onto the network is slow. I'm getting lots and lots of Timeouts and Overloads in my stranger-status details, although not too many BackOffs. After over an hour of uptime, my bandwidth usage hasn't really stabilized. Even the upload speeds, which used to be quite stable around my 15KB/s limit, are very bumpy, quite often near 2KB/s. Same with my download speeds. (Although, at least they aren't flooding :p.) In general, whenever I look at my strangers, most of them will be: FatalTimeout/SENDER_DIED FatalTimeout/TransferFailedInsert FatalTimeout/AfterInsertAcceptedTimeout FatalTimeout/ForwardRejectedOverload2 I've seen a bunch of InsertTimeoutNoFinalAck, TransferFailedRequest (5,13). Is this abnormal, or normal congenstion control? I also see that the ping times to my strangers are very high, 300ms-1000 +ms, even though I can ping google under 20ms. I don't know if this is abnormal, or perhaps all my peers are on the other side of the planet, or perhaps the value is calculated differently. Also, perhaps unrelated, why was I being connected to 11 peers, with a 15KB/s connection? Isn't that too high? Although, even after I halved this, nothing much changed. ___ 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
