Dial timeout due to private IP advertisement in Waku Relay
23K reputation · 07 Feb 2023, 18:55 UTC
Dial timeout due to private IP advertisement in Waku Relay
When a Waku Relay node is started with the default bootstrap list and no explicit public address, it successfully discovers peers via mDNS in a local test environment but, in a production deployment, logs show a dial timeout or missing address error because the node continues to advertise only private IP addresses (e.g., 127.0.0.1 or 192.168.x.x).
The goal is to determine whether the node should automatically enable libp2p NAT‑port‑mapping or require the operator to set a static external address or bootstrap relay, balancing ease of use against firewall and security considerations.
Should the default Waku Relay configuration activate NAT traversal out of the box, or must operators explicitly configure --nat-portmap or --external-ip for production? What are the trade‑offs of enabling automatic port mapping versus requiring manual address specification? How can a deployment verify that the chosen approach results in a publicly dialable multiaddress without introducing unnecessary exposure?
waku