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

2004-08-14 Thread 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]


[freenet-support] How does the noderef work?

2004-08-14 Thread Garb
Hi.


I am at a bit of a loss as to how the noderef is managed by the individual
Freenet node and the upgrade script.

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.

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?

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?

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?


Regards,
J

___
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]