Currently, the node manager does not listen on the loopback interface (aka localhost, 127.0.0.1, or 127/8). This is irrelevant for typically donator installations, but makes accessing local vessels on a Custom Install unnecessarily difficult to access, requiring Internet connectivity and a public IP (or NAT Affixes).
The nodemanager listening on localhost would also ease our problems with running Repy locally on Android, where the usual
python repy.py restrictionsfile myprogram.repy
just doesn't work out of the box: You could use a machine connected over ADB, set up port forwarding (adb forward tcp:1224 tcp:12345), and then connect to 127.0.0.1:12345 using seash on the debug machine to reach the node manager on the Android device. (Alas, this will only become useful when we have a Custom Installer Builder for Android, #1193).
I suggest making the node manager listen on localhost per default, and possibly adding an install-time switch to disable this function.
By the way, the node manager can be told to at install time to listen ''only'' on localhost,
$ ./install.sh --nm-iface lo
but then it won't be contactable from the outside at all.
Currently, the node manager does not listen on the loopback interface (aka localhost, 127.0.0.1, or 127/8). This is irrelevant for typically donator installations, but makes accessing local vessels on a Custom Install unnecessarily difficult to access, requiring Internet connectivity and a public IP (or NAT Affixes).
The nodemanager listening on localhost would also ease our problems with running Repy locally on Android, where the usual
just doesn't work out of the box: You could use a machine connected over
ADB, set up port forwarding (adb forward tcp:1224 tcp:12345), and then connect to 127.0.0.1:12345 usingseashon the debug machine to reach the node manager on the Android device. (Alas, this will only become useful when we have a Custom Installer Builder for Android, #1193).I suggest making the node manager listen on localhost per default, and possibly adding an install-time switch to disable this function.
By the way, the node manager can be told to at install time to listen ''only'' on localhost,
but then it won't be contactable from the outside at all.