Reassociate innernet server

[make-github-pseudonymous-again]

I have a machine on which I configured innernet while being on the local network of the innernet server. The machine is a laptop, and now that I am connected to a different network it cannot find the server (although I configured it using a domain name, but that domain name was resolved to the local network IP address when configuring). I have different machines that are not on the server's local network and for which innernet is configured correctly so I do not think this problem is related to the server being unreachable. Is there a way to reconfigure the peer to connect to the innernet server through a different (global) IP address without having to create a new peer?

[mcginty]

You can manually edit the innernet configuration file at /etc/innernet/your-network.conf at your own peril, which is where the server's external endpoint is defined, if that's what you mean.

Sorry if I didn't understand your problem, the description confused me a little bit.

[make-github-pseudonymous-again]

Thanks for pointing me to the configuration. Now it is a bit more clear. Indeed there I found an external-endpoint configured by domain name. So this seems to be correctly configured and after further inspection I am able to discover the innernet server.

However, I cannot connect to peers that are in the same local network as the innernet server. I can see them with innernet list --tree, but they do not show up online, and I cannot ping them. I can see the server, and it shows up online, and I can ping it.

Sorry for the confusion. Maybe this issue should have a better title

[make-github-pseudonymous-again]

I think the second part of the question corresponds to the more general issue #109. Do I understand correctly that currently the only way to connect to peers is via a "direct" connection (no relay) and this direct connection requires public access to the innernet service port of the peer? Public access can be achieved through port-forwarding for instance, but not UPnP?

[strohel]

@make-github-pseudonymous-again exactly as you describe. Better NAT traversal and (optional) UPnP support is where we'd welcome contributions from the community.