On Tuesday 07 September 2010 19:33:33 Robert Hailey wrote: > > On Sep 3, 2010, at 7:31 AM, Matthew Toseland wrote: > > > We need more seednodes again! If you can run a seednode, please > > email me your opennet noderef. You must: > > - Turn on "be a seednode" in advanced opennet config. > > - Have a static IP address or a reliable DNS name in your noderef. > > - Be port forwarded. > > - Have your node up roughly 24x7. > > > > The load on the seednodes is rather high at the moment because of > > lots of new nodes. More seednodes will spread this around and make > > it more manageable. Also, all seednode operators should upgrade to > > 1276-pre1 (update.sh testing / update.cmd testing). It has some > > important code for announcement load limiting. Thanks. > > I remember a time ago when I restarted my node I was surprised to see > it bootstrapping / announcing. I was under the assumption that process > should only occur for a freshly-downloaded node. Otherwise, we can cut > the load on the seed nodes by eliminating a seasoned nodes reliance on > them.
No, unfortunately life isn't that easy. It may be possible to reduce the usage of seednodes by old opennet nodes, perhaps by allowing seed-style limited connections to peers you've previously been opennet peers of even when we don't allow them to actually reconnect, but it certainly won't be possible to eliminate it. Your opennet peers may have changed IP address, may be offline, may be NATed and not sending to you, etc. Plus, we want to reconnect *QUICKLY*, meaning we can't afford to wait a long time for reconnections. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20100911/34b31358/attachment.pgp>
