- Dec 18, 2004
-
-
- Dec 16, 2004
-
-
* Catch another oddball case for a reset connection in the streaming lib. * Add a dumpprofile.jsp page, called with ?peer=base64OfPeerHash, which dumps the current state of that peer's profile. Instead of the full base64, you can pass in however many characters you have and it will return the first match found. -
* Catch another oddball case for a reset connection in the streaming lib. * Add a dumpprofile.jsp page, called with ?peer=base64OfPeerHash, which dumps the current state of that peer's profile. Instead of the full base64, you can pass in however many characters you have and it will return the first match found. -
-
* Remove the randomized factor in the tunnel rejection by bandwidth - we now accept the request if we've allocated less than our limit and reject it if we've allocated more. * Stick to the standard capacity scale on tunnel rejection, even for the 10m period. * Build the time message at the very last possible moment -
* Handle hard disconnects more gracefully within the streaming lib, and log unmonitored events more aggressively. * If we drop a peer after connection due to clock skew, log it to the /logs.jsp#connectionlogs with relevent info. In addition, toss it in the stat 'tcp.disconnectAfterSkew'. * Fixed the formatting in the skew display * Added an ERROR message that is fired once after we run out of routerInfo files (thanks susi!) * Set the connect timeout equal to the streaming lib's disconnect timeout if not already specified (the I2PTunnel httpclient already enforces a 60s connect timeout) * Fix for another connection startup problem in the streaming lib. * Fix for a stupid error in the probabalistic drop (rand <= P, not > P) * Adjust the capacity calculations so that tunnel failures alone in the last 10m will not trigger a 0 capacity rank.
-
- Dec 15, 2004
-
-
- Dec 14, 2004
-
-
* Periodically send a message along all I2NP connections with the router's current time, allowing the receiving peer to determine that the clock has skewed too much, and hence, disconnect. For backwards compatability reasons, this is being kludged into a DeliveryStatusMessage (ewww). The next time we have a backwards compatability break, we can put in a proper message setup for it. -
* Reenable the probabalistic drop on the TCP queues to deal with good old fashioned bandwidth limiting. However, by default the probability is rigged to reserve 0% of the queue free - meaning we just aggressively fail messages in the queue if we're transferring too slowly. That reservation factor can be increased with 'tcp.queueFreeFactor=0.25' (or whatever) and the drop code can be disabled with the parameter 'tcp.dropProbabalistically=false'. * Still penalize a peer on tunnel failure, but don't immediately drop their capacity to 0. * More aggressively ACK duplicates * Randomize the timestamper period * Display the clock skew on the connection logs when a peer sends it. * Allow the timestamper to fix skews of up to 10 minutes * Logging -
* Reenable the probabalistic drop on the TCP queues to deal with good old fashioned bandwidth limiting. However, by default the probability is rigged to reserve 0% of the queue free - meaning we just aggressively fail messages in the queue if we're transferring too slowly. That reservation factor can be increased with 'tcp.queueFreeFactor=0.25' (or whatever) and the drop code can be disabled with the parameter 'tcp.dropProbabalistically=false'. * Still penalize a peer on tunnel failure, but don't immediately drop their capacity to 0. * More aggressively ACK duplicates * Randomize the timestamper period * Display the clock skew on the connection logs when a peer sends it. * Allow the timestamper to fix skews of up to 10 minutes * Logging
-
- Dec 13, 2004
-
-
* Added some error checking on the new client send job (thanks duck!) * Implemented tunnel rejection based on bandwidth usage (rejecting tunnels proportional to the bytes allocated in existing tunnels vs the bytes allowed through the bandwidth limiter). * Enable a new configuration parameter for triggering a tunnel rebuild (tunnel.maxTunnelFailures), where that is the max allowed test failures before killing the tunnel (default 0). * Gather more data that we rank capacity by (now we monitor and balance the data from 10m/30m/60m/1d instead of just 10m/60m/1d). * Fix a truncation/type conversion problem on the long term capacity values (we were ignoring the daily stats outright) -
-
-
- Dec 11, 2004
-
-
* Fix the missing HTTP timeout, which was caused by the deferred syn used by default. This, in turn, meant the I2PSocket creation doesn't fail on .connect, but is unable to transfer any data in any direction. We now detect that condition for the I2PTunnelHTTPClient and throw up the right error page. * Logging -
* Use a simpler and less memory intensive job for processing outbound client messages when the session is in mode=bestEffort. We can immediately discard the data as soon as its sent the first time, rather than wait for an ack, since we will never internally resend. * Reduce some synchronization to avoid a rare deadlock * Replaced 'localhost' with 127.0.0.1 in the i2ptunnel config, and special case it within the tunnel controller. * Script cleanup for building jbigi/jcpuid * Logging -
-
-
-
- Dec 10, 2004
-
-
- Dec 09, 2004
-
-
- Dec 08, 2004
-
-
-
* Revised the buffering when reading from the SAM client and writing to the stream. Also added a thread (sigh) so we don't block the SAM client from giving us more messages for abnormally long periods of time. * Display the router version in the logs on startup (oft requested) * Fix a race during the closing of a messageOutputStream -
-
- Dec 07, 2004
-
-
- Dec 06, 2004
-
-
- Dec 05, 2004
-
-
-
* Fix the recently broken SAM bridge (duh) * Add a new pair of SAM apps - net.i2p.sam.client.SAMStreamSink and net.i2p.sam.client.SAMStreamSend, mirroring the streaming lib's StreamSink and StreamSend apps for transferring files. * Make the passive flush timer fire more frequently. -
-
