search

SeattleTestbed / nodemanager

Remote control server for SeattleTestbed nodes
MIT License
0 stars 10 forks source link

Nodemanager should listen on localhost #90

Open choksi81 opened 10 years ago

choksi81 commented 10 years ago

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.

choksi81 commented 10 years ago

I think you're really saying the default Affix should contain a branch that allows receiving connection on local host. I'm fine with this. I don't know we need a code change in the NM or elsewhere for this.