Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
>> when the node starts up, the rt gets cleaned, so no bad refs are left. >> then, while the node is running only good refs are added to the rt. >>=20 >> then why are connections from incompatible (e.g. stable/unstable) nodes i= >n the OCM? >> because they contacted us? >> then why aren't they rejected for using an incompatible protocol? > >Their queries are rejected. Their connections are not rejected because >we don't exchange that info at connection time. We don't close the >connections because they'd only retry. that makes some sense at the expense of (since muxing not so) valuable connection slots, system resources, etc... the connection backoff from Trevor Smith might be useful for this kind of stuff also, maybe a additional fnp answer at connection time could be designed: "never contact me again" which will make out node remove the node which answers us this from the rt, so we won't retry the node as it's permanently unusable ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
On Wed, Jan 14, 2004 at 11:43:29PM +0100, [EMAIL PROTECTED] wrote: > >> then wrong noderefs can only slip into the rt when the local rt already h= > >as these bad references (e.g. when switching von unstable->stable or the ot= > >her way around without purging the rt) or when importing new=20 > >> seednodes which contain these bad refs. > >>=20 > >> would it be useful if the local routing table would be checked on node st= > >artup if every ref is suited for the build? if there is such a check when a= > >dding refs while the node is running, then this check logic would be=20 > >> reusable at startup time, wouldn't it? > > > >It is. > > errr.. then i just don't get it > > when the node starts up, the rt gets cleaned, so no bad refs are left. > then, while the node is running only good refs are added to the rt. > > then why are connections from incompatible (e.g. stable/unstable) nodes in the OCM? > because they contacted us? > then why aren't they rejected for using an incompatible protocol? Their queries are rejected. Their connections are not rejected because we don't exchange that info at connection time. We don't close the connections because they'd only retry. > > sorry for bothering you and flooding the list, but i imagine i've seen some > confusion on the list too. well.. dev that is -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
>> then wrong noderefs can only slip into the rt when the local rt already h= >as these bad references (e.g. when switching von unstable->stable or the ot= >her way around without purging the rt) or when importing new=20 >> seednodes which contain these bad refs. >>=20 >> would it be useful if the local routing table would be checked on node st= >artup if every ref is suited for the build? if there is such a check when a= >dding refs while the node is running, then this check logic would be=20 >> reusable at startup time, wouldn't it? > >It is. errr.. then i just don't get it when the node starts up, the rt gets cleaned, so no bad refs are left. then, while the node is running only good refs are added to the rt. then why are connections from incompatible (e.g. stable/unstable) nodes in the OCM? because they contacted us? then why aren't they rejected for using an incompatible protocol? sorry for bothering you and flooding the list, but i imagine i've seen some confusion on the list too. well.. dev that is ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
On Wed, Jan 14, 2004 at 11:31:23PM +0100, [EMAIL PROTECTED] wrote: > >> why not have some sanity checks when importing seed files or adding node = > >refs to the routing table? we'll all be luckier with this and in the long r= > >un the generated seednode files are much less polluted (why aren't=20 > > > >We do. > > oh, good :) > > then wrong noderefs can only slip into the rt when the local rt already has these > bad references (e.g. when switching von unstable->stable or the other way around > without purging the rt) or when importing new > seednodes which contain these bad refs. > > would it be useful if the local routing table would be checked on node startup if > every ref is suited for the build? if there is such a check when adding refs while > the node is running, then this check logic would be > reusable at startup time, wouldn't it? It is. > > >> they filtered after retrieving and combining for the official seednodes ?= > >!?) > > > >Because I didn't get around to it... > > i just remembered you asking Conrad Sabatier if he or someone else could write such > a 'cleanup' script which removes lines from a seednode file not matching a regexp. i > think thats a nice idea and would provide > reliable seednodes... someone came around with this? -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
>> why not have some sanity checks when importing seed files or adding node = >refs to the routing table? we'll all be luckier with this and in the long r= >un the generated seednode files are much less polluted (why aren't=20 > >We do. oh, good :) then wrong noderefs can only slip into the rt when the local rt already has these bad references (e.g. when switching von unstable->stable or the other way around without purging the rt) or when importing new seednodes which contain these bad refs. would it be useful if the local routing table would be checked on node startup if every ref is suited for the build? if there is such a check when adding refs while the node is running, then this check logic would be reusable at startup time, wouldn't it? >> they filtered after retrieving and combining for the official seednodes ?= >!?) > >Because I didn't get around to it... i just remembered you asking Conrad Sabatier if he or someone else could write such a 'cleanup' script which removes lines from a seednode file not matching a regexp. i think thats a nice idea and would provide reliable seednodes... someone came around with this? ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
On Wed, Jan 14, 2004 at 11:06:48PM +0100, [EMAIL PROTECTED] wrote: > i have seen some stable nodes with connections to unstable nodes, unstable nodes > with connections to stable nodes, seednodes for stable nodes with unstable > references, seednodes for unstable nodes with > stable references, you get the idea. why are stable nodes connecting AT ALL to > unstable nodes and vice versa? they use incompatible protocols IIRC, so why should > they even *try* to connect to incompatible > nodes?!? > > why not have some sanity checks when importing seed files or adding node refs to the > routing table? we'll all be luckier with this and in the long run the generated > seednode files are much less polluted (why aren't We do. > they filtered after retrieving and combining for the official seednodes ?!?) Because I didn't get around to it... > > *scratches head* i see no sense in the current noderef politics. > > >I am running stable with 5058. I got the new node set at 5054, but I'm not > >at all sure those node are all stable (have my doubts). > > > > > >> [Original Message] > >> From: Toad <[EMAIL PROTECTED]> > >> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > ><[EMAIL PROTECTED]> > >> Date: 1/14/2004 3:16:32 PM > >> Subject: [freenet-support] Re: [freenet-dev] Please help: seednode sources > >> > >> It appears several nodes in the unstable list are running stable, and > >> several nodes in the stable list are running unstable. Would ALL persons > >> whose nodes are currently used as seednode sources please contact me and > >> tell me the URL and which branch it is currently running please. > >> > >> On Wed, Jan 14, 2004 at 08:08:07PM +, Toad wrote: > >> > We need more sources of seednodes for the new stable branch. Please mail > >> > me with the URL to fetch seednodes from. It must be accessible from > >> > dodo.freenetproject.org (by IP), but it need not be visible to the rest > >> > of the internet. You can do this by setting: > >> > mainport.allowedHosts=127.0.0.0/8,212.13.198.248 > >> > in your freenet.conf. Note that this technically means that we can > >> > browse through your node and break your anonymity, so you may want to > >> > do it on nodes you don't use for important browsing :) > >> -- > >> Matthew J Toseland - [EMAIL PROTECTED] > >> Freenet Project Official Codemonkey - http://freenetproject.org/ > >> ICTHUS - Nothing is impossible. Our Boss says so. > > > > > > > >___ > >Support mailing list > >[EMAIL PROTECTED] > >http://news.gmane.org/gmane.network.freenet.support > > > > ___ > Support mailing list > [EMAIL PROTECTED] > http://news.gmane.org/gmane.network.freenet.support -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] Re: [freenet-dev] Please help: seednode sources
On Wed, Jan 14, 2004 at 11:06:48PM +0100, [EMAIL PROTECTED] wrote: > i have seen some stable nodes with connections to unstable nodes, unstable nodes > with connections to stable nodes, seednodes for stable nodes with unstable > references, seednodes for unstable nodes with > stable references, you get the idea. why are stable nodes connecting AT ALL to > unstable nodes and vice versa? they use incompatible protocols IIRC, so why should > they even *try* to connect to incompatible > nodes?!? Because they have an old ref. We don't terminate the connection immediately because they'd only retry. > > why not have some sanity checks when importing seed files or adding node refs to the > routing table? we'll all be luckier with this and in the long run the generated > seednode files are much less polluted (why aren't > they filtered after retrieving and combining for the official seednodes ?!?) > > *scratches head* i see no sense in the current noderef politics. > > >I am running stable with 5058. I got the new node set at 5054, but I'm not > >at all sure those node are all stable (have my doubts). > > > > > >> [Original Message] > >> From: Toad <[EMAIL PROTECTED]> > >> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > ><[EMAIL PROTECTED]> > >> Date: 1/14/2004 3:16:32 PM > >> Subject: [freenet-support] Re: [freenet-dev] Please help: seednode sources > >> > >> It appears several nodes in the unstable list are running stable, and > >> several nodes in the stable list are running unstable. Would ALL persons > >> whose nodes are currently used as seednode sources please contact me and > >> tell me the URL and which branch it is currently running please. > >> > >> On Wed, Jan 14, 2004 at 08:08:07PM +, Toad wrote: > >> > We need more sources of seednodes for the new stable branch. Please mail > >> > me with the URL to fetch seednodes from. It must be accessible from > >> > dodo.freenetproject.org (by IP), but it need not be visible to the rest > >> > of the internet. You can do this by setting: > >> > mainport.allowedHosts=127.0.0.0/8,212.13.198.248 > >> > in your freenet.conf. Note that this technically means that we can > >> > browse through your node and break your anonymity, so you may want to > >> > do it on nodes you don't use for important browsing :) > >> -- > >> Matthew J Toseland - [EMAIL PROTECTED] > >> Freenet Project Official Codemonkey - http://freenetproject.org/ > >> ICTHUS - Nothing is impossible. Our Boss says so. > > > > > > > >___ > >Support mailing list > >[EMAIL PROTECTED] > >http://news.gmane.org/gmane.network.freenet.support > > > > ___ > Support mailing list > [EMAIL PROTECTED] > http://news.gmane.org/gmane.network.freenet.support -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
RE: [freenet-support] Re: [freenet-dev] Please help: seednode sources
i have seen some stable nodes with connections to unstable nodes, unstable nodes with connections to stable nodes, seednodes for stable nodes with unstable references, seednodes for unstable nodes with stable references, you get the idea. why are stable nodes connecting AT ALL to unstable nodes and vice versa? they use incompatible protocols IIRC, so why should they even *try* to connect to incompatible nodes?!? why not have some sanity checks when importing seed files or adding node refs to the routing table? we'll all be luckier with this and in the long run the generated seednode files are much less polluted (why aren't they filtered after retrieving and combining for the official seednodes ?!?) *scratches head* i see no sense in the current noderef politics. >I am running stable with 5058. I got the new node set at 5054, but I'm not >at all sure those node are all stable (have my doubts). > > >> [Original Message] >> From: Toad <[EMAIL PROTECTED]> >> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; ><[EMAIL PROTECTED]> >> Date: 1/14/2004 3:16:32 PM >> Subject: [freenet-support] Re: [freenet-dev] Please help: seednode sources >> >> It appears several nodes in the unstable list are running stable, and >> several nodes in the stable list are running unstable. Would ALL persons >> whose nodes are currently used as seednode sources please contact me and >> tell me the URL and which branch it is currently running please. >> >> On Wed, Jan 14, 2004 at 08:08:07PM +, Toad wrote: >> > We need more sources of seednodes for the new stable branch. Please mail >> > me with the URL to fetch seednodes from. It must be accessible from >> > dodo.freenetproject.org (by IP), but it need not be visible to the rest >> > of the internet. You can do this by setting: >> > mainport.allowedHosts=127.0.0.0/8,212.13.198.248 >> > in your freenet.conf. Note that this technically means that we can >> > browse through your node and break your anonymity, so you may want to >> > do it on nodes you don't use for important browsing :) >> -- >> Matthew J Toseland - [EMAIL PROTECTED] >> Freenet Project Official Codemonkey - http://freenetproject.org/ >> ICTHUS - Nothing is impossible. Our Boss says so. > > > >___ >Support mailing list >[EMAIL PROTECTED] >http://news.gmane.org/gmane.network.freenet.support ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
RE: [freenet-support] Re: [freenet-dev] Please help: seednode sources
I am running stable with 5058. I got the new node set at 5054, but I'm not at all sure those node are all stable (have my doubts). > [Original Message] > From: Toad <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Date: 1/14/2004 3:16:32 PM > Subject: [freenet-support] Re: [freenet-dev] Please help: seednode sources > > It appears several nodes in the unstable list are running stable, and > several nodes in the stable list are running unstable. Would ALL persons > whose nodes are currently used as seednode sources please contact me and > tell me the URL and which branch it is currently running please. > > On Wed, Jan 14, 2004 at 08:08:07PM +, Toad wrote: > > We need more sources of seednodes for the new stable branch. Please mail > > me with the URL to fetch seednodes from. It must be accessible from > > dodo.freenetproject.org (by IP), but it need not be visible to the rest > > of the internet. You can do this by setting: > > mainport.allowedHosts=127.0.0.0/8,212.13.198.248 > > in your freenet.conf. Note that this technically means that we can > > browse through your node and break your anonymity, so you may want to > > do it on nodes you don't use for important browsing :) > -- > Matthew J Toseland - [EMAIL PROTECTED] > Freenet Project Official Codemonkey - http://freenetproject.org/ > ICTHUS - Nothing is impossible. Our Boss says so. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
