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

Skip to content
Snippets Groups Projects
  1. Sep 13, 2005
    • jrandom's avatar
      2005-09-12 jrandom · b5784d60
      jrandom authored and zzz's avatar zzz committed
          * More aggressively publish updated routerInfo.
          * Expose the flag to force SSU introductions on the router console
          * Don't give people the option to disable SNTP time sync, at least not
            through the router console, because there is no reason to disable it.
            No, not even if your OS is "ntp synced", because chances are, its not.
      b5784d60
  2. Sep 12, 2005
  3. Sep 11, 2005
    • jrandom's avatar
      2005-09-10 jrandom · d9b4406c
      jrandom authored and zzz's avatar zzz committed
          * Test the router's reachability earlier and more aggressively
          * Use the low level bandwidth limiter's rates for the router console, and
            if the router has net.i2p.router.transport.FIFOBandwidthLimiter=INFO in
            the logger config, keep track of the 1 second transfer rates as the stat
            'bw.sendBps1s' and 'bw.recvBps1s', allowing closer monitoring of burst
            behavior.
      d9b4406c
  4. Sep 10, 2005
  5. Sep 07, 2005
    • jrandom's avatar
      2005-09-07 BarkerJr · 54074e76
      jrandom authored and zzz's avatar zzz committed
          * HTML cleanup for the router console (thanks!)
      2005-09-07  jrandom
          * Lay the foundation for 'client routers' - the ability for peers to opt
            out of participating in tunnels entirely due to firewall/NAT issues.
            Individual routers have control over where those peers are used in
            tunnels - in outbound or inbound, exploratory or client tunnels, or
            none at all.  The defaults with this build are to simply act as before -
            placing everyone as potential participants in any tunnel.
          * Another part of the foundation includes the option for netDb
            participants to refuse to answer queries regarding peers who are marked
            as unreachable, though this too is disabled by default (meaning the
            routerInfo is retrievable from the netDb).
      54074e76
    • cervantes's avatar
      Adjusted wording on the bandwidth limiter controls to reflect new router defaults · 744671a5
      cervantes authored and zzz's avatar zzz committed
      744671a5
  6. Sep 06, 2005
  7. Sep 05, 2005
  8. Sep 04, 2005
  9. Sep 01, 2005
    • jrandom's avatar
      2005-08-31 jrandom · b43114f6
      jrandom authored and zzz's avatar zzz committed
          * Don't publish leaseSets to the netDb if they will never be looked for -
            namely, if they are for destinations that only establish outbound
            streams.  I2PTunnel's 'client' and 'httpclient' proxies have been
            modified to tell the router that it doesn't need to publish their
            leaseSet (by setting the I2CP config option 'i2cp.dontPublishLeaseSet'
            to 'true').
          * Don't publish the top 10 peer rankings of each router in the netdb, as
            it isn't being watched right now.
      b43114f6
  10. Aug 31, 2005
  11. Aug 30, 2005
  12. Aug 27, 2005
    • jrandom's avatar
      2005-08-27 jrandom · 8660cf0d
      jrandom authored and zzz's avatar zzz committed
          * Minor logging and optimization tweaks in the router and SDK
          * Use ISO-8859-1 in the XML files (thanks redzara!)
          * The consolePassword config property can now be used to bypass the router
            console's nonce checking, allowing CLI restarts
      8660cf0d
  13. Aug 25, 2005
  14. Aug 24, 2005
    • jrandom's avatar
      2005-08-24 jrandom · 346faa3d
      jrandom authored and zzz's avatar zzz committed
          * Catch errors with corrupt tunnel messages more gracefully (no need to
            kill the thread and cause an OOM...)
          * Don't skip shitlisted peers for netDb store messages, as they aren't
            necessarily shitlisted by other people (though they probably are).
          * Adjust the netDb store per-peer timeout based on each particular peer's
            profile (timeout = 4x their average netDb store response time)
          * Don't republish leaseSets to *failed* peers - send them to peers who
            replied but just didn't know the value.
          * Set a 5 second timeout on the I2PTunnelHTTPServer reading the client's
            HTTP headers, rather than blocking indefinitely.  HTTP headers should be
            sent entirely within the first streaming packet anyway, so this won't be
            a problem.
          * Don't use the I2PTunnel*Server handler thread pool by default, as it may
            prevent any clients from accessing the server if the handlers get
            blocked by the streaming lib or other issues.
          * Don't overwrite a known status (OK/ERR-Reject/ERR-SymmetricNAT) with
            Unknown.
      346faa3d
  15. Aug 23, 2005
    • jrandom's avatar
      2005-08-23 jrandom · 1a6b49cf
      jrandom authored and zzz's avatar zzz committed
          * Removed the concept of "no bandwidth limit" - if none is specified, its
            16KBps in/out.
          * Include ack packets in the per-peer cwin throttle (they were part of the
            bandwidth limit though).
          * Tweak the SSU cwin operation to get more accurrate estimates under
            congestions.
          * SSU improvements to resend more efficiently.
          * Added a basic scheduler to eepget to fetch multiple files sequentially.
      1a6b49cf
  16. Aug 21, 2005
  17. Aug 16, 2005
  18. Aug 10, 2005
    • jrandom's avatar
      2005-08-10 jrandom · 77b995f5
      jrandom authored and zzz's avatar zzz committed
          * Deployed the peer testing implementation to be run every few minutes on
            each router, as well as any time the user requests a test manually.  The
            tests do not reconfigure the ports at the moment, merely determine under
            what conditions the local router is reachable.  The status shown in the
            top left will be "ERR-SymmetricNAT" if the user's IP and port show up
            differently for different peers, "ERR-Reject" if the router cannot
            receive unsolicited packets or the peer helping test could not find a
            collaborator, "Unknown" if the test has not been run or the test
            participants were unreachable, or "OK" if the router can receive
            unsolicited connections and those connections use the same IP and port.
      77b995f5
  19. Aug 08, 2005
  20. Aug 07, 2005
    • jrandom's avatar
      2005-08-07 Complication · ba30b56c
      jrandom authored and zzz's avatar zzz committed
          * Display the average clock skew for both SSU and TCP connections
      2005-08-07  jrandom
          * Fixed the long standing streaming lib bug where we could lose the first
            packet on retransmission.
          * Avoid an NPE when a message expires on the SSU queue.
          * Adjust the streaming lib's window growth factor with an additional
            Vegas-esque congestion detection algorithm.
          * Removed an unnecessary SSU session drop
          * Reduced the MTU (until we get a working PMTU lib)
          * Deferr tunnel acceptance until we know how to reach the next hop,
            rejecting it if we can't find them in time.
          * If our netDb store of our leaseSet fails, give it a few seconds before
            republishing.
      ba30b56c
  21. Aug 03, 2005
Loading