Unexpected behavior when trying to connect to bootstrap nodes about go-libp2p-daemon HOT 11 OPEN

This is because there needs to be some confidence on the observations in autonat; you need to connect to enough peers to verify that (I think it's 3 or 4), so you can't get it from a single bootstrapper.

We could expose the ForceReachability option in go-libp2p, should be simple to implement if you care for a patch.

from go-libp2p-daemon.

Seems you are announcing 0.0.0.0 addresses with the -hostAddrs option.

from go-libp2p-daemon.

And you are also only listening on localhost. That's definitely not what you want.

from go-libp2p-daemon.

-listen address is using for connecting to daemon from binding, isn't it? It may be unix socket as well. Do we (with @deniskamazur ) misunderstand something? What is the proper way to start p2pd node with public IP and several nodes under NAT so that "under NAT" nodes acquire "behind NAT" IP and may connect to each other?

from go-libp2p-daemon.

Sorry, my bad -- you are right. I haven't touched this code in a while and I forget what all the options do :)

from go-libp2p-daemon.

Your addrs options are perfectly fine, sorry for my misleading comments.

from go-libp2p-daemon.

ok, so your bootstrappers are using tcp and you are listening on quic; I wonder whether this is a problem in this case.

from go-libp2p-daemon.

which shouldn't be because it is also using the default transports.

from go-libp2p-daemon.

I describe task detailed. We have node with public IP (node A):

$ ./p2pd -tls=1 -connManager=1 -natPortMap=1 -autonat=1 -dhtServer=1   -hostAddrs=/ip4/0.0.0.0/tcp/5000
Control socket: /unix/tmp/p2pd.sock
Peer ID: QmUN5jQC26K3FM3XSjjPcKBWZAaxB9NiQBcL3XZPhaWvPX
Peer Addrs:
/ip4/92.53.78.235/tcp/5000
/ip4/127.0.0.1/tcp/5000

and node under NAT (node B) with bootstrapping to node A:

$ ./p2pd -tls=1 -connManager=1 -natPortMap=1 -autonat=1 -dhtClient=1 -b -bootstrapPeers=/ip4/92.53.78.235/tcp/5000/p2p/QmUN5jQC26K3FM3XSjjPcKBWZAaxB9NiQBcL3XZPhaWvPX -hostAddrs=/ip4/0.0.0.0/tcp/44002
Control socket: /unix/tmp/p2pd.sock
Peer ID: Qmdn5vaZ3tR81wfDVQ5m1Z4dWmKXUFwuhPNGvwf5FYM1CM
Peer Addrs:
/ip4/192.168.1.150/tcp/44002
/ip4/127.0.0.1/tcp/44002
Bootstrap peers:
/ip4/92.53.78.235/tcp/5000/p2p/QmUN5jQC26K3FM3XSjjPcKBWZAaxB9NiQBcL3XZPhaWvPX

Peer addrs list contains only LAN addresses. But if connect to global IPFS network node B has "behind NAT" IP:

$ ./p2pd -tls=1 -connManager=1 -natPortMap=1 -autonat=1 -dhtClient=1 -b -hostAddrs=/ip4/0.0.0.0/tcp/44002
Control socket: /unix/tmp/p2pd.sock
Peer ID: Qmdp341BhnUdZxxPU873qP6NtYT1DrdMGNixG9S41wJKfL
Peer Addrs:
/ip4/192.168.1.150/tcp/44002
/ip4/127.0.0.1/tcp/44002
/ip4/109.252.14.143/tcp/19973   <--- behind NAT IP. Why it shows only if connect to IPFS network?

How to run node A (public IP machine) so that node B gets its "behind NAT" ?

from go-libp2p-daemon.

Thanks for your help!

from go-libp2p-daemon.

The ForceReachability option actually did not solve our problem as running only one bootstrap doesn't return the public IP

from go-libp2p-daemon.