P2P clients sharing the same IP should not be considered as duplicate about tendermint HOT 4 CLOSED

Is this a GFI? I would like to try to work on this @arno01

from tendermint.

Is this a GFI? I would like to try to work on this @arno01

I think so, good luck!

from tendermint.

Could you please help me with the process to reproduce this situation?

from tendermint.

Could you please help me with the process to reproduce this situation?

You can test either scenario:

1) NAT

I think you can use Docker to simulate NAT (for points 2. & 3.)

1. HostA: Start tendermint app server;
2. HostB (behind NAT, sharing the same public IP as HostC): Connect tendermint app client to HostA;
3. HostC (behind NAT, sharing the same public IP as HostB): Connect tendermint app client to HostA;

As soon as you reach point 3. you will hit the duplicate CONN error as the tendermint app server will see the same public IP (except for the remote ports which never overlap) from the HostC as HostB used.

2) Behind the load-balancer

Load-balancer can be: K8s ingress-nginx controller / nginx LB / haproxy / ... any load-balancer pretty much

1. HostA: Start tendermint app server listening over 127.0.0.1:26656 instead of 0.0.0.0:26656;
2. HostA: Deploy LB (any load balancer you like) listening at 26656/tcp over a known public IP and forwarding the incoming connections to the tendermint app server that listens over 127.0.0.1:26656;
3. HostB: Connect tendermint app client to <Public-IP-Of-HostA>:26656;

As soon as you reach point 3. you will hit the duplicate CONN error as the tendermint app server will only see the incoming IP of the load-balancer which is always same (except for the remote ports which never overlap).

from tendermint.