- Sep 27, 2006
-
-
* Take back an accidental log level change
-
* Subclass from Clock a RouterClock which can access router transports, with the goal of developing it to second-guess NTP results * Make transports report clock skew in seconds * Adjust renderStatusHTML() methods accordingly * Show average for NTCP clock skews too * Give transports a getClockSkews() method to report clock skews * Give transport manager a getClockSkews() method to aggregate results * Give comm system facade a getMedianPeerClockSkew() method which RouterClock calls (to observe results, add "net.i2p.router.transport.CommSystemFacadeImpl=WARN" to logging) * Extra explicitness in NTCP classes to denote unit of time. * Fix some places in NTCPConnection where milliseconds and seconds were confused
-
- Sep 26, 2006
-
- Sep 24, 2006
-
- Sep 20, 2006
-
- Sep 16, 2006
-
- Sep 14, 2006
-
-
* news.xml update
-
- Sep 13, 2006
-
-
* i2psnark: Mark a peer's requests as unrequested on disconnect, preventing premature end game * i2psnark: Randomize selection of next piece during end game * i2psnark: Don't restore a partial piece to a peer that is already working on it * i2psnark: strip ".torrent" on web page * i2psnark: Limit piece size in generated torrent to 1MB max
- Sep 10, 2006
-
- Sep 09, 2006
-
-
-
* Tweak the PRNG logging so it only displays error messages if there are problems * Disable dynamic router keys for the time being, as they don't offer meaningful security, may hurt the router, and makes it harder to determine the network health. The code to restart on SSU IP change is still enabled however. * Disable tunnel load testing, leaning back on the tiered selection for the time being. * Spattering of bugfixes
- Sep 07, 2006
-
- Sep 06, 2006
-
-
* i2psnark: Implement basic partial-piece saves across connections * i2psnark: Implement keep-alive sending. This will keep non-i2psnark clients from dropping us for inactivity but also renders the 2-minute transmit-inactivity code in i2psnark ineffective. Will have to research why there is transmit but not receive inactivity code. With the current connection limit of 24 peers we aren't in any danger of keeping out new peers by keeping inactive ones. * i2psnark: Increase CHECK_PERIOD from 20 to 40 since nothing happens in 20 seconds * i2psnark: Fix dropped chunk handling * i2psnark: Web rate report cleanup
-
- Sep 04, 2006
-
-
* i2psnark: Report cleared trackerErr immediately * i2psnark: Add trackerErr reporting after previous success; retry more quickly * i2psnark: Set up new connections more quickly * i2psnark: Don't delay tracker fetch when setting up lots of connections * i2psnark: Reduce MAX_UPLOADERS from 12 to 4
-
- Sep 03, 2006
-
-
* Limit form size in SusiDNS to avoid exceeding a POST size limit on postback * Print messages about addressbook size to give better overview * Enable delete function in published addressbook
- Aug 21, 2006
-
-
* Fix error reporting discrepancy (thanks for helping notice, yojoe!)
-
- Aug 04, 2006
-
-
* news.xml update
-
- Aug 03, 2006
-
- Aug 01, 2006
-
- Jul 30, 2006
-
-
* Treat NTP responses from unexpected stratums like failures
-
- Jul 29, 2006
-
- Jul 28, 2006
-
-
- Jul 27, 2006
-
-
* Cut down NTCP connection establishments once we know the peer is skewed (rather than wait for full establishment before verifying) * Removed a lock on the stats framework when accessing rates, which shouldn't be a problem, assuming rates are created (pretty much) all at once and merely updated during the lifetime of the jvm.
-
* When dropping a netDb router reference, only accept newer references as part of the update check * If we have been up for a while, don't accept really old router references (published 2 or more days ago) * Drop router references once they are no longer valid, even if they were allowed in due to the lax restrictions on startup
-
* When dropping a netDb router reference, only accept newer references as part of the update check * If we have been up for a while, don't accept really old router references (published 2 or more days ago) * Drop router references once they are no longer valid, even if they were allowed in due to the lax restrictions on startup
-