Talk:I2P HowTo (Deprecated, see I2PHelper documentation)

From VuzeWiki
Jump to: navigation, search

I am trying to set up my I2P server as described at 5.2.4 [[1]], but this post does not seem to indicate the correct steps when using "Randomize listen ports on startup" in Vuze (Options > Connection). Vuze's I2P plugin page does give the options to use UPnP, but when creating the server tunnel in the I2P router's Tunnel Manager, a target port is seemingly still required. According to the directions:

Enter details similar to the following (example for a peer-data tunnel)
  • Name: AzureusData
  • Description: Azureus Peer Data Tunnel
  • Auto Start: selected - (i.e YES)
  • Target:
Host: 127.0.0.1 Port: <your Azureus port configured under Tools->Connection>

As UPnP changes the port each time Vuze restarts, there doesn't seem to be a way to keep using UPnP in Vuze as well as creating a permanent server tunnel for Vuze in the I2P router.

I'm not sure if I am missing something obvious here (apologies if so), but as a new I2P user this is somewhat confusing. If the I2P plugin in Vuze handles this without needing to add a I2P server tunnel for Vuze manually, this should be indicated in the wiki. I have searched far and wide for a solution, but still haven't figured it out. However, this discussion is directed at the wiki addressing this question in the directions.

<parg> Yes, you are right, there is no current way of combining the port randomization and I2P incoming tunnel destination - really this should all be reworked to interface more directly with I2P by having the plugin itself establish the incoming routing, but I haven't had time to work on this :(