Monday, February 15, 2016

LTSP(Linux Terminal Server project)

Introduction.
The Linux Terminal Server Project adds thin-client support to Linux servers.

Prerequisited for Installation
            Before installing LTSP we need DHCP  that must be already installed & configured on your
system.

Installation

DHCP (Dynamic Host Configuration Protocol)

apt-get install dhcp3-server dhcp3-common

After installation just you have to edit a file dhcpd.conf
vi /etc/dhcp3/dhcpd.conf

ddns-update-style none;
option domain-name "domain.com";

option domain-name-servers IP[i.e =192.168.3.1];
next-server IP[i.e=192.168.3.2];

default-lease-time 600;
max-lease-time 7200;

#log-facility local7;

subnet [i.e=192.168.3.0] netmask 255.255.255.0 {
# range [starting]  [ending]
   range 192.168.3.10  192.168.3.100;
   option subnet-mask 255.255.255.0;
   option routers 192.168.3.1;

#  option broadcast-address 10.5.5.31;
}
NFS
apt-get install nfs-kernel-server

After installation add permissions on any directory to any user. For this open
vi  /etc/exports
[Folder name]  [Client-IP/Complete Network] / [Netmask](permissions)
/home  192.168.1.0/255.255.255.0(rw)

LTSP
apt-get install ltsp-server
Note : If you find i386 [/opt/ltsp/i386] in your system than remove that.
rm -fr /opt/ltsp/i386

apt-get install atftpd


There are two ways to take all the packges to complete the LTSP installation.
ONE if you have all the updates download as a tar file or second if you have to connect
with the internet and download the updates. It's may be take two or three hours depending on your
internet speed.

If you want to download form internet or for apt server than

ltsp-build-client –mirror http://apt-proxy.emergen.biz:1010/kubuntu
ltsp-build-client  uses  the ubuntu archive mirrors in order to build an ltsp client for use with the ltsp server.

ltsp-update-sshkeys
ltsp-update-sshkeys  updates  the current ltsp servers sshkeys in the client chroot.  This is required for example if the ltsp server changes ip address.

After performing all these step you have to edit the dhcpd.conf file
Add this line

option-root-path “/opt/ltsp/i386”;
And in the body where you are defining range add this line
filename “/ltsp/pxelinux.0”

After editting dhcpd.conf you have to add two line in exports file.

vi /etc/exports
/opt/ltsp   *(ro,no-root-squash,sync)
/var/opt/ltsp/swapfiles *(rw,no-root-squash,sync)

Some times there is some error related with xdmcp bcoz of  xdmcp is not enabled bcoz of that you are unable to boot GUI on thin-clients.
for enabling xdmcp
vi /etc/kde3/kdm.kdmre

 [xdmcp]
 Enable=true  ( It was false before)

After this restart
/etc/init.d/nfs-kernel-server  restart
/etc/init.d/portmap  restart
/etc/init.d/inetd  restart

After this execute commad

showmount -e
showmount  queries  the  mount  daemon  on a remote host for information about the state of the NFS server on that machine.  With no options showmount lists the set of clients who are mounting from that  host.


After this Open
vi /etc/kd3/kdm/xaccess
Find line like
# *       #Any host can get a login windows
remove 1st hash (number sign)  from this line.

After removing the hash sign restart kdm and execute
netstat -anp| grep 177
you should see line like
udp      0          00        6716/kdm       

After this restart DHCP & bootup client.
this client'll boot up :)

SECOND If we have downloaded updates as i iso on CD than run
  ltspadmin
one menu is appear

===================================================================

Thin Client deployment on SuSe Enterprise 9

This document details the deployment and maintenance using LTSP on Suse Linux Enterprise Server 9.

Introduction
LTSP is an add-on package for Linux that allows you to connect lots of low-powered thin client terminals to a Linux server. Applications typically run on the server, and accept input and display their output on the thin client display.

Prerequisites for Installation of LPST
Before Installing LTSP you need LWP Pearl already installed on your system.
Also you need a TFTP server for LTSP.

Installation
There are two ways to  install LTSP 4.1 .

