%@page contentType="text/html" %>
If enabled, your router will periodically anonymously probe some of your peers to see what sort of throughput they can handle. This improves your router's ability to pick faster peers, but can cost substantial bandwidth. Relevant data from the load testing is fed into the profiles as well as the test.rtt and related stats.
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.
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 this setting will terminate all of your connections and effectively restart your router.