Identity REST API endpoint returns 0.0.0.0 address about nimbus-eth2 HOT 7 OPEN

This is libp2p known issue and probably limitation.

from nimbus-eth2.

What do you mean by "limitation"? I'd assume that If it works for discovery it can be made to work for the p2p address.

from nimbus-eth2.

Usually developers prefer to use 0.0.0.0 which forces OS to bound server to all available interfaces. But this comes with limitation that when you will request local address of bound socket you will receive 0.0.0.0:<some port> instead of real interface address. To get this addresses you need to enumerate all the interfaces and bound to their IP addresses manually. But there is no such functionality in nim-libp2p yet, so REST server reports what nim-libp2p provides to it.
And to note that that provided multiaddresses are 100% correct, but i agree this addresses are unusable...

from nimbus-eth2.

By word "limitation" i mean that nim-libp2p developers do not implemented this functionality yet and i have not seen such functionality in plans.

from nimbus-eth2.