Launch node memory usage improvement

[born2build]

I think using UPnP if it’s enabled, and port forwarding isn’t configured, and only then falling back to relay behavior makes sense. It has the benefit of ease of use without the disadvantage of putting extra work on port forwarded nodes, as relay behavior does.

In concert, I believe there’s low hanging fruit available in helping more people to run port forwarded configurations.

The following two issues document trouble I’ve encountered in my goal of running 100% port forwarded nodes. The first issue is a feature I need.

Antctl add --node-interface?

For node machines with multiple NICs, passing --node-ip to antctl add is helpful to direct node traffic over the intended interface/IP address. Once added, however, I’m not aware of a way to update the configured IP address for nodes. Is it possible? If not, it would be great to be able to pass --node-interface to antctl add, with the expected behavior that upon each start of nodes, they obtain the current IP address of the interface.

The second issue is documentation I need.

Optimal firewall rules for port-forwarded nodes

I have port forwarding set up, and now I’d like to lock down my firewall. What’s required to be open for nodes to have optimal network access? I’m asking because it appears, though I could be mistaken, that nodes require more than UDP to the ports that are being forwarded to the nodes. I’m seeing many HandshakeTimeOut errors in node logs, and much blocked traffic in to UDP ports outside of the range of ports that are being forwarded to nodes.

This documentation could be augmented with a simple feature added to antctl/antnode, or a small dedicated tool, that people could run. It would report their connection status, and take the guess work out of knowing if they have port forwarding properly configured or not, and perhaps also if they have UPnP enabled or not.