[freenet-support] support request

[Martin Scheffler]

Am Samstag, 7. Januar 2006 19:56 schrieb danilo salieri:
> Dear Freenet supporters,
> after a crash my Freenet (on Win XP SP2) doesn't start anymore but
> keeps telling 'Freenet is starting...please wait'. I tried reinstalling
> it (saving the datastore) and reseeding but nothing happens, it seems I
> can't reach any nodes nor I can't get recognized. Any help would be
> much appreciated. This is the log message:
> ava.io.EOFException
>   at
> freenet.support.io.ReadInputStream.readUTFChar(ReadInputStream.java:223
>) at
> freenet.support.io.ReadInputStream.readToEOF(ReadInputStream.java:134)
> at
> freenet.support.io.CommentedReadInputStream.readToEOF(CommentedReadInpu
>tStream.java:45) at
> freenet.support.io.ReadInputStream.readToEOF(ReadInputStream.java:184)
> at freenet.FieldSet.privParse(FieldSet.java:521)
>   at freenet.FieldSet.parseFields(FieldSet.java:454)
>   at freenet.FieldSet.parseFields(FieldSet.java:390)
>   at freenet.FieldSet.(FieldSet.java:83)
>   at freenet.node.Main.loadNodeFile(Main.java:2950)
>   at freenet.node.Main.main(Main.java:515)
> Thanks in advance

your problem is a corrupted node file.
remove the file named "node" in the freenet install directory, and freenet 
creates a new one on restart. sadly your old established connections 
break and your node has to re-integrate. but, it will work again.
and the experience of your node is not at zero, because your node has 
still the old routing information.

good byte
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: 

Re: [freenet-support] support request

[Martin Scheffler]

Am Samstag, 7. Januar 2006 19:56 schrieb danilo salieri:
 Dear Freenet supporters,
 after a crash my Freenet (on Win XP SP2) doesn't start anymore but
 keeps telling 'Freenet is starting...please wait'. I tried reinstalling
 it (saving the datastore) and reseeding but nothing happens, it seems I
 can't reach any nodes nor I can't get recognized. Any help would be
 much appreciated. This is the log message:
 ava.io.EOFException
   at
 freenet.support.io.ReadInputStream.readUTFChar(ReadInputStream.java:223
) at
 freenet.support.io.ReadInputStream.readToEOF(ReadInputStream.java:134)
 at
 freenet.support.io.CommentedReadInputStream.readToEOF(CommentedReadInpu
tStream.java:45) at
 freenet.support.io.ReadInputStream.readToEOF(ReadInputStream.java:184)
 at freenet.FieldSet.privParse(FieldSet.java:521)
   at freenet.FieldSet.parseFields(FieldSet.java:454)
   at freenet.FieldSet.parseFields(FieldSet.java:390)
   at freenet.FieldSet.init(FieldSet.java:83)
   at freenet.node.Main.loadNodeFile(Main.java:2950)
   at freenet.node.Main.main(Main.java:515)
 Thanks in advance

your problem is a corrupted node file.
remove the file named node in the freenet install directory, and freenet 
creates a new one on restart. sadly your old established connections 
break and your node has to re-integrate. but, it will work again.
and the experience of your node is not at zero, because your node has 
still the old routing information.

good byte


pgpmwQyQdaE9a.pgp
Description: PGP signature
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Virtual Memory Minimum Too Low

[Martin Scheffler]

  Unfortunately, because of the absurd way in which the Windows VMM
  allocates memory, the more physical RAM you have, the more swap you
  must add. (About 1.5x physical RAM is a typical value for the minimum
  pagefile size.) Having less swap than physical memory is very bad
  because Windows wants to allocate a page of swap for every page of
  physical memory which gets allocated. If you've got 2048MB RAM and
  128MB swap, it'll start complaining bitterly as soon as your memory
  usage exceeds 128MB.

 Actually Linux does this too. IIRC the recommended setting is 2x RAM
 for swap on linux. :)

