<%@page contentType="text/html"%> <%@page pageEncoding="UTF-8"%> I2P Router Console - config clients <%@include file="css.jsp" %> <%@include file="nav.jsp" %> <%@include file="summary.jsp" %> " />

I2P Client Configuration

<%@include file="confignav.jsp" %> " /> " /> " />
<% String prev = System.getProperty("net.i2p.router.web.ConfigClientsHandler.nonce"); if (prev != null) System.setProperty("net.i2p.router.web.ConfigClientsHandler.noncePrev", prev); System.setProperty("net.i2p.router.web.ConfigClientsHandler.nonce", new java.util.Random().nextLong()+""); %> " />

Client Configuration

The Java clients listed below are started by the router and run in the same JVM.

All changes require restart to take effect. To change other client options, edit the clients.config file.

WebApp Configuration

The Java web applications listed below are started by the webConsole client and run in the same JVM as the router. They are usually web applications accessible through the router console. They may be complete applications (e.g. i2psnark), front-ends to another client or application which must be separately enabled (e.g. susidns, i2ptunnel), or have no web interface at all (e.g. addressbook).

A web app may also be disabled by removing the .war file from the webapps directory; however the .war file and web app will reappear when you update your router to a newer version, so disabling the web app here is the preferred method.

All changes require restart to take effect. To change other webapp options, edit the webapps.config file.