- Nov 25, 2004
-
-
* Revised the installer to include start menu and desktop shortcuts for windows platforms, including pretty icons (thanks DrWoo!) * Allow clients specified in clients.config to have an explicit startup delay. * Update the default install to launch a browser pointing at the console whenever I2P starts up, rather than only the first time it starts up (configurable on /configservice.jsp, or in clients.config) * Bugfix to the clock skew checking code to monitor the delta between offsets, not the offset itself (duh) * Router console html update * New (and uuuuugly) code to verify that the wrapper.config contains the necessary classpath entries on update. If it has to update the wrapper.config, it will stop the JVM and service completely, since the java service wrapper doesn't reread the wrapper.config on JVM restart - requiring the user to manually restart the service after an update. * Increase the TCP connection timeout to 30s (which is obscenely long) ------------------------------------------------ -
-
- Nov 23, 2004
-
-
- Nov 22, 2004
-
-
* Update the I2PTunnel web interface to include an option for the new streaming lib (which is ignored until the 0.4.2 release). * Revised the I2PTunnel web interface to keep the I2CP options of client and httpclient tunnels in sync, as they all share the same I2CP session.
-
- Nov 21, 2004
-
-
* Only allow small clock skews after the first 10 minutes of operation (to prevent later network lag bouncing us way off course - yes, we really need an NTP impl to balance out the network burps...) * Revamp the I2PTunnel web interface startup process so that everything is shown immediately, so that different pieces hanging don't hang the rest, and other minor bugfixes. * Take note of SAM startup error (in case you're already running a SAM bridge...) * Increase the bandwidth limiter burst values available to 10-60s (or whatever is placed in /configadvanced.jsp, of course) -
* Only allow small clock skews after the first 10 minutes of operation (to prevent later network lag bouncing us way off course - yes, we really need an NTP impl to balance out the network burps...) * Revamp the I2PTunnel web interface startup process so that everything is shown immediately, so that different pieces hanging don't hang the rest, and other minor bugfixes. * Take note of SAM startup error (in case you're already running a SAM bridge...) * Increase the bandwidth limiter burst values available to 10-60s (or whatever is placed in /configadvanced.jsp, of course) -
* Allow end of line comments in the hosts.txt and other config files, using '#' to begin the comments (thanks susi!) * Add support to I2PTunnel's 'client' feature for picking between multiple target destinations (e.g. 'client 6668 irc.duck.i2p,irc.baffled.i2p') * Add a quick link on the left hand nav to reseed if there aren't enough known peers, as well as link to the config page if there are no active peers. Revised config page accordingly. -
-
-
* Destroy ElGamal/AES+SessionTag keys after 15 minutes of inactivity rather that every 15 minutes, and increase the warning period in which we refresh tags from 30s to 2 minutes. * Bugfix for a rare problem closing an I2PTunnel stream where we'd fail to close the I2PSocket (leaving it to timeout).
-
- Nov 20, 2004
-
-
- Nov 19, 2004
-
-
-
-
if you want to get this data and you're running outside the router, just toss on a "-Dstat.logFilters=* -Dstat.logFile=proxy.stats" to the java command line. the resulting file can be parsed w/ java -cp lib/i2p.jar net.i2p.stat.StatLogSplitter proxy.stats, then fed into gnuplot or whatever
-
- Nov 18, 2004
-
-
further and cancel all of the tags we're using for that peer so that we can react to their potential restart / tag loss quicker. * use the minimum resend delay as the base to be exponentiated if our RTT is too low (so we resend less) * dont be such a wuss when flushing a closed stream
-
-
- Nov 17, 2004
-
-
- Nov 16, 2004
-
-
-
* add new back-off logic to reduce payload resends during transient lag - only let one packet be resent at a time, even if the window size allows it (and the packet timers request it). this should make congestion less painful, and reduce the overall number of messages resent (as the SACKs for the one packet actively resent should clarify what made it through)
-
-
-
- Nov 15, 2004
-
-
- Nov 13, 2004
-
-
* Added throttles on how many I2PTunnel client connections we open at once * Replaced some buffered streams in I2PTunnel with unbuffered streams, as the streaming library used should take care of any buffering. * Added a cache for some objects used in I2PTunnel, especially useful when there are many short lived connections. * Trimmed the SimpleTimer's processing a bit -
-
* Added throttles on how many I2PTunnel client connections we open at once * Replaced some buffered streams in I2PTunnel with unbuffered streams, as the streaming library used should take care of any buffering. * Added a cache for some objects used in I2PTunnel, especially useful when there are many short lived connections. * Trimmed the SimpleTimer's processing a bit
-
- Nov 12, 2004
-
-
- Nov 11, 2004
-
-
- Nov 10, 2004
-
-
