[X2Go-Commits] [[X2Go Wiki]] page changed: doc:howto:tce

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2019/02/02 18:58
Browser     : Mozilla/5.0 (X11; Linux x86_64; rv:52.9) Gecko/20100101 Goanna/3.4 Firefox/52.9 PaleMoon/27.9.4
IP-Address  : 109.193.81.67
Hostname    : HSI-KBW-109-193-081-067.hsi7.kabel-badenwuerttemberg.de
Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1548883990
New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Prerequisites] added note regarding problematic tftp server
User        : stefanbaur

@@ -258,9 +258,9 @@
    * 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 and requires building your own iPXE image. see http://ipxe.org/crypto for details. Alternatively, use ipxe.lkrn (from [[http://boot.ipxe.org/ipxe.lkrn]]) and pxelinux.0 in combination with scripted ipxe commands in the pxelinux.cfg.
    * You will also need an HTTP/HTTPS/FTP server with a dedicated IP (no name-based virtual hosts) for the squashfs image. - **Note:** set LBX2GO_NOSQUASHFS=true and use iPXE (e.g. with ipxe.lkrn + pxelinux.0) if you cannot use an IP for your host. Another option (untested) is explained [[https://blog.jacekk.info/2016/01/debian-live-webboot-dns/|here]]
-     * 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.
+     * This image cannot be deployed via TFTP as it is too large - some TFTP servers
(atftpd in particular) 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.
      * It **might** be possible to use HTTPS with the ''fetch='' command.  This is untested.
    * Once your setup fulfills all the requirements listed above, go ahead and build the image using the scripts listed in [[doc:howto:tce#configuring_the_build|Configuring the Build]] - make sure to choose ''export LBX2GO_IMAGETYPE='netboot''' (this should be the default)


-- 
This mail was generated by DokuWiki at
https://wiki.x2go.org/