no, this is not true! your linux will behave a lot more consistent 
(compared to windows) when you only supply 2MB of swap - or even no swap.
the recommendation is just a rule of thumb, supplying more does not make 
much sense, because your machine will swap for ages if you really use the 
space. supplying less than 2xRAM is not as painful as with windows.

ok, even linux swaps out unuses memory pages occasionally, but they are 
still mapped, until it is really needed to remap the pages.

pro:
- preemptive swapout is done in idle condition
- when RAM gets tight, some of the swapping is already done

con:
- memory+swap may show more than 100% of allocated memory

good byte


pgpzYifLrdJKm.pgp
Description: PGP signature
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] new ip (was can't listen on local interfaces..)

[Martin Scheffler]

 If everything else is the same, a change in IP address shouldn't
 matter.  That's what ARKs are for.

ARKs are not being used anymore - they were of no use :-)

good byte


pgpjj0PvusxyK.pgp
Description: PGP signature
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] How does the noderef work?

[Martin Scheffler]

Am Saturday, 14. August 2004 12:42 schrieb Garb:
 ...
 I am running Freenet with do announce, which I figure has the purpose
 of telling the world that I exist and would like to be added to other
 peoples list of nodes. At the same time I assume that I am building up
 my own internal list of good contact nodes by simply surfing Freenet
 and thus interacting with the network.
That is correct.

 But whenever I update, I get two files - the jar and a much lager
 noderef. Assuming that the latter contains a list of known good
 contact nodes, will this file then overwrite the one I have in my
 system already? Or maybe append itself to it? Or is it simply discarded
 by my node because it already has one?
The seednodes.ref file is overwritten on update, this is ok because 
nodes come and go. On startup, the node decides if it knows about enough 
neighbours, otherwise some noderefs from the seednodes file are added to 
the routing table (you can see that at the first lines in the log (not) 
seeding routing table).
If you want to force a reseed, you just have to give the seednodes.ref a 
later modification date than the routing table files (load and save the 
file without modification).


 If the one I've built by running and using Freenet simply gets
 overwritten by the noderef, wouldt that mean that my node have to
 integrate itself into the network from scratch everytime I update?
No. The routing table is saved in different files (the ones named *_a and 
*_b). The seednodes.ref is only used as primer.

 To add to my confusion, I've noticed that people often get the advice
 to re-seed when complaining about too many RNF's, and they are even
 provided with a special link for that. Isnt re-seed what we all do
 automatically everytime we update? Is the noderef from that special
 link better than the one I get every time I upgrade?
This link points to the very same file, which is loaded by the automatic 
updater. After the download, the automatic updater changes the 
modification time into the past, to avoid reseeding on every startup. As 
long as the existing routing table is healthy, reseeding may degrade the 
routing quality.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Startup times

[Martin Scheffler]

Am Sonntag, 8. August 2004 13:48 schrieb Anonymous:
 ...
 yes, disk is in full thrash.. cpu maxed.  other processes grinding to a
 halt.
 ...
 64mb (best this mb will do)
 ...

Sorry to say that, but just forget this for now.
My node is P1/200 with 128MB of RAM (Gentoo Linux) and i had to choke it 
really hard to get it working more than 12 hours without restart.
(Now it does, but not very powerful operation)

It's not really the speed, the RAM matters.

btw. if you could obtain 32MB PS2-Simms or even 64MB chips, you may give 
your computer more (i'm quite sure), but these chips are hard to get now, 
they are ancient in computer evolution terms.

good byte


pgpMShgg6t0Uh.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

[freenet-support] h

[Martin Scheffler]

Am Dienstag, 10. August 2004 21:41 schrieb Steve:
 Can it hurt the network if I make my datastore too big?

short answer: No!

long answer: The store fills up when your node serves requests from others 
and you (the user). If a requested key is already in the store, your node 
just sends this and makes no request on his own for that. When the store 
is full, the least recently used key(s) is/are purged to make room. A 
bigger store means more keys are available, so chances to find requested 
keys in the store increase, this is _GOOD_ for the network.

( might only overflow your own hard disk if configured insane :-) )

