x2go-commits January 2017

x2go-commits@lists.x2go.org

3 participants
366 discussions

Start a nNew thread

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 15:42 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483371682 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -630,13 +630,12 @@ FIXME User Support: Checking the ThinClient's local printer setup (when using the ''tcpprint'' boot parameter) There are several ways to check whether a ThinClient has detected any local printers: * Assuming you have remote access to the ThinClient, run ''ls -lah /etc/xinetd.d/jetdirect*'' and examine the files listed there. - * You can also look at the messages printed during the local printer setup phase, either by: - * running ''cat /dev/vcs9'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely, or - * telling the user to press [Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. + * When connected remotely, you can also look at the messages printed during the local printer setup phase, by running ''cat /dev/vcs9'' (you might have to pipe it through ''less'' to see the entire screen). + * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. FIXME User Support: Checking the ThinClient's update status (when using local storage) There are several ways to check a ThinClient's update status: * Assuming you have remote access to the ThinClient, look at the messages printed during the update phase, by running ''cat /dev/vcs10'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F10] and to read out what's on the screen, preferably starting with the bottom line and continuing upward. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 15:41 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483371196 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -624,4 +624,19 @@ When you are unable to connect to the ThinClient, you might want to ascertain its MAC and/or IP address(es), to make sure you and the user you are trying to support are talking about the same machine. Tell the user to press [Ctrl]+[Alt]+[F1] and to read out * the GREEN text if you want to know the MAC address(es) * the RED text if you want to know the IP address(es) - if there is no red text, it means that the client was unable to acquire a DHCP lease. Check cabling. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. + + + FIXME User Support: Checking the ThinClient's local printer setup (when using the ''tcpprint'' boot parameter) + There are several ways to check whether a ThinClient has detected any local printers: + + * Assuming you have remote access to the ThinClient, run ''ls -lah /etc/xinetd.d/jetdirect*'' and examine the files listed there. + * You can also look at the messages printed during the local printer setup phase, either by: + * running ''cat /dev/vcs9'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely, or + * telling the user to press [Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. + + FIXME User Support: Checking the ThinClient's update status (when using local storage) + There are several ways to check a ThinClient's update status: + + * Assuming you have remote access to the ThinClient, look at the messages printed during the update phase, by running ''cat /dev/vcs10'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely + * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F10] and to read out what's on the screen, preferably starting with the bottom line and continuing upward. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 15:33 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483370673 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -604,11 +604,11 @@ * 1150-openssh-readsshprivatekeys or 1150-x2go-readsshprivatekeys would probably be the proper names * Maybe it would be better to split the process into 2 scripts, one that fetches the keys from local storage/USB media, and one that patches the sessions file * 2800-x2go-thinclientconfig would also have to be changed so it uses the keyfile(s) when in broker mode - FIXME Remote viewing the local display + FIXME User Support: Remote Access to the ThinClient's local display (before any connection is made) X2Go-TCE comes with x11vnc installed. - If you want to see what's on the ThinClient's X11 screen, before a connection to the X2GoServer has been established, proceed as follows: + If you want to see what's on the ThinClient's X11 screen, before a server connection has been established, proceed as follows: * On Linux/macOS/Unix: - spawn a VNC listening //client//, like so: ''xvncviewer -listen'' - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -rfbport 0 -coe localhost''' * On Windows: @@ -617,4 +617,11 @@ - Select Connections/SSH/Tunnels in PuTTY - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and, very important, hit **Add** //before// you hit **Apply**, or your changes will **not** be saved - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance. + + FIXME User Support: Determining the ThinClient's IP and/or MAC via phone + + When you are unable to connect to the ThinClient, you might want to ascertain its MAC and/or IP address(es), to make sure you and the user you are trying to support are talking about the same machine. Tell the user to press [Ctrl]+[Alt]+[F1] and to read out + * the GREEN text if you want to know the MAC address(es) + * the RED text if you want to know the IP address(es) - if there is no red text, it means that the client was unable to acquire a DHCP lease. Check cabling. + To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 15:24 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483366117 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: User : stefanbaur @@ -145,9 +145,9 @@ ==== Prerequisites ==== * You need an existing DHCP/PXE/TFTP setup with the usual pxelinux.0/pxelinux.cfg boot and configuration files, and a directory where kernel and initrd can be stored. This is not covered here, though we might add a separate howto for that some time later on. * Note that whoever manages to spoof this server name can deploy rogue images to your ThinClients. If this is a serious issue for you, consider using local storage media and the autoupdater instead. - * It **might** be possible to already use HTTPS in this early stage when using iPXE. This is untested. + * It **might** be possible to already use HTTPS in this early stage when using iPXE. This is untested and requires building your own iPXE image. see http://ipxe.org/crypto for details. * You will also need an HTTP/HTTPS/FTP server with a dedicated IP (no name-based virtual hosts) for the squashfs image. * This image cannot be deployed via TFTP as it is too large - some TFTP servers refuse to serve files lager than 32MB, and some TFTP clients have problems with that as well. * Also, even if you have a TFTP server/client combination that handles files larger than 32 MB, it will still be waaaay slower than the HTTP/FTP transfer. * Note that whoever manages to spoof this server name can deploy rogue images to your ThinClients. If this is a serious issue for you, consider using local storage media and the autoupdater instead. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 14:08 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483366037 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -608,13 +608,13 @@ FIXME Remote viewing the local display X2Go-TCE comes with x11vnc installed. If you want to see what's on the ThinClient's X11 screen, before a connection to the X2GoServer has been established, proceed as follows: * On Linux/macOS/Unix: - - spawn a VNC listening //client//, like so: + - spawn a VNC listening //client//, like so: ''xvncviewer -listen'' - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -rfbport 0 -coe localhost''' * On Windows: - Start a VNC listening //client//, for example ''vncclient.exe -listen 5500'' - Start PuTTY, connect to root@thinclient - Select Connections/SSH/Tunnels in PuTTY - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and, very important, hit **Add** //before// you hit **Apply**, or your changes will **not** be saved - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 14:07 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483365816 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -609,12 +609,12 @@ X2Go-TCE comes with x11vnc installed. If you want to see what's on the ThinClient's X11 screen, before a connection to the X2GoServer has been established, proceed as follows: * On Linux/macOS/Unix: - spawn a VNC listening //client//, like so: - - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -localhost -connect localhost''' + - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -rfbport 0 -coe localhost''' * On Windows: - Start a VNC listening //client//, for example ''vncclient.exe -listen 5500'' - Start PuTTY, connect to root@thinclient - Select Connections/SSH/Tunnels in PuTTY - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and, very important, hit **Add** //before// you hit **Apply**, or your changes will **not** be saved - - run ''x11vnc -display :0 -localhost -connect localhost'' in the PuTTY window + - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 14:03 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483363821 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -604,4 +604,17 @@ * 1150-openssh-readsshprivatekeys or 1150-x2go-readsshprivatekeys would probably be the proper names * Maybe it would be better to split the process into 2 scripts, one that fetches the keys from local storage/USB media, and one that patches the sessions file * 2800-x2go-thinclientconfig would also have to be changed so it uses the keyfile(s) when in broker mode + FIXME Remote viewing the local display + X2Go-TCE comes with x11vnc installed. + If you want to see what's on the ThinClient's X11 screen, before a connection to the X2GoServer has been established, proceed as follows: + * On Linux/macOS/Unix: + - spawn a VNC listening //client//, like so: + - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -localhost -connect localhost''' + * On Windows: + - Start a VNC listening //client//, for example ''vncclient.exe -listen 5500'' + - Start PuTTY, connect to root@thinclient + - Select Connections/SSH/Tunnels in PuTTY + - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and, very important, hit **Add** //before// you hit **Apply**, or your changes will **not** be saved + - run ''x11vnc -display :0 -localhost -connect localhost'' in the PuTTY window + To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 13:30 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483360358 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: User : stefanbaur @@ -241,9 +241,9 @@ These are //not yet implemented//, but planned for a future release: * ''blank=n|n:n:n'' - Will disable (''blank=0'') or set screensaver timeout. Use ''blank=n:n:n'' to set DPMS Standby/Suspend/Off values. Standby value equals screensaver timeout value. All values are given in seconds. * ''nodpms'' - Will not touch DPMS settings at all (by default, ''blank=0'' does both ''xset s off'' and ''xset -dpms''). Use this along with ''blank=n'' if you do want to blank the screen, but your screen is confused by DPMS settings. - * ''tcpprint'' - Will allow you to use local LPT/USB printers like "dumb" network printers (listening to port 9100 and above). Requires MAC->IP mapping in DHCP server (and optionally, DNS->IP mapping), or static IPs - else your print jobs will end up on random devices. This setup is preferred over the X2GoClient's built-in printing for locally attached printers if X2GoServer and ThinClients are on the same network. It is not recommended when your X2Go connection goes across the internet or when the ThinClient is actually a laptop roaming between different networks. + * ''tcpprint'' - Will allow you to use local LPT/USB printers like "dumb" network printers (listening to port 9100 and above). Requires MAC->IP mapping in DHCP server (and optionally, DNS->IP mapping), or static IPs - else your print jobs will end up on random devices. This setup is preferred over the X2GoClient's built-in printing for locally attached printers if X2GoServer and ThinClients are on the same network. It is not recommended when your X2Go connection goes across the internet or when the ThinClient is actually a laptop roaming between different networks. **Attention:** When used without ''tcpprintonlyfrom'' (see below), this means anyone that can reach your thin client via e.g. ping can also send print jobs to it! * ''tcpprintonlyfrom=x.x.x.x'' - Will allow you to specify which IP address may connect to Port 9100 and above for printing to a locally attached LPT/USB printer. This should be the IP of your CUPS server or whatever print server system you use. Understands the same syntax as xinetd's ''only_from''. These are //not yet implemented//, but planned for a future release, and only intended to be used with TCE images stored on local media: * ''updateurl=rsync|https|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used. Regardless of NTFS or not, the updater requires three directories: ''/boot/live1, /boot/live2, /boot/live-download'' **Attention:** Whoever manages to spoof the server name can deploy rogue images to your ThinClients. Even though it is slower, using an HTTPS web server is the safer way of doing this. Be sure that your web server delivers a last-modified header for all files. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 12:32 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483359910 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: User : stefanbaur @@ -246,9 +246,9 @@ * ''tcpprintonlyfrom=x.x.x.x'' - Will allow you to specify which IP address may connect to Port 9100 and above for printing to a locally attached LPT/USB printer. This should be the IP of your CUPS server or whatever print server system you use. Understands the same syntax as xinetd's ''only_from''. These are //not yet implemented//, but planned for a future release, and only intended to be used with TCE images stored on local media: * ''updateurl=rsync|https|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used. Regardless of NTFS or not, the updater requires three directories: ''/boot/live1, /boot/live2, /boot/live-download'' **Attention:** Whoever manages to spoof the server name can deploy rogue images to your ThinClients. Even though it is slower, using an HTTPS web server is the safer way of doing this. Be sure that your web server delivers a last-modified header for all files. - * ''updatesleep=nnnnn'' - Will allow you to specify the upper limit (in seconds) of the update timer's randomizer. Allowed range: 121-32767. Will default to 900 if unset or set to an out-of-range value. + * ''updatesleep=nnnnn'' - Will allow you to specify the upper limit (in seconds) of the update timer's randomizer. Allowed range for upper limit: 240-32767. Will default to 900 if unset or set to an out-of-range value. Lower limit is fixed at 120 seconds. * ''bwlimit=nnn'' - Will allow you to specify a bandwidth limit (valid values: 1-100) in percent for the backgrounded update task. * ''ntfs-uuid='' - Will be required for updating images stored on NTFS filesystems. Full UUID as shown under /dev/disk/by-uuid/ is preferred, but can work with the volume serial number shown in the output of "vol c:" as well. === Required unless using the X2Go Session Broker: Adding the x2go-tce.sessions session configuration file to your HTTP or FTP Server === -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

← Newer
1
...
30
31
32
33
34
35
36
37
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

x2go-commits January 2017