- 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
-
- Jul 26, 2006
-
-
* Every time we create a new router identity, add an entry to the new "identlog.txt" text file in the I2P install directory. For debugging purposes, publish the count of how many identities the router has cycled through, though not the identities itself. * Cleaned up the way the multitransport shitlisting worked, and added per-transport shitlists * When dropping a router reference locally, first fire a netDb lookup for the entry * Take the peer selection filters into account when organizing the profiles (thanks Complication!) * Avoid some obvious configuration errors for the NTCP transport (invalid ports, "null" ip, etc) * Deal with some small NTCP bugs found in the wild (unresolveable hosts, strange network discons, etc) * Send our netDb info to peers we have direct NTCP connections to after each 6-12 hours of connection uptime * Clean up the NTCP reading and writing queue logic to avoid some potential delays * Allow people to specify the IP that the SSU transport binds on locally, via the advanced config "i2np.udp.bindInterface=1.2.3.4"
-
- Jul 18, 2006
-
-
* URL and date fix in news.xml
-
-
-
- Jul 16, 2006
-
-
* Collect tunnel build agree/reject/expire statistics for each bandwidth tier of peers (and peers of unknown tiers, even if those shouldn't exist)
-
- Jul 14, 2006
-
-
* Improve the multitransport shitlisting (thanks Complication!) * Allow routers with a capacity of 16-32KBps to be used in tunnels under the default configuration (thanks for the stats Complication!) * Properly allow older router references to load on startup (thanks bar, Complication, et al!) * Add a new "i2p.alwaysAllowReseed" advanced config property, though hopefully today's changes should make this unnecessary (thanks void!) * Improved NTCP buffering * Close NTCP connections if we are too backlogged when writing to them
-
- Jul 07, 2006
-
-
- Jul 04, 2006
-
-
* New NIO-based tcp transport (NTCP), enabled by default for outbound connections only. Those who configure their NAT/firewall to allow inbound connections and specify the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound connections. SSU is still enabled for use by default for all users as a fallback. * Substantial bugfix to the tunnel gateway processing to transfer messages sequentially instead of interleaved * Renamed GNU/crypto classes to avoid name clashes with kaffe and other GNU/Classpath based JVMs * Adjust the Fortuna PRNG's pooling system to reduce contention on refill with a background thread to refill the output buffer * Add per-transport support for the shitlist * Add a new async pumped tunnel gateway to reduce tunnel dispatcher contention
-
- Jul 01, 2006
-
-
* Ensure that the I2PTunnel web interface won't update tunnel settings for shared clients when a non-shared client is modified (thanks for spotting, BarkerJr!)
-
- Jun 15, 2006
-
-
- Jun 14, 2006
-
-
- Jun 13, 2006
-
-
- Jun 11, 2006
-
-
- Jun 10, 2006
-
-
- Jun 09, 2006
-
-
- Jun 05, 2006
-
-
-
* Stop sending a blank line before USER in susimail. Seemed to break in rare cases, thanks for reporting, Brachtus!
-
- Jun 04, 2006
-
-
- May 31, 2006
-
-
* Only send netDb searches to the floodfill peers for the time being * Add some proof of concept filters for tunnel participation. By default, it will skip peers with an advertised bandwith of less than 32KBps or an advertised uptime of less than 2 hours. If this is sufficient, a safer implementation of these filters will be implemented. -
* weekly news.xml update
-
- May 19, 2006
-
-
* news.xml update
-
- May 18, 2006
-
-
-
* Fix some oversights in my previous changes: adjust some loglevels, make a few statements less wasteful, make one comparison less confusing and more likely to log unexpected values -
-
- May 16, 2006
-
-
- May 15, 2006
-
-
- May 14, 2006
-
-
* Update the build number too
-
* Separate growth factors for tunnel count and tunnel test time * Reduce growth factors, so probabalistic throttle would activate * Square probAccept values to decelerate stronger when far from average * Create a bandwidth stat with approximately 15-second half life * Make allowTunnel() check the 1-second bandwidth for overload before doing allowance calculations using 15-second bandwidth * Tweak the overload detector in BuildExecutor to be more sensitive for rising edges, add ability to initiate tunnel drops * Add a function to seek and drop the highest-rate participating tunnel, keeping a fixed+random grace period between such drops. It doesn't seem very effective, so disabled by default ("router.dropTunnelsOnOverload=true" to enable)
-
