i2p.itoopie

Files

- Restrict peers requiring introducers from inbound tunnels,
        since it's slow and unreliable... and many of them advertise
        NTCP, which seems unlikely to work
      - Provide warning on summary bar if firewalled with inbound NTCP enabled
    * Stats: Remove the bw.[send,recv]Bps[1,15]s stats unless
      log level net.i2p.router.transport.FIFOBandwidthLimiter >= WARN
      at startup (you didn't get any data unless you set the log level anyway)
    * oldstats.jsp: Don't put 2 decimal places on integer event counts
    * Remove the Internals link from the menu bar
    * i2psnark: Extend startup delay from 1 to 3 minutes

2008-05-07 16:23:54 +00:00

java

* Reachability:

2008-05-07 16:23:54 +00:00

jsp

* Reachability:

2008-05-07 16:23:54 +00:00

readme.txt

first pass at the 0.4 architecture. not ready for use or integration yet, but is functional with some manual build/config work

2004-07-24 02:06:07 +00:00

readme.txt

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