- Oct 05, 2012
-
-
zzz authored
-
- Sep 28, 2012
-
-
zzz authored
-
- Nov 28, 2011
- Nov 09, 2011
-
-
zzz authored
-
- Oct 31, 2011
-
-
zzz authored
- Restore and implement lengthOverride() - Adjust quantity override
-
- Oct 25, 2011
-
-
zzz authored
- Make most classes package private - Final, static, logs, cleanups - Consolideate createRateStat calls - Add getTotalLength() - Remove unused lengthOverride()
-
- May 06, 2011
-
-
zzz authored
- Increase max fast and high-cap tier sizes - Slow profile eval cycle after sufficient uptime - Fix bug which started a new build after a successful build - Misc. cleanups
-
- May 16, 2010
-
-
zzz authored
-
- Jul 13, 2009
-
-
zzz authored
Under the one-packet-enough theory, and the fact that most tunnels in a x+1 pool are of length x, variable lengths don't really help that much. Also, a default of 1 led to all sorts of problems with iMule/SAM, who was not setting the variance properties. This will affect exploratory tunnels for new users, and those that have never saved a change on configtunnels.jsp, and iMule users 1.4.5 and earlier.
-
- Jul 01, 2009
-
-
zzz authored
for efficiency (thanks Arsene for the suggestion)
-
- Apr 21, 2009
-
-
sponge authored
* Code janator work, basic corrections involving @Override, and appling final where it is important. Also fixed some equals methods and commented places that need fixing.
-
- Mar 07, 2008
-
-
zzz authored
- Prevent peers with matching IPs from joining same tunnel. Match 0-4 bytes of IP (0=off, 1=most restrictive, 4=least). Default is 2 (disallow routers in same /16). Set with router.defaultPool.IPRestriction=x - Comment out unused RebuildPeriod pool setting - Add random key to pool in preparation for XOR peer ordering
-
- Dec 09, 2005
-
-
* Create different strategies for exploratory tunnels (which are difficult to create) and client tunnels (which are much easier) * Gradually increase number of parallel build attempts as tunnel expiry nears. * Temporarily shorten attempted build tunnel length if builds using configured tunnel length are unsuccessful * React more aggressively to tunnel failure than routine tunnel replacement * Make tunnel creation times randomized - there is existing code to randomize the tunnels but it isn't effective due to the tunnel creation strategy. Currently, most tunnels get built all at once, at about 2 1/2 to 3 minutes before expiration. The patch fixes this by fixing the randomization, and by changing the overlap time (with old tunnels) to a range of 2 to 4 minutes. * Reduce number of excess tunnels. Lots of excess tunnels get created due to overlapping calls. Just about anything generated a call which could build many tunnels all at once, even if tunnel building was already in process. * Miscellaneous router console enhancements
-
- Nov 23, 2005
-
- Feb 16, 2005
-
-