1.    LTSP Installer
You can download the LTSP installer, and use that to download the rest of the packages.
2.    ISO image
Download the ISO image and use the LTSP Installer to install from that.

We use second method in this document . Download ISO image but you need to run it on Apache or any other web server because it needs an web URL and mount the ISO directory to apache default web folder .

server #  mount -o loop /home/noman/LTSP4.1/ltsp-4.1-1.iso   /srv/www/htdocs/  

Now you have LTSP installer in htdocs folder. Install it first .

server #  rpm -ivh ltsp-utils-0.10-0.noarch.rpm

Now Run ltspadmin for LTSP package installation.

server # ltspadmin
Selection main menu is appered.

Select Install and update LTSP package.

LTSP installer Configuration wizard appears.
give your local apache web address for file to retrieve from there else it go on internet to get packages from there.

Specify directory for LTSP client Configuration to place all client files there.
/opt/ltsp

Select All packages to install.

Now select Configure LTSP.

1.    Runlevel
2.    Interface selection
3.    DHCP Configuration
4.    TFTP Configuration
5.    Portmapper Configuration
6.    NFS Configuration
7.    XDMCP Configuration
8.    Create /etc/hosts entries
9.    Create /etc/hosts.allow entries
10.              Create /etc/exports entries
11.              Create lts.conf files


1.    Run Level
Enter run level 5 for GUI Login Mode.
2.    Interface selection
Select the Network Interface for clients to connect if you have only one its select .
3.    DHCP Configuration
             # Sample configuration file for ISC dhcpd
            #
            # Make changes to this file and copy it to /etc/dhcpd.conf.sample
            #
ddns-update-style            none;

default-lease-time           21600;
max-lease-time               21600;
option ntp-servers 192.168.2.254;
option domain-name "emergen.biz”;
option domain-name-servers 192.168.2.254;

option subnet-mask           255.255.255.0;
option broadcast-address     192.168.2.255;
option routers               192.168.2.249;
option domain-name-servers   192.168.2.249;
option domain-name           "ltsp";          # <--Fix this domain name

option root-path             "192.168.2.249:/opt/ltsp/i386";

option option-128 code 128 = string;
option option-129 code 129 = text;

subnet 192.168.2.0 netmask 255.255.255.0 {
    use-host-decl-names      on;
    range 192.168.2.60 192.168.2.240;
    filename             "lts/2.4.26-ltsp-3/pxelinux.0";
    option log-servers       192.168.2.249;
}         
#
            # Add these two lines to the host entry that needs kernel parameters
            #
            #        option option-128     e4:45:74:68:00:00;       # NOT a mac address
            #        option option-129     "NIC=ne IO=0x300";
            #

4.    TFTP Configuration
      Enable TFTP.

5. Portmapper Configuration
Enable Poet Mapping (By default its on)

6.    NFS Configuration
     Enable NFS (By default its on)

7.    XDMCP Configuration
     Enable XDMCP (By default its XDM and its on)           

8. Create /etc/hosts entries
     Create hosts with LTSP installer. Then no need to modify it.

9.    Create /etc/hosts.allow entries
Create hosts with LTSP installer. Then no need to modify it.

10.              Create /etc/exports entries
Create export list with LTSP installer. Then no need to modify it.

12.              Create lts.conf files
     Create lts.conf with LTSP installer           
USB mount on LTSP

1. vi /opt/ltsp/i386/etc/lts.conf            //insert HOTPLUG entry.
        SERVER             = 10.0.2.51
        XSERVER            = auto
        X_MOUSE_PROTOCOL   = "PS/2"
        X_MOUSE_DEVICE     = "/dev/psaux"
        X_MOUSE_RESOLUTION = 400
        X_MOUSE_BUTTONS    = 3
        HOTPLUG            = Y
        USE_XFS            = N
        SCREEN_01          = startx


2.    Next, download the following two scripts and put them in /usr/local/bin










No comments:

AWS EC2 - SSH locked with UFW

Need to update the instance's user data: 1. Stop the instance 2. Right click (windows) or ctrl + click (Mac) on the instance to open a c...