good byte
berny [EMAIL PROTECTED]


pgph4g26X2fpg.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

[freenet-support] oops

[Martin Scheffler]

sorry, messed up the last mail a bit, but the text is valid!

good byte


pgpkft2zi46m6.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] access freenet

[Martin Scheffler]

Am Dienstag, 10. August 2004 20:23 schrieb Ralph Towner:
 Can you please help me.  For years I've never had problems to connect
 to freenet, but since some days ago I can't anymore. What could be the
 problem? I include my logfile.
 Thanks!

The seednodes.ref file is quite big nowadays. that is the reason for the 
OutOfMemory messages which do lobotomize your node before starting up.

Please use an editor of your choice and cut the file down to only some few 
megabytes; then restart.

this shall be fixed with stable version 5091, until then, use this method.

good byte


pgpPOnXJ6rxIc.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] datastore size

[Martin Scheffler]

Am Mittwoch, 11. August 2004 00:55 schrieb Michael Kuijn:
 On Tuesday 10 August 2004 21:41, Steve wrote:
  Can it hurt the network if I make my datastore too big?

 Not really, but enlarging your datastore all the time will prevent
 specialisation. This isn't real bad, but specialisation improves
 routing. If I were you I would let it specialise at one point.

Sorry, but forget that. In Freenet there is no thing like a one peak 
specialisation for more than one minute.
And when the network can hold more data, it increases the lifetime of 
seldom requested keys.
Specialization changes over time, anyway.

The only drawback may be that your ubernode becomes popular over time 
because of more successful replies :-) (much connections increase request 
ability aswell)

Routing does not get better when your node has to purge old keys on new 
requests - maybe they are requested just one minute later - more net 
load :-(

good byte


pgpty6uif4ja1.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] datastore size

[Martin Scheffler]

Am Mittwoch, 11. August 2004 01:06 schrieb Derek Ferguson:
 Hmmm. Am I wrong to think there probably is an optimal store size for
 each node?
Sorry, yes.

 My thinking is that as the store grows, the node draws more requests,
 which at some point will exceed the node's ability to service them all
 in a timely manner due to resource limits (probably bandwidth).

 As the store grows larger, even more requests come in, causing the node
 to service a shrinking proportion of the total number of requests
 directed towards it, which has a negative impact on the network.

The first is the request success rate (which makes your node attractive), 
another measure (request rate limiting) tells the other nodes to reduce 
the requests/time, to balance out all the peers with your avaiable 
bandwidth.

A big store is good (even for yourself).

good byte


pgp3utfkDm14e.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] on-the-fly storesize change

[Martin Scheffler]

Am Mittwoch, 4. August 2004 13:45 schrieb [EMAIL PROTECTED]:
 Hi,
 i changed the storesize in freenet.ini while running Freenet. When
 Freenet checked the file at the next time, it generated the following
 error message:


 04.08.2004 13:36:02 (freenet.node.NodeConfigUpdater, YThread-59,
 ERROR): Option storeSize changed to 1024M but no handler was available.
 java.lang.NoSuchMethodException:
 freenet.node.NodeConfigUpdater$ConfigOptions.storeSize()
 ...

Yes, but that is not fatal to the running node. It just means you have to 
stop and restart your node make this change.

 Freenet 5089 under WinXP, Sun Java 1.41_07

Well, this does not change the message from above, but you should really 
upgrade your JVM to something like 1.4.2_05; there are strange effects 
with older JVMs from time to time.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] anonymity(NOT)

[Martin Scheffler]

Kendy Kutzner wrote:
 On 2004-08-04T14:50:52+0200, Zenon Panoussis wrote:
  Traffic
  analysis might help me figure who made a request and who served
  it, but I still have to break encryption before I can figure
  which file that request concerned.

 That is not entirely true. The files are encrypted with keys
 based on the file's content. When the file content is known, then
 routing keys can be computed.

