Hi,
I have a central LAN, where the X2Go server and many clients live, and several branch offices which connect via the WAN. I used to be able to modify the FreeNX 'nxacl' script to force 'LAN' for local clients, and 'ADSL' for everyone else. Last I looked, there was no such facility in the X2Go server, and the team had posted good reasons (which I can't quite recall) why that file was not coming back.
But does X2Go server have a way for me to accomplish what I want? I still find the occasional misconfigured client.
Thanks, Steve Bergman
On Tue, May 29, 2018 at 7:06 PM, Steve Bergman <sbergman27@gmail.com> wrote:
Hi,
I have a central LAN, where the X2Go server and many clients live, and several branch offices which connect via the WAN. I used to be able to modify the FreeNX 'nxacl' script to force 'LAN' for local clients, and 'ADSL' for everyone else. Last I looked, there was no such facility in the X2Go server, and the team had posted good reasons (which I can't quite recall) why that file was not coming back.
But does X2Go server have a way for me to accomplish what I want? I still find the occasional misconfigured client.
This is a client side configuration, so simply configure the ADSL clients to use ADSL and the others to use LAN.
Uli
Thank you for your reply, Uli. I appreciate it. But I already know that. The issue is that of my 120 or so remote Linux desktop clients, some get misconfigured. Some of these offices are 700+ miles away, and I don't set these clients up. On-site personel do. And they do a pretty good job. But I still find the occasional remote client set to LAN.
The collective contents of the session.log files do allow me to generate reports. But it would be nice if I could just go back to forcing these to the right setting based upon server policy. Especially as I'm the only admin for everything, and this customer continues to expand its employee base.
-Steve
On May 29, 2018 12:34 PM, "Ulrich Sibiller" <uli42@gmx.de> wrote:
On Tue, May 29, 2018 at 7:06 PM, Steve Bergman <sbergman27@gmail.com> wrote:
Hi,
I have a central LAN, where the X2Go server and many clients live, and several branch offices which connect via the WAN. I used to be able to modify the FreeNX 'nxacl' script to force 'LAN' for local clients, and 'ADSL' for everyone else. Last I looked, there was no such facility in the X2Go server, and the team had posted good reasons (which I can't quite recall) why that file was not coming back.
But does X2Go server have a way for me to accomplish what I want? I still find the occasional misconfigured client.
This is a client side configuration, so simply configure the ADSL clients to use ADSL and the others to use LAN.
Uli
On Tue, May 29, 2018 at 7:59 PM, Steve Bergman <sbergman27@gmail.com> wrote:
Thank you for your reply, Uli. I appreciate it. But I already know that. The issue is that of my 120 or so remote Linux desktop clients, some get misconfigured. Some of these offices are 700+ miles away, and I don't set these clients up. On-site personel do. And they do a pretty good job. But I still find the occasional remote client set to LAN.
The collective contents of the session.log files do allow me to generate reports. But it would be nice if I could just go back to forcing these to the right setting based upon server policy. Especially as I'm the only admin for everything, and this customer continues to expand its employee base.
Well, the connection speed is part of the options string in the options file. You should be able to adapt the options string right before the nxagent gets started. Have a look at the x2gostartagent script, search for the lines where X2GO_HOST is set. You will see you need to adapt X2GO_LINK accordingly. The client initiating the connection is in X2GO_CLIENT.
For reconnect you need to adapt X2GO_LINK in x2goresume-session.
Please note that I have not tested this, but I am pretty sure that it works like this.
Extending those scripts in a generic way is encouraged, e.g. you could add a callback script for modifying the options string. Patches are welcome!
Uli
Thanks for that, Ulrich. I just realized that I had already figured that much out back when we were on Wheezy. I had to chattr -i x2gostartagent after our recent Stretch upgrade, and lost my modifications. Sorry to bother the list with this memory lapse of mine.
-Steve
Am 29.05.2018 um 20:20 schrieb Ulrich Sibiller:
Extending those scripts in a generic way is encouraged, e.g. you could add a callback script for modifying the options string. Patches are welcome!
Uh, guys, before messing in the guts of X2Go code, please remember that X2GoBroker can deliver session profiles based on user, group, and IP network the user is connecting from, so IMO, a broker setup would be the way to go.
Or, if your remote sites connect via VPN, use a file share (e.g. NFS on Linux, Samba on Windows) and a central, read-only sessions file. The sessions file is small enough that even over a bad WAN link, transferring it doesn't take much time.
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
-
Stefan Baur -
Steve Bergman -
Ulrich Sibiller