From bff685f7ca80c2745ac60467e86b3863ef181d50 Mon Sep 17 00:00:00 2001 From: zzz Date: Tue, 10 Jun 2008 14:05:55 +0000 Subject: [PATCH] * Throttle: Use BANDWIDTH rather than CRIT as the rejection reason at startup, so peers don't list us as failing. --- history.txt | 2 ++ router/java/src/net/i2p/router/RouterThrottleImpl.java | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/history.txt b/history.txt index 5d3eda0d9..379ed92fa 100644 --- a/history.txt +++ b/history.txt @@ -7,6 +7,8 @@ - Don't publish bw stats in first hour of uptime - Publish floodfill stats even if other stats are disabled - Changes not effective until 0.6.2.1 to provide cover. + * Throttle: Use BANDWIDTH rather than CRIT as the rejection reason at + startup, so peers don't list us as failing. * graphs.jsp: Fix a bug where it tries to display the combined bandwidth graph when it isn't available diff --git a/router/java/src/net/i2p/router/RouterThrottleImpl.java b/router/java/src/net/i2p/router/RouterThrottleImpl.java index cfe11e8ad..c44e9be1b 100644 --- a/router/java/src/net/i2p/router/RouterThrottleImpl.java +++ b/router/java/src/net/i2p/router/RouterThrottleImpl.java @@ -91,8 +91,9 @@ class RouterThrottleImpl implements RouterThrottle { return TunnelHistory.TUNNEL_REJECT_CRIT; } + // Don't use CRIT because we don't want peers to think we're failing if (_context.router().getUptime() < 20*60*1000) - return TunnelHistory.TUNNEL_REJECT_CRIT; + return TunnelHistory.TUNNEL_REJECT_BANDWIDTH; long lag = _context.jobQueue().getMaxLag(); // reject here if lag too high???