Set up FatClient Configuration

Attention

Fat Client configurations only apply to LTSP versions 5.2 and greater.

LTSP Fat Client - Definition / Purpose

Previous documentation indicated that LTSP lab consists of a server that supports thin (diskless clients). Therefore, then a workstation logs in and runs an application, that application is running from the server and displayed on the workstation. Although this has many advantages, due to network transports and server load, certain applications can run slow.

A fat client (in LTSP terms) is a computer lab setup whereby the application processing is performed by the client itself, thus better distributing the load.

The interesting point is that the client still does not require a hard disk.

TASK #1: How configure a FAT Client

STEPS:

1. Perform the previous steps to perform an install from scratch.
2. Open a terminal (shell) and login as root (eg. sudo su)
3. Enter the following command to remove the current chroot configuration:
   
   rm -rf /opt/ltsp/amd64
   
   
4. Issue the following command to rebuild the system using FAT Clients:
   
   ltsp-build-client --fat-client --fat-client-desktop edubuntu-desktop --arch amd64 --skipimage
   
   
5. Once the image is rebuilt, issue the following commands:
   
   ltsp-update-sshkeys
   ltsp-update-image
   
   
6. When completed, test out the system to ensure users can boot-up their workstations and login.

TASK #2: Configure System to Allow FAT Clients to Connect to Internet

Note: When running the computer lab configured for FAT Clients, the workstations will NOT be able to connect to the Internet. Perform the following steps to allow workstations to connect to the Internet:

STEPS:

1. Open and terminal (shell) and login as root.
2. Edit the dhcpd.conf file by issuing the command: vi /etc/ltsp/dhcpd.conf and ensure that the following command line exists, otherwise enter it:
   option routers 192.168.1.254;
3. Add the line: option domain-name-servers 192.168.0.1;
4. Refer below to our example of the dhcpd.conf file:

#
# Default LTSP dhcpd.conf config file.
#

authoritative;

subnet 192.168.1.0 netmask 255.255.255.0 {
    range 192.168.1.20 192.168.1.250;
#    option domain-name "example.com";
    option domain-name-servers 192.168.0.1;
    option broadcast-address 192.168.1.255;
#    option routers 192.168.1.1;
    option routers 192.168.1.254;
#    next-server 192.168.0.1;
#    get-lease-hostnames true;
    option subnet-mask 255.255.255.0;
#    option root-path "/opt/ltsp/i386";
    option root-path "/opt/ltsp/amd64";
    if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
#        filename "/ltsp/i386/pxelinux.0";
        filename "/ltsp/amd64/pxelinux.0";
    } else {
#        filename "/ltsp/i386/nbi.img";
        filename "/ltsp/amd64/nbi.img";
    }
}

5. Save and exit the editor.
6. Restart the dhcpd server by issuing the command: sudo /etc/init.d/dhcp3-server restart
7. Edit the sysctl.conf file by issuing the command: vi /etc/sysctl.conf
8. Add the following line or uncomment (if it already exists):
   net.ipv4.ip_forward=1
9. Save and exit the editor.
10. Run the command: sudo sysctl -w net.ipv4.ip_forward=1
11. Issue the following command:
    
    iptables --table nat --append POSTROUTING --jump MASQUERADE --source 192.168.1.0/24
12. Run the following command to make the above setting permanent:
    
    sudo sh -c 'iptables-save > /etc/ltsp/nat'
13. Edit the interfaces file by issuing the command:
    
    vi /etc/network/interfaces
14. Make changes to the file to add the line up iptables-restore < /etc/ltsp/nat to the existing file. See below for our example:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

auto eth1
iface eth1 inet static
  address 192.168.1.254
  netmask 255.255.255.0
  network 192.168.1.0
  up iptables-restore < /etc/ltsp/nat
  broadcast 192.168.1.255

15. Restart the server.
16. Your client should now be able to connect to the Internet. Test out your connection on your thin (fat) client.