NAT traversal

[D4nte]

Problem

js-waku is built to allow dapps & wallets to support the waku protocol. Hence, the target platform are user devices that have little or no control on their network topology (mobile broadband, wifi hostposts, etc). We cannot assume that said devices will always have an open port accessible to the internet.

Solution

Implement NAT passthrough support.

Acceptance criteria

• Support similar NAT passthrough techs than nim-waku: NAT-PMP, NAT-UPnp and manual ext mappings.
• Demonstrate the support by being able to receive messages in the js-chat app from a nim-waku fleet instance.

[D4nte]

After further reading https://github.com/libp2p/js-libp2p/blob/master/doc/CONFIGURATION.md#configuring-the-nat-manager

NAT traversal only makes sense for node applications. However, the focus on this library in in the browser that does not need NAT traversal as it does not support TCP connections.

Instead, WebRTC should be considered for browser environment.

Closing this issue now. This could be re-open if there is demand for js-waku node.

Superseded by #20.