X2Go Bug report logs - #1080
x2goclient should have --server option added for CLI use to specify IP of server to connect to

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: brian mullan <bmullan.mail@gmail.com>

Date: Wed, 31 Aug 2016 03:20:02 UTC

Severity: wishlist

Found in version 4.0.5.1

Full log


Message #25 received at 1080@bugs.x2go.org (full text, mbox, reply):

Received: (at 1080) by bugs.x2go.org; 11 Jan 2017 23:13:17 +0000
From X2Go-ML-1@baur-itcs.de  Thu Jan 12 00:13:16 2017
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 required=3.0 tests=BAYES_00,RCVD_IN_SORBS_SPAM,
	URIBL_BLOCKED autolearn=no version=3.3.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id B64673CDDE
	for <1080@bugs.x2go.org>; Thu, 12 Jan 2017 00:13:16 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 856aiHMUeRxQ for <1080@bugs.x2go.org>;
	Thu, 12 Jan 2017 00:13:10 +0100 (CET)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id F098E3CDDD
	for <1080@bugs.x2go.org>; Thu, 12 Jan 2017 00:13:09 +0100 (CET)
Received: from [192.168.0.23] ([78.43.90.159]) by mrelayeu.kundenserver.de
 (mreue002 [212.227.15.129]) with ESMTPSA (Nemesis) id
 0MBO0z-1cHn2e0MJp-00AEvt; Thu, 12 Jan 2017 00:13:09 +0100
Subject: Re: [X2Go-Dev] Bug#1080: can "--server" option to specify the IP of
 the target, desktop server be added to x2goclient cli
To: brian mullan <bmullan.mail@gmail.com>
References: <275ad7c1-2ef8-e194-ca39-671fd32792bc@gmail.com>
 <e57fa224-b92e-32e1-4de8-ab7508a3df91@baur-itcs.de>
 <CAFX-c4vdNaDxhsNv7gjQrOdVnpYHmFzYR_9d+OihcQZnEcfkNw@mail.gmail.com>
Cc: 1080@bugs.x2go.org
From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
Message-ID: <b6cea5e4-f637-5e4e-cb67-ffd473967799@baur-itcs.de>
Date: Thu, 12 Jan 2017 00:12:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <CAFX-c4vdNaDxhsNv7gjQrOdVnpYHmFzYR_9d+OihcQZnEcfkNw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="uA1qmGirVwXeN8KBdNtd7Xv87FgfEB3p8"
X-Provags-ID: V03:K0:dXLu5Gi0xKNAgOKvqLwy80kUaRrn01PILk76YZrdi2BiqqxWNrd
 0fivRlH6pTME3meSY987NWKLZbfihY1l2bsEeGIv+G9ZPP4LlYq0WA55wpSGXfM9uX1XnIE
 eny0IvSCJzm6FMm5sWc/5pv9/4uhDAe4pA0iSSKC1cS2qAOE3t7lnpqUzeLWHJ7QYjYLnYQ
 bwDSJMMjk/ImcfQkae+1w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:YYDh9iV3Mgc=:ksdgWhPLxcJHVOZXo5LlVd
 BAfVXceRI5/ODusb/lwFOMuRd1daftRWsfnzjUgHQ8kBX3W+yPdMPF+EWwaAZ6OT+17HVwpkv
 LciE5zlf0xSrxpneI6km7nznL12vmh9A9t3V0X02jAFwHhTla9ZmRmczDjO84B/JATgEb6pZ6
 6spJqUVHdJykOTJ9iYhErvmbWECCY7FrtTMwwpK+c3XKAZxLs2gISMI0yUH9Y47ktzx2jh6x6
 921mtBtQcLCOpTxHTR4xafMrKald0qJDTF+MFhXve0b7+RH6YSQSRX68IrpEOWved1QqsW6GV
 40utH5IWUpuh3Ebs6kQkKrOonxe7cY+F/g/yzG+tE/24uQlzXDmuHstDb1xmAxY7I2gTwZ1i+
 +IGXNtJKk999HUxoyqJpG1ptuq4Mup5nNI46a/FO8WoDS+o9ov4wHwW16lQ3EwSAvhz7E/C+d
 +hcCMImA0qyZqtw8pr72odPYJxNJA6CV1XzU5JC0mO9MMxMylt2u4aVxDntSSoYpSl/8d/N6G
 Vq+pc6kNZRRQ1zJvwdoodwFq8ehpg6Lq5GQg42ie/NFxULp66R5i8txOwYU64st7iRQSLhp+b
 nt1cJ0T/krAu8y6TUS/CO6nCWm/VgyUUs9lJeC9X9n+rFSGbr6qvnRH0yl+wLIGKRqkka0xdv
 x+ur39A45BuigC5OZiX2scKF4HTAWsC8KOsy6ejgbFHbk7enoEhK2ChWCvPehDjN0ys8=
