<%@page contentType="text/html" %> I2P Router Console - config networking <%@include file="nav.jsp" %> <%@include file="summary.jsp" %> " />
<%@include file="confignav.jsp" %> " />
<% String prev = System.getProperty("net.i2p.router.web.ConfigNetHandler.nonce"); if (prev != null) System.setProperty("net.i2p.router.web.ConfigNetHandler.noncePrev", prev); System.setProperty("net.i2p.router.web.ConfigNetHandler.nonce", new java.util.Random().nextLong()+""); %> " /> Bandwidth limiter
Inbound rate: " /> KBps bursting up to " /> KBps for
Outbound rate: " /> KBps bursting up to " /> KBps for
KBps = kilobytes per second = 1024 bytes per second = 8192 bits per second.
A negative inbound rate means a default limit of 32KBytes per second. A negative outbound rate means a default limit of 16KBytes per second.

Bandwidth share percentage:
<% int share = nethelper.getShareBandwidth(); if (share < 12) { out.print("NOTE: You have configured I2P to share only " + share + "KBps. "); out.print("I2P requires at least 12KBps to enable sharing. "); out.print("Please enable sharing (participating in tunnels) by configuring more bandwidth. "); out.print("It improves your anonymity by creating cover traffic, and helps the network.
"); } else { out.print("You have configured I2P to share " + share + "KBps. "); out.print("The higher the share bandwidth the more you improve your anonymity and help the network.
"); } %>



External UDP address:
Require SSU introductions? />

If you can, please poke a hole in your NAT or firewall to allow unsolicited UDP packets to reach you on your external UDP address. If you can't, I2P now includes supports UDP hole punching with "SSU introductions" - peers who will relay a request from someone you don't know to your router for your router so that you can make an outbound connection to them. I2P will use these introductions automatically if it detects that the port is not forwarded (as shown by the Status: OK (NAT) line), or you can manually require them here. Users behind symmetric NATs, such as OpenBSD's pf, are not currently supported.


Inbound TCP connection configuration:
Externally reachable hostname or IP address: " /> (dyndns and the like are fine)
OR use IP address detected by SSU (currently )? />

Externally reachable TCP port: " />
OR use the same port configured for SSU (currently )? />

You do not need to allow inbound TCP connections - outbound connections work with no configuration. However, if you want to receive inbound TCP connections, you must poke a hole in your NAT or firewall for unsolicited TCP connections. If you specify the wrong IP address or hostname, or do not properly configure your NAT or firewall, your network performance will degrade substantially. When in doubt, leave the hostname and port number blank.

Note: changing any of these settings will terminate all of your connections and effectively restart your router.