n2n
n2n copied to clipboard
Some suggestions on manually adding static routes back to edge nodes
At present, the method of using n2n to return to the LAN where the edge node is located can be found on the Internet,But this will not work on Android or apple phones. After all, the openness of their systems and the difficulty of adding static routes are more difficult than windows and Linux,Special means are needed to make him escape from prison or obtain root permission,Now the version is more and more new, and these operations have gradually become impossible.So can the visitor's edge node automatically receive the static route of the LAN where the visited edge node is located by setting up a separate route file? Thanks for an amazingly great product!
So can the visitor's edge node automatically receive the static route of the LAN where the visited edge node is located by setting up a separate route file?
With the freshly added enhancements to the management port offering events, e.g. the event on a peer having changed, we probably will see the routing table alterations being performed by additional tools which can take care of platform specific characteristics.
And indeed, the basic idea of this approach would be to allow the remote peers being communicated to through the default route, just like the supernodes.
But this will not work on Android or apple phones.
We unfortunately have not been able to offer Android or iOS versions here so far.
Now the version is more and more new, and these operations have gradually become impossible.
Others have ported it to Android, see here, and iOS (#381). Maybe they know better about routing on these platforms.