- Sep 18, 2005
-
- Sep 17, 2005
-
-
* Updated the bandwidth limiter to use two tiers of bandwidth - our normal steady state rate, plus a new limit on how fast we transfer when bursting. This is different from the old "burst as fast as possible until we're out of tokens" policy, and should help those with congested networks. See /config.jsp to manage this rate. * Bugfixes in Syndie to handle missing cache files (no data was lost, the old posts just didn't show up). * Log properly in EepPost
-
* Added the natively compiled jbigi and patched java service wrapper for OS X. Thanks Bill Dorsey for letting me use your machine! * Don't build i2p.exe or i2pinstall.exe when run on OS X machines, as we don't bundle the binutils necessary (and there'd be a naming conflict if we did). * Added 'single user' functionality to syndie - if the single user checkbox on the admin page is checked, all users are allowed to control the instance and sync up with remote syndie nodes. * Temporarily disable the x-i2p-gzip in i2ptunnel until it is more closely debugged.
-
- Sep 16, 2005
-
-
* Adjust I2PTunnelHTTPServer so it can be used for outproxy operators (just specify the spoofed host as an empty string), allowing them to honor x-i2p-gzip encoding. * Let windows users build the exes too (thanks bar and redzara!) * Allow I2PTunnel httpserver operators to disable gzip compression on individual tunnels with the i2ptunnel.gzip=false client option (good idea susi!)
-
* Added the i2p.exe and i2pinstall.exe for windows users, using launch4j. * Added runplain.sh for *nix/osx users having problems using the java service wrapper (called from the install dir as: sh runplain.sh) * Bundle susidns and syndie, with links on the top nav * Have I2PTunnelHTTPClient and I2PTunnelHTTPServer use the x-i2p-gzip content-encoding (if offered), reducing the payload size before it reaches the streaming lib. The existing compression is at the i2cp level, so we've been packetizing 4KB of uncompressed data and then compressing those messages, rather than compressing and then packetizing 4KB of compressed data. This should reduce the number of round trips to fetch web pages substantially. * Adjust the startup and timing of the addressbook so that susidns always has config to work off, and expose a method for susidns to tell it to reload its config and rerun.
- Sep 15, 2005
-
- Sep 13, 2005
-
-
* Removed guaranteed delivery mode entirely (so existing i2phex clients using it can get the benefits of mode=best_effort). Guaranteed delivery is offered at the streaming lib level. * Improve the peer selection code for peer testing, as everyone now supports tests. * Give the watchdog its fangs - if it detects obscene job lag or if clients have been unable to get a leaseSet for more than 5 minutes, restart the router. This was disabled a year ago due to spurious restarts, and can be disabled by "watchdog.haltOnHang=false", but the cause of the spurious restarts should be gone.
-
* 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.
- Sep 12, 2005
-
- Sep 11, 2005
-
-
* 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.
- Sep 10, 2005
-
- Sep 09, 2005
-
- Sep 08, 2005
-
- Sep 07, 2005
-
-
* 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).
-
- Sep 06, 2005
-