complication authored 18 years ago and zzz committed 18 years ago

    * Collect tunnel build agree/reject/expire statistics
      for each bandwidth tier of peers (and peers of unknown tiers,
      even if those shouldn't exist)

jrandom authored 18 years ago and zzz committed 18 years ago

    * 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

jrandom authored 18 years ago and zzz committed 18 years ago

    * 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

complication authored 18 years ago and zzz committed 18 years ago

    * 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!)

cervantes authored 18 years ago and zzz committed 18 years ago

    * Small tweak to I2PTunnel CSS, so it looks better with desktops
      that use Bitstream Vera fonts @ 96 dpi

jrandom authored 18 years ago and zzz committed 18 years ago

    * Use a minimum uptime of 2 hours, not 4 (oops)

jrandom authored 18 years ago and zzz committed 18 years ago

    * Cut down the proactive rejections due to queue size - if we are
      at the point of having decrypted the request off the queue, might
      as well let it through, rather than waste that decryption

jrandom authored 18 years ago and zzz committed 18 years ago

    * Bugfix to the I2PTunnel IRC filter to support multiple concurrent
      outstanding pings/pongs

jrandom authored 18 years ago and zzz committed 18 years ago

    * Further reduction in proactive rejections

jrandom authored 18 years ago and zzz committed 18 years ago

    * Don't let the pending tunnel request queue grow beyond reason
      (letting things sit for up to 30s when they fail after 10s
      seems a bit... off)

jrandom authored 18 years ago and zzz committed 18 years ago

    * Be more conservative in the proactive rejections

complication authored 18 years ago and zzz committed 18 years ago

    * Stop sending a blank line before USER in susimail.
      Seemed to break in rare cases, thanks for reporting, Brachtus!

jrandom authored 18 years ago and zzz committed 18 years ago

2006-06-04  jrandom
    * Reduce the SSU ack frequency
    * Tweaked the tunnel rejection settings to reject less aggressively

jrandom authored 18 years ago and zzz committed 18 years ago

    * 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.

complication authored 18 years ago and zzz committed 18 years ago

    * weekly news.xml update

complication authored 18 years ago and zzz committed 18 years ago

    * news.xml update

jrandom authored 18 years ago and zzz committed 18 years ago

2006-05-18  jrandom
    * Made the SSU ACKs less frequent when possible

complication authored 18 years ago and zzz committed 18 years ago

    * 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

jrandom authored 18 years ago and zzz committed 18 years ago

    * Make the peer page sortable
    * SSU modifications to cut down on unnecessary connection failures

jrandom authored 18 years ago and zzz committed 18 years ago

    * Further shitlist randomizations
    * Adjust the stats monitored for detecting cpu overload when dropping new
      tunnel requests

jrandom authored 18 years ago and zzz committed 18 years ago

    * Add a load dependent throttle on the pending inbound tunnel request
      backlog
    * Increased the tunnel test failure slack before killing a tunnel

complication authored 18 years ago and zzz committed 18 years ago

    * Update the build number too

complication authored 18 years ago and zzz committed 18 years ago

    * 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)

jrandom authored 18 years ago and zzz committed 18 years ago

    * PRNG bugfix (thanks cervantes and Complication!)

complication authored 18 years ago and zzz committed 18 years ago

    * weekly news.xml update

jrandom authored 18 years ago and zzz committed 18 years ago

2006-05-09  jrandom
    * Further tunnel creation timeout revamp

complication authored 18 years ago and zzz committed 18 years ago

    * Fix problem whereby repeated calls to allowed() would make
      the 1-tunnel exception permit more than one concurrent build

jrandom authored 18 years ago and zzz committed 18 years ago

    * Readjust the tunnel creation timeouts to reject less but fail earlier,
      while tracking the extended timeout events.

jrandom authored 18 years ago and zzz committed 18 years ago

    * Short circuit a highly congested part of the stat logging unless its
      required (may or may not help with a synchronization issue reported by
      andreas)

complication authored 18 years ago and zzz committed 18 years ago

    * Allow a single build attempt to proceed despite 1-minute overload
      only if the 1-second rate shows enough spare bandwidth
      (e.g. overload has already eased)

complication authored 18 years ago and zzz committed 18 years ago

    * Correct a misnamed property in SummaryHelper.java
      to avoid confusion
    * Make the maximum allowance of our own concurrent
      tunnel builds slightly adaptive: one concurrent build per 6 KB/s
      within the fixed range 2..10
    * While overloaded, try to avoid completely choking our own build attempts,
      instead prefer limiting them to 1

complication authored 18 years ago and zzz committed 18 years ago

    * Fixed URL in previous update, sorry

complication authored 18 years ago and zzz committed 18 years ago

    * Weekly news.xml update

jrandom authored 18 years ago and zzz committed 18 years ago

    * Adjust the tunnel build timeouts to cut down on expirations, and
      increased the SSU connection establishment retransmission rate to
      something less glacial.
    * For the first 5 minutes of uptime, be less aggressive with tunnel
      exploration, opting for more reliable peers to start with.

jrandom authored 18 years ago and zzz committed 18 years ago

    * Fix for a netDb lookup race (thanks cervantes!)