- Jan 12, 2005
-
-
- Jan 09, 2005
-
-
- Jan 07, 2005
-
-
- Jan 06, 2005
-
-
2005-01-06 jrandom * Added a startup message to the addressbook, printing its version number to stdout (which is sent to wrapper.config) when it loads. * Updated the addressbook to reread the config file periodically * Added orion.i2p to the list of eepsites on the default homepage -
-
* Handle unexpected network read errors more carefully (thanks parg!) * Added more methods to partially compare (DataHelper) and display arrays (Base64.encode). * Exposed the AES encryptBlock/decryptBlock on the context.aes() * Be more generous on the throttle when just starting up the router * Fix a missing scheduled event in the streaming lib (caused after reset) * Add a new DisconnectListener on the I2PSocketManager to allow notification of session destruction. * Make sure our own router identity is valid, and if it isn't, build a new one and restart the router. Alternately, you can run the Router with the single command line argument "rebuild" and it will do the same.
-
- Jan 05, 2005
-
-
- Jan 04, 2005
-
-
- Jan 03, 2005
-
-
- Jan 01, 2005
-
-
- Dec 31, 2004
-
-
- Dec 30, 2004
-
-
* Revised the I2PTunnel client and httpclient connection establishment throttles. There is now a pool of threads that build the I2PSocket connections with a default size of 5, configurable via the I2PTunnel client option 'i2ptunnel.numConnectionBuilders' (if set to 0, it will not throttle the number of concurrent builders, but will launch a thread per socket during establishment). In addition, sockets accepted but not yet allocated to one of the connection builders will be destroyed after 30 seconds, configurable via 'i2ptunnel.maxWaitTime' (if set to 0, it will wait indefinitely).
-
- Dec 29, 2004
-
-
-
-
-
* Add in a new keepalive event on each TCP connection, proactively sending a (tiny) time message every minute or two, as well as killing the connection if no message has been fully sent within 5 minutes or so. This should help deal with hung connections from IP address changes. -
-
- Dec 21, 2004
-
-
-
* Cleaned up the postinstall/startup scripts a bit more to handle winME, and added windows info to the headless docs. (thanks ardvark!) * Fixed a harmless (yet NPE inspiring) race during the final shutdown of a stream (thanks frosk!) * Add a pair of new stats for monitoring tunnel participation - tunnel.participatingBytesProcessed (total # bytes transferred) and tunnel.participatingBytesProcessedActive (total # bytes transferred for tunnels whose byte count exceed the 10m average). This should help further monitor congestion issues. * Made the NamingService factory property public (thanks susi!)
-
- Dec 20, 2004
-
-
- Dec 19, 2004
-
-
-
-
* Added a new i2ptunnel type: 'httpserver', allowing you to specify what hostname should be sent to the webserver. By default, new installs will have an httpserver pointing at their jetty instance with the spoofed name 'mysite.i2p' (editable on the /i2ptunnel/edit.jsp page). -
-
- 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
-
