aschmahmann
commented
4 years ago @Strernd as a sanity check could you make sure this is actually a libp2p issue instead of a Docker config one?
For example, instead of doing a host.Connect() on your manually discovered peer's address just do a direct TCP connect to it such as:
conn, err := net.Dial("tcp", "172.31.37.27:5500")
if err != nil {
panic(err)
}
fmt.Println(conn.RemoteAddr())
returnIf you're concerned about the libp2p server side you could replace that with a go TCP listener as well, such as:
l, err := net.Listen("tcp", 5500)
if err != nil {
fmt.Println(err)
return
}
defer l.Close()
c, err := l.Accept()
if err != nil {
fmt.Println(err)
return
}
Strernd
I'm using libp2p to communicate with other instances of the service. All of them are hosted in a docker container on an AWS EC2 machine. They're all configured to each listen on port 5500. The port 5500 is open to all instances of the service. I used the code mentioned in https://github.com/libp2p/go-libp2p/issues/460 .
It works locally in a docker-compose setup.
The nodes are announcing their address, port and Id over another service and then try to connect to their peers. I tried it with the public and private address of the EC2 machine, but had no success.
I'm not sure if this is a bug, but I'd expect it to work, as I'm doing it in a similar way (at least for the network configuration) with a different service in libp2p-js.
Version Information