Wouldn't you be able to help this by increasing your default *maxRoutingSteps?*
From:
fish <[EMAIL PROTECTED]>
Date:
Thu, 14 Nov 2002 23:33:06 +1100 (EST)
anyhow, offtopic, i have a theory that this should also help with the
streaming stuff, too, since the reason why I was getting RNF's is that I
was running into the load balancing code of fred - whereas I used to be
able to stream 16kbps audio at htl=15 with only 20 simeltaneous threads,
now it's needing to push 40 or so, and when I hit 30, bang, RNF city. even at 24 threads, i'm often hitting try=5 and similar such largish
numbers, but at least not try=20.
/Name:/ *maxRoutingSteps* (--maxRoutingSteps)
/Arguments:/ <integer>
/Default val:/ 40
/Description: / The maximum number or node refs that will be used to route a request before RNFing.
Increasing your *rtMaxNodes* might help as well so that you don't run out of nodes to contact.
/Name:/ *rtMaxNodes* (--rtMaxNodes)
/Arguments:/ <integer>
/Default val:/ 50
/Description: / The number of unique nodes that can be contained in the routing table.
However, I have tried increasing my *initialRequestHTL *but that parameter seems to be ignored and hardwired to 15 somewhere. I know that it does not ignore rtMaxNodes but I can't say anything about maxRoutingSteps.
Mike
_______________________________________________
devl mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
