On Mar 27, 2017 8:23 AM, "Stefan Baur" <x2go-m...@baur-itcs.de> wrote:
Am 16.03.2017 um 18:28 schrieb John Cobo: > I am considering X2Go for a project which involves non-technical people > using X2Go to connect to a Raspberry Pi which does not have a screen and > so the user will not know the Pi's IP address. I could set an SSH port > on the Pi to an obscure number such as 2432 or something. > > Would it be feasible for the X2Go clients have a new option to scan a > range of IPs (eg. 192.168.0.1 - 192.168.0.255) for a given port (eg. > 2432) on which to connect? > > Such a feature could solve the generic problem of how to connect for the > first time to something new on your local network. I've been giving this some more thought. I still believe that we shouldn't be adding such an option to X2GoClient, but there may be more comfortable ways of providing your users with a DNS name to connect to, rather than having to figure out an IP, even without APIPA/mDNS/Zeroconf/Bonjour. For that, you should tell us more about that usage scenario - will all those Raspis have full internet access? If not, are they being deployed on different subnets of one larger network where you could place one machine they all can reach? I'm thinking along the lines of using either a DynDNS server on the internet, with the Raspi reporting its internal IP instead of the external one, though, or setting up an internal DynDNS server. -Stefan How about using samba nmbd on the raspberry pi? If you only have Windows clients, they'll be able to connect to the machine by netbios name, same as a DNS name, by default. This depends on no firewall blocking netbios traffic.
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
