Networking script for support

[pablomendezroyo]

Context

Considering networking issues as any difficulty a user may have to connect to a DAppNode via: Wi-Fi, OpenVPN, Wireguard and/or Local proxy.

Networking issues are one of the most difficult issues to debug, they are tedious and need a lot of instructions to be given to the user. In most cases, it requires commands to be executed on the host machine to collect information from the host.

Networking issues are really critical since they do not allow a user to connect to the DAppNode user interface.

Issues reported

In most cases the source of the issue is:

• UPnP is not enabled so ports are not opened
• DAppNode not wired to the router
• Ports are opened but not properly routed to the dappnode local IP
• VPN credentials are not well configured
• Network interface is taken by the host machine, so dappnode wifi does not work as expected
• No internet
• Cgnat
• Double NAT
• ?

Networking script

Would be great to have a host networking script that collects network host information to debug all the issues a user may have. The script could be executed through a command from the terminal like dappnode_net and from the UI.

Important data to collect:

• Is there internet?
• Is the network interface owned by the host, is blocked? (see DAppNode-WIFI)
• Are ports opened and routed to dappnode local IP? (use of upnpc with docker container)
• ?

┆Issue is synchronized with this Basecamp todo by Unito

[3alpha]

I propose few things

• Check DAppNode LAN connection
• Print local IP address
• Print public IP address
• Print iptables-save (users on custom machines may have iptables blocking the access
• Check whether core DAppNode packages are up and running, primarily DAppManager, Wifi, and VPN packages
• For dappnode.local to work, HTTPS package must be working, check that

This is all in case users can't even access DAppNode UI from the local network.

For problems in accessing DAppNodes remotely, few checks maybe done

• Check whether ports are correctly forwarded via UPnP or somehow else
• CGNAT

I am really not sure how to check for these last few things. That is what can be from DAppNode machine itself.

From some other machine on the local network following thing can be checked (After first check is done)

• Ping DAppNode IP address. This should always work except in cases when pinging is ignored in iptables. This is almost never the case.

• Resolve dappnode.local. Can be done with ping. If DAppManager is up, this domain should resolve to the local IP of DAppNode.

This is everything that now comes to mind now. We can update this list as we go. All suggestions welcome.