I2P Address: [http://git.idk.i2p]

Skip to content
Snippets Groups Projects
  1. Oct 07, 2004
  2. Oct 06, 2004
    • jrandom's avatar
      2004-10-06 jrandom · 38c422bb
      jrandom authored and zzz's avatar zzz committed
          * Implement an active queue management scheme on the TCP transports,
            dropping messages probabalistically as the queue fills up.  The
            estimated queue capacity is determined by the rate at which messages
            have been sent to the peer (averaged at 1, 5, and 60m periods).  As
            we exceed 1/2 of the estimated capacity, we drop messages throughout
            the queue probabalistically with regards to their size.  This is based
            on RFC 2309's RED, with the minimum threshold set to 1/2 the
            estimated connection capacity.  We may want to consider using a send
            rate and queue size measured across all connections, to deal with our
            own local bandwidth saturation, but we'll try the per-con metrics first.
      38c422bb
    • jrandom's avatar
      list the shutdown time w/ the clock fudge factor included · 39d4e5ea
      jrandom authored and zzz's avatar zzz committed
      39d4e5ea
    • jrandom's avatar
      2004-10-06 jrandom · 4191ad1c
      jrandom authored and zzz's avatar zzz committed
          * Enable explicit disabling of the systray entirely for windows machines
            with strange configurations: add -Dsystray.disable=true to the java
            command line.  (thanks mihi!)
      4191ad1c
    • jrandom's avatar
      2004-10-05 jrandom · 29287da3
      jrandom authored and zzz's avatar zzz committed
          * Allow peers on the same LAN to communicate with each other safely even
            when they cannot talk to each other through the external address.
      29287da3
  3. Oct 05, 2004
    • jrandom's avatar
      2004-10-05 jrandom · 98c78041
      jrandom authored and zzz's avatar zzz committed
          * Display how much time is left before the graceful shutdown is complete.
          * Debug some improperly failed messages on timeout or disconnection.
      98c78041
    • jrandom's avatar
      oops · 756af9c6
      jrandom authored and zzz's avatar zzz committed
      756af9c6
    • jrandom's avatar
      updated beyond.i2p (after verification) · 7f9076bb
      jrandom authored and zzz's avatar zzz committed
      7f9076bb
    • jrandom's avatar
      added b.i2p · 2404f1ab
      jrandom authored and zzz's avatar zzz committed
      2404f1ab
    • jrandom's avatar
      2004-10-05 jrandom · 64bcfd09
      jrandom authored and zzz's avatar zzz committed
          * Don't go into a fast busy if an I2PTunnel 'server' is explicitly killed
            (thanks mule!)
          * Handle some more error conditions regarding abruptly closing sockets
            (thanks Jonva!)
      64bcfd09
    • jrandom's avatar
      added tinyurl.i2p · 6251d22c
      jrandom authored and zzz's avatar zzz committed
      6251d22c
  4. Oct 04, 2004
  5. Oct 03, 2004
    • jrandom's avatar
      cli to splot the stat log · 0526d5b5
      jrandom authored and zzz's avatar zzz committed
      0526d5b5
    • jrandom's avatar
      dont overwrite index.html anymore (0.4.1.2 wont) · 34163fb8
      jrandom authored and zzz's avatar zzz committed
      34163fb8
    • jrandom's avatar
      2004-10-03 jrandom · 98d2d661
      jrandom authored and zzz's avatar zzz committed
          * Add a new stat logging component to optionally dump the raw stats to
            disk as they are generated, rather than rely upon the summarized data.
            By default, this is off, but the router property "stat.logFilters" can
            be set to a comma delimited list of stats (e.g. "client.sendAckTime")
            which will be written to the file "stats.log" (or whatever the property
            "stat.logFile" is set to).  This can also log profile related stats,
            such as "dbResponseTime" or "tunnelTestResponseTime".
      98d2d661
    • jrandom's avatar
      dont list an explicit webdefault.xml (use the default) · d9f0a0fd
      jrandom authored and zzz's avatar zzz committed
      d9f0a0fd
  6. Oct 02, 2004
    • jrandom's avatar
      2004-10-02 jrandom · d20d043e
      jrandom authored and zzz's avatar zzz committed
          * Assure that we quickly fail messages bound for shitlisted peers.
          * Address a race on startup where the first peer contacted could hang the
            router (thanks Romster!)
          * Only whine about an intermittent inability to query the time server once
      d20d043e
    • jrandom's avatar
      2004-10-02 jrandom · ce186e18
      jrandom authored and zzz's avatar zzz committed
          * Command line utility to verify a peer's reachability - simply run
            net.i2p.router.transport.tcp.ConnectionHandler hostname port# and it
            will print out whether that peer is reachable or not (using a simple
            verification handshake).
      ce186e18
  7. Oct 01, 2004
  8. Sep 30, 2004
  9. Sep 29, 2004
    • jrandom's avatar
      * updated stats: · b6017c55
      jrandom authored and zzz's avatar zzz committed
      - sendsPerFailure: how many partial sends we make when they all fail
      - timeoutCongestionInbound: describes how much faster than our average speed we were receiving data when each partial send timed out (in Bps)
      - timeoutCongestionMessage: our send processing time when each partial send timed out (in ms)
      - timeoutCongestionTunnel: our tunnel test time when each partial send timed out (in ms)
      - participatingMessagesProcessedActive: # of messages more than the (most recent) average that a tunnel we were participating in transmitted (for tunnels with more than the average)
      * updated to use Writer for rendering the console, so we can do partial writes (and hopefully help debug some kooky threading bugs on kaffe)
      b6017c55
    • jrandom's avatar
      * updated stats: · 62ed6c6a
      jrandom authored and zzz's avatar zzz committed
      - sendsPerFailure: how many partial sends we make when they all fail
      - timeoutCongestionInbound: describes how much faster than our average speed we were receiving data when each partial send timed out (in Bps)
      - timeoutCongestionMessage: our send processing time when each partial send timed out (in ms)
      - timeoutCongestionTunnel: our tunnel test time when each partial send timed out (in ms)
      - participatingMessagesProcessedActive: # of messages more than the (most recent) average that a tunnel we were participating in transmitted (for tunnels with more than the average)
      * updated to use Writer for rendering the console, so we can do partial writes (and hopefully help debug some kooky threading bugs on kaffe)
      62ed6c6a
Loading