On Wed, 12 Jan 2011 00:01:34 +0000, Matthew Toseland wrote:
> 1324 introduced many changes including some bugfixes and some big
> changes related to timeouts and telling other peers about the node's
> current status. Unfortunately it was buggy, and has been withdrawn.
> 1325 just includes the bugfixes. 1326 will be another try at the
> original big changes. Please upgrade to 1325, for now. Thanks.

These builds still don't really respect our bandwidth limits. Could it
be that the node tries to keep the *session's average rate* at our
limit, instead of the "instantaneous" rate? If so, that is still quite
unacceptable. (Among many other reasons, if my ISP connection goes down
for a bit (it does), and drops my session average, upon re-connection,
my node will consume all (or too much) bandwidth to try to bring the
average back up.) In any case, as the setting says, "Freenet should
<strike>almost</strike> never exceed [the configured bandwidth limit]."
_______________________________________________
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

Reply via email to