Reachability and contributing to I2P network

[bitter]

Hi all,

I'm running my I2P router H24/7 on a mini server with Open Media Vault OS.
Router runs with Docker. I followed Docker example here http://i2p-projekt.i2p/en/download/docker

Required port is open on IPS home router.
I successful tested reachability of TCP port by a internet check site.

Unfortunately I2P network results Firewalled.
Furthermore inspecting the events log, there are reachability and port changing events. For example:

Code: Select all

Changed port	IPv4 port {some port number}
...
Changed port	IPv4 port {some port number}
...
Reachability change	from Firewalled to Symmetric NAT
...
Reachability change	from Symmetric NAT to Firewalled
...
Reachability change	from Firewalled to Symmetric NAT

At the current status, am I contributing to I2P network?

Are there some information on I2P router that shows my contribution?

[lgillis]

Hi bitter!

This is more than a three body problem. Your operating system, which somehow connects to the Internet. The Java router that accesses the operating system's network. The container that has to mediate between the operating system and the Java router. The current router version is 2.6.1, but the instructions* for Docker were written for router version 0.9.50. And so on. And only you are sitting right in front of it and can see what you are doing.

To narrow things down, I would ask myself whether the router runs smoothly without Docker. If this is the case, then I would use the ready-made Docker that the project offers for download.

http://i2p-projekt.i2p/en/download I2P for Docker
https://hub.docker.com/r/geti2p/i2p/ Upstream Docker images for the Java implementation of the Invisible Internet(I2P).

--
(* Note the example shown there, which places a comment after a forced line break.)

[bitter]

Thank you lgillis
for pointing out several technical aspects.

I finally found the problem and I want to share the solution for all Docker users.
Here on GitHub https://github.com/i2p/i2p.i2p/blob/master/Docker.md the documentation insists to show this kind of example also for 2.6.1

Code: Select all

... port portion only
ports:
     - 127.0.0.1:4444:4444
     - 127.0.0.1:6668:6668
     - 127.0.0.1:7657:7657
     - 54321:12345
     - 54321:12345/udp
...

Problem
The example above suggests that you are free to remap internally configured port 12345 to a different host port 54321. This implies adding a forward rule based on port 54321 on the home router.

I2P router announces itself on the network indicating that it is reachable at Public-IP + InternallyConfiguredPort, but this port is not forwarded.

Solution
I changed the internal port 12345 to a new value and published the same value on host in Docker compose file. Finally i changed the forwarding rule on the home router.

Now I have Network: OK and a share ratio of 40 after only 3 hours, instead of a share ratio of 0.20 after 8 days