No, this description is inaccurate!
When you know the _exact_ file contents, you don't need freenet. And 
besides, the very same text or data with just one bit changed is a new 
key, this means you are only able to scan for well-known data.

The SHA1 hash from the original and unencrypted data is used as encryption 
key. The data is encrypted with that (You can not get back the encryption 
key without decrypting first).

Then, some other data is added for routing and checking, and the SHA1 hash 
of the whole piece makes up the routing key, this is what you see while 
proxying and caching the key data.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Re: on-the-fly storesize change

[Martin Scheffler]

Am Mittwoch, 4. August 2004 19:13 schrieb Manfred Huber:
 Yes, but that is not fatal to the running node. It just means you have
 to stop and restart your node make this change.

 So what's the place to report non-fatal bugs and observations?

This is not really a bug, it's just not implemented to change the store 
size on-the-fly (so far). Maybe it should be noted in the error message.

This list is the right place to discuss observations and problems.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Must Freenet load on login?

[Martin Scheffler]

Am Sonntag, 1. August 2004 07:58 schrieb Nick Tarleton:
 I run Freenet stable on Windows XP. Whenever I log in, the Freenet
 systray application loads and starts Freenet. This is annoying, to say
 the least, because I'm not connected to the Internet most of the time.
 I can't find what is telling Windows to load it. Is there any way to
 make the systray application *not* load on login?

Look into your start-menu, under all programs. There, you should find a 
folder named start up or autostart. Remove the Freenet entry, and on 
the next login, you will notice that it does not do so anymore.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Freenet not starting on Mandrake 10 + J2SE 1.4.2_05

[Martin Scheffler]

Am Mittwoch, 4. August 2004 02:01 schrieb Scott Call:
 I get the following when I run start-freenet under mandrake 10 (log
 level debug):
 ...

Please, leave LogLevel at Normal or Minor. LogLevel=debug will rather 
make your node inoperatable, because of the vast amount of messages it 
spits out.

There is another statement in the .conf (or .ini on windows) that 
specifies which subclasses to debug, when using LogLevel=normal.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] starting probs

[Martin Scheffler]

Am Sonntag, 11. Juli 2004 15:50 schrieb rensinghoff:
 Thank you soo much for your help.. I LOVE OPEN SOURCE PEOPLE !!!

another free hint: you posted your user-id along with your password.
you should now change the password as soon as possible :-)

good byte


pgpdmkaNh1pAY.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Access the web interface from remote machines.

[Martin Scheffler]

On Wednesday 09 June 2004 01:26, Weiliang Zhang wrote:
 Hi there,

 I'm trying to access running on a remote machine through the web
 interface, so I modified the following line in the freenet.conf on the
 remote machine:

 fcpHosts=127.0.0.1,ip_address_of_my_machine

 Is that all I need to do? It didn't work for me... :

That line is only for FCP (port 8481 standard).

try mainport.allowedHosts=...

good byte


pgpYF3xWFdDnn.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] alert

[Martin Scheffler]

On Sunday 06 June 2004 18:51, Robert Greenage wrote:
 I received the following Alert while I was in the process of d/l one
 image that was part of a larger file. I was connected to freenet at the
 time. Any thoughts?


 The connection was refused when attempting to contact  127.0.0.1:

This happens, when you start too many connections to FProxy/FCP at once.
Then, the node closes the port until the load dropped a bit.
You should make less requests at once.

good byte


pgpmLgaIAaIMR.pgp
Description: signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Re: Limiting outgoing connections to a certain port range...

[Martin Scheffler]

 I checked on that before posting to the list, and the module is only
 valid in the OUTPUT chain. Since Freenet sends data both ways it's not
 much use for this.

I use this -m owner match, it works well and is sufficient. There is no 
point in limiting the input rate (well, at least in most setups), because the 
packets already arrived at your box, when you limit them.
The peers slow down after some time, but when your box starts to drop packets 
you even lose more bandwith for retransmission.

When you have asymmetric connection, the uplink will be the harder problem.

good byte
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]