[Message part 1 (text/plain, inline)]
Am 11.01.2017 um 23:36 schrieb brian mullan:

> I'd built up a remote desktop solution for some schools where the
> initial desktop was on an ubuntu cloud server.
> 
> However, on that Cloud server I had dozens of LXD containers which have
> a variety of different Desktop Environments in some of them
> as well as different purposes.
> 
> LXD is a "system" container technology versus the Docker type
> "application" container technology.
> 
> So some of the LXD containers might be more oriented to a specific
> "group" of educational users like science, or writing, or even teachers.
> 
> Those LXD containers are on their own 10.x.x.x network.
> 
> I wanted to use x2go to get to the "host" server Desktop but then just
> have Desktop Icon's setup to use x2goclient cli to connect them further
> to a specific LXD container Desktop of their choosing.
> 
> But although pyhoca-cli supports specifying a "- -server" target the
> x2goclient cli does not include that option.
> 
> However, the x2goclient cli supports other options I wanted to use that
> the pyhoca-cli does not such as "no-session-edit", "hide-menu-toolbar" etc.
> 
> My use-case problem really revolved around those kind of feature option
> differences between the two CLI methods.

Okay.  I think one way to solve this would be to install X2Go-Broker on
the host, along with postgres (the X2Go servers in the containers would
have to connect to that postgres DB as well), and have the broker
deliver the proper trimmed-down session config for the user (it can
match on user, group, IP or network range).  That way you don't have to
connect to the host desktop first.

Another, easier approach, though not as elegant, would be to configure
*all* the sessions that you need in one sessions file, then specify
either --session or --session-id on the shortcut.  Or, if you want to
use separate session configuration files, use the same name for the
session in each file, make --session point to that name, and specify the
sessions file using --session-conf.

You can also create desktop shortcuts by clicking on "Create Session
Icon on Desktop" (it's in the triangle-button -soon to be
"hamburger"-button- in the lower right of a session tile).
Have a look at the file/shortcut it puts on the desktop.

Also, in addition to using --no-session-edit, as long as your users are
sharing the same "client" system (in your case, the host to the
containers) to log on to their host, or have access to a common file
system, you can place a read-only sessions file there and use
--session-conf to point at it. Bam, central administration of the
session file, without having to install broker and postgres.

Oh, and by the way - X2GoClient has a SSH proxy feature.
So you don't have to run X2Go through X2Go to reach the container'ed
server your users are supposed to work on.
Just specify the host machine as SSH proxy in the session settings.
In that situation, you will have to make use of a shared, read-only
directory for the sessions file, though, if you want to keep
administration in a central spot.  But, if your users are all windows
users on the same network, you can even deploy the entire X2GoClient,
not only the sessions file, via a read-only network share, so you don't
even have to install it individually any more.

IMO, this isn't exactly a bug/X2Go-Dev topic any more - care to switch
over to the X2Go-User mailing list and explaining your setup further?
My hope would be that we can turn the results of this conversation both
into a success story (X2Go use at ..., by Brian Mullan) as well as a
HowTo (How to run X2Go servers in containers, with central
administration, blah, blah, blah) on our Wiki.

See
http://wiki.x2go.org/doku.php/doc:deployment-stories:start#success_stories
and
http://wiki.x2go.org/doku.php/doc:howto if you have no clue what I'm
talking about. ;-)

And of course, if you have the need for further consulting and support,
especially if you don't want to discuss your setup in public on one of
our mailing lists, we offer commercial services for that as well.
(I already feel bad for posting my "shameless plug" so often in the last
few days, so I'll refrain from it.  I'm sure you've read it often enough
if you follow the lists.)


> So I submitted the wish-list bug just to ask as not being a coder I
> don't know if something is alot or a little work but there was no harm
> asking.
> 
> I just hadn't gotten any response.   As I know you guys are busy with
> the future of Artica (btw I'm anxious to see what it is/does)... I
> thought I'd just send
> a ping to make sure someone at least took a look at the request.

It's Arctica (as in "effin' cold" ;-)), not Artica (as in artsy).  And
while some X2Go developers have left for Arctica, and others divide
their time between Arctica and X2Go, X2Go is anything but dead.

For example, Mihai is working on the macOS client, and there's also
ongoing work on what is the common base of FreeNX, NeatX, OpenNX, X2Go,
TheQVD and Arctica alike - the update/revamp of the NX-Libraries.

And while I don't exactly monitor the commit log that closely, I believe
there have been some commits by Alex (one of the two original founders
of X2Go) lately as well.

> By the way... Happy New Years to all of you guys on the x2go & artica
> team(s)...!

Thank you! :-)

Kind Regards,
Stefan Baur

-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Sat Nov 23 20:14:59 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.