forked from I2P_Developers/i2p.i2p
9a820961a2
* Fix during the ssu handshake to avoid an unnecessary failure on
packet retransmission (thanks ripple!)
* Fix during the SSU handshake to use the negotiated session key asap,
rather than using the intro key for more than we should (thanks ripple!)
* Fixes to the message reply registry (thanks Complication!)
* More comprehensive syndie banning (for repeated pushes)
* Publish the router's ballpark bandwidth limit (w/in a power of 2), for
testing purposes
* Put a floor back on the capacity threshold, so too many failing peers
won't cause us to pick very bad peers (unless we have very few good
ones)
* Bugfix to cut down on peers using introducers unneessarily (thanks
Complication!)
* Reduced the default streaming lib message size to fit into a single
tunnel message, rather than require 5 tunnel messages to be transferred
without loss before recomposition. This reduces throughput, but should
increase reliability, at least for the time being.
* Misc small bugfixes in the router (thanks all!)
* More tweaking for Syndie's CSS (thanks Doubtful Salmon!)
The routerconsole application is an embedable web server / servlet container. In it there is a bundled routerconsole.war containing JSPs (per jsp/*) that implement a web based control panel for the router. This console gives the user a quick view into how their router is operating and exposes some pages to configure it. The web server itself is Jetty [1] and is contained within the various jar files under lib/. To embed this web server and the included router console, the startRouter script needs to be updated to include those jar files in the class path, plus the router.config needs appropriate entries to start up the server: clientApp.3.main=net.i2p.router.web.RouterConsoleRunner clientApp.3.name=webConsole clientApp.3.args=7657 0.0.0.0 ./webapps/ That instructs the router to fire up the webserver listening on port 7657 on all of its interfaces (0.0.0.0), loading up any .war files under the ./webapps/ directory. The RouterConsoleRunner itself configures the Jetty server to give the ./webapps/routerconsole.war control over the root context, directing a request to http://localhost:7657/index.jsp to the routerconsole.war's index.jsp. Any other .war file will be mounted under their filename's context (e.g. myi2p.war would be reachable at http://localhost:7657/myi2p/index.jsp). [1] http://jetty.mortbay.com/jetty/index.html