Illustration
38: The Setup Manager requests a password after it is launched with
the F2 key.
WML Linux Thin Client User Guide
The Setup Manager allows the system administrator to manage the WML Linux Thin Client's device settings. It allows you to control the network settings, the language/keyboard settings, display resolution, mouse settings, administrator password and sound.
The Setup Manager is also used to apply new firmware updates to the WML Linux Thin Client.
The Setup Manager can always be run by pressing the F2 key. It is password protected using the same password used to access the “Configuration” tab of the Connection Manager and has the default value of “password” on a factory delivered unit.
The Setup Manager is a tabbed window, with a tab for each section of the program.
Illustration
38: The Setup Manager requests a password after it is launched with
the F2 key.
The System tab shows details about the thin client hardware and firmware.
Illustration
39: The System Tab of the Setup Manager
The “System Information” box shows
information about the processor type, the amount of memory available,
the Linux kernel version and the Firmware version. The network
settings are also shown in this box.
The “Desktop” box has two fields to control the thin client's desktop. The first check box controls whether a user may launch a command line terminal. If it is checked, a button will appear on the “Connections” tab of the Connection Manager called “Terminal”.
Note that if a user has access to a terminal window, then it is possible for the user to modify the list of connections in the Connection Manager. Access to the terminal is intended for administrator and power users.
The second check box enables a task bar at the bottom of the screen which allows the user to navigate between windows.
The “System Settings” window has three buttons to help manage the WML Linux Thin Client. “Save Settings” will store the current system and connection configuration to a backup file, which is either stored on a usb storage device (if present) or in the temporary directory /tmp if not. “Save Settings” will save network, display, mouse, locale and password settings, as well as any connections which have been configured in the Connection Manager. The settings are saved in a file settings.tar.
Illustration
40: Save Settings clicked, and settings saved on a usb storage
device
To replicate a WML Linux Thin Client, take the
usb storage device containing settings.tar and plug it into a new
client. Press the “Load Settings” button. A file chooser
dialog will appear, showing the contents of the /flash directory (the
contents of the usb storage device).
Illustration
41: Loading the settings file
Highlight the settings.tar file and press
“Open”. A confirmation box will open, asking you if you
are sure and notifying you that the WML Linux Thin Client will
re-boot if you confirm.
If you press the “Factory Defaults” button, a confirmation box will appear asking you to confirm that you wish to clear all configured connections and return the device to the factory default settings. This will reset all settings, including the administration password, and reboot the device. When the device powers up, the Setup Wizard will run.
Illustration
42: Confirming Factory Default Settings
The WML Linux Thin Client may be remotely configured using the saved file, settings.tar. It achieves this using DHCP (Dynamic Host Configuration Protocol). If the WML Linux Thin Client boots on a network with DHCP and the “next_server” DHCP parameter is specified, it will try to download a file from a web server whose address can be specified using the “next_server” DHCP parameter.
If “next_server” is specified as , for example, 192.168.0.1, then it will try to download http://192.168.0.1/foundrylinux/settings.tar If it is successful, it will apply these settings to the WML Linux Thin Client. If it can't download the file, startup will proceed as normal.
Note that the downloaded settings.tar should itself specify DHCP for network settings.
Here is an example configuration directive for the Internet Systems Consortium DHCP Server, specifying the next_server parameter. This would be placed in the /etc/dhcp/dhcpd.conf file.
shared-network WORKSTATIONS {
subnet 192.168.10.0 netmask 255.255.255.0 {
range 192.168.10.100 192.168.10.150;
}
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.10.255;
option routers 192.168.10.1;
option domain-name-servers 123.23.232.23;
option domain-name "company.lan";
next-server 192.168.10.1;
}
In this example, the WML Linux Thin Client will try to download settings.tar from http://192.168.10.1/foundrylinux/settings.tar
The Language/Keyboard is changed by selecting the desired locale from the drop-down menu. If you choose a new locale, a confirmation box will appear, and if you confirm, then the windowing session will re-start using the new language and keyboard settings.
Make sure you close down any connections you have running before changing the locale, as any open connections will be killed when the windowing system is re-started.
Illustration
43: The "Locale" tab of the Setup Manager
The WML Linux Thin Client's Network settings are configured using this tab. The WML Linux Thin Client can use DHCP to obtain its IP address and DNS settings, or these can be manually configured.
Illustration
44: Network settings set to DHCP
If the network settings are entered manually,
details for IP address, netmask, gateway and name resolution need to
be entered in the “Network interface” and “Domain
name server” tabs. In the “Domain name server”
settings, two DNS servers may be specified, along with a domain
search path, which should be a space separated list of the domains on
your network to search.
The WML Linux Thin Client can be remotely accessed by an administrator either via secure shell, or using VNC. Both of these features need to be switched on in the Network tab of the Setup Manager. Illustration 44 shows both secure shell and VNC access switched on. The SSH and VNC daemons are started as soon as their respective boxes are checked, the “Apply” button in the Network box needn't be pressed.
Secure shell provides a text based connection to the WML Linux Thin Client, which the admin can use to check memory usage and runaway processes.
Connect to the WML Linux Thin Client using any SSH client (for example, OpenSSH for unix, or Putty for Windows). Use the username “root” and the same password that you use to configure the WML Linux Thin Client.
VNC provides a full graphical view of the WML Linux Thin Client's desktop. A number of options are provided:
“control as well as view” When checked, the remote admin will be able to control the desktop of the WML Linux Thin Client user, as well as viewing it.
“prompt the user” When this option is checked, the local WML Linux Thin Client user will see a pop-up window whenever a remote admin tries to view or control the desktop. The local user may then either refuse or accept the connection.
“password protection” Use a password to protect access to the WML Linux Thin Client desktop. This password is stored separately from the usual admin password.
The “Proxy/Font Server” tab allows the administrator to specify an X Font Server from which the WML Linux Thin Client should obtain font information. The WML Linux Thin Client runs its own font server, but this provides a very limited range of fonts. The Bitstream Vera truetype font is provided, along with a simple fixed X font. To allow tunnelled X applications to use a full range of fonts, a networked X font server can be used. Fill in the field with a suitable font server entry, and press “Set Font Server”. An example is xfs.company.lan:7100
The default for the font server field is the local font server, unix/:7100. This font server remains in use, even when an additional font server is specified.
Currently, the proxy configuration setting is made within the web browser, rather than in the Setup Manager.
Illustration
45: Highlighting the x font server field to specify an additional
font server.
Currently, wireless networking must be configured by editing text configuration files. Wireless networking can be achieved on the WML Linux Thin Client GX using a plugin usb wireless device based on the prism2 chipset. The WML Linux Thin Client LX can be supplied with an optional Intel Pro2200b/g wireless card. In each case, the wireless device is configured in the file /etc/persistent/prestartup.sh.
To edit prestartup.sh, you must get a root shell on the WML Linux Thin Client. You can either press Ctrl-Alt-F1 to get a login prompt, then login as “root” with the usual admin password used to gain access to the Setup Manager. Alternatively, if you have sshd running for remote admin, you can ssh to your WML Linux Thin Client (to ssh to your own WML Linux Thin Client, type: ssh root@localhost).
Now edit the prestartup.sh file:
edit /etc/persistent/prestartup.sh
And modify the commented out commands. The first commands load the kernel modules to drive the wireless device. The following commands use either wlanctl-ng (prism2) or iwconfig (intel pro2200) commands to configure the SSID and WEP settings for the device.
The display resolution tab presents a menu of supported resolutions and refresh rates. These are determined from your monitor using a DDC query.
Illustration
46: The "Display" tab of the Setup Manager
If you wish to change the display resolution,
choose the new setting and click “Apply”. If the box is
checked (“Display settings above should be retained between
reboots”), then the next time the WML Linux Thin Client boots,
it will not automatically detect the optimum monitor
resolution but will run your chosen resolution.
If you want to return the WML Linux Thin Client to checking automatically for resolution, simply uncheck the box. This can be useful when preparing a settings.tar file to implement remote management for a fleet of Sumos.
The mouse settings tab allows the mouse speed and handedness to be configured.
Illustration
47: Mouse set to the default speed and right-handed operation.
The printing tab provides some information about printing via the WML Linux Thin Client. On devices with a parallel port, a menu is provided to choose whether the printer is attached to the parallel or usb port. On the standard WML Linux Thin Client, only usb ports are available.
Illustration
48: Printer support information
Firmware upgrade image files are available from William Matthew Limited.
The firmware upgrade process requires a usb storage device. The firmware upgrade file is 56 MB in size and must be placed directly (i.e. not within any sub-folders) on a usb storage device of at least 128 MB. The additional space is required to save temporary files used during the upgrade process. Firmware upgrade files have a filename of the form st166sumo64-20060712_1000.img. The name should not be changed after downloading; it should be stored on the USB drive with the original name.
Illustration
49: The Firmware Upgrade tab
After inserting the USB drive containing the
upgrade file into one of the USB ports on the WML Linux Thin Client,
run the Setup Manager and choose the “Firmware” tab.
Click the “Refresh” button and the USB drive will be
scanned for a firmware image. If an image is found, the “Upgrade”
button will be enabled. Click “Upgrade” and a final
window will appear asking for confirmation. Once the upgrade process
has started it cannot be stopped and the WML Linux Thin Client will
reboot at the end of the process.
Do not interrupt the upgrade process once it is underway, or power off the device. The process will take 2 minutes.
Illustration
50: Confirming the Firmware Upgrade
Upgrading the firmware will not change the
device settings or affect the configured connections in the
Connection Manager.
The System administrator password can be changed using the Password tab of the Setup Manager. Enter the new password in the field and press “Change Password”. You will be asked to confirm the password by re-entering it. If the two passwords match, and are greater in length than 5 character, the password will be updated.
Illustration
51: Updating the administrator password
The WML Linux Thin Client supports networked sound for ICA and Unix/Linux connection types. The sound tab allows you to start or stop the esound daemon. The esound daemon allows Unix sessions to support networked audio.
If you use sound for Citrix sesssions, the esound daemon must be switched off.
When you switch the esound daemon on, with speakers or headphones connected, you will hear a series of tones (best not to wear the headphones when doing this – the sounds may be quite loud).
To send audio from your Unix/Linux application to the WML Linux Thin Client, it is necessary to configure the application to send audio output to “esound” or “esd” rather than the usual ALSA or OSS. No other action need be taken. If you have difficulty configuring sound, please check the firewall settings on your application server; the esound daemon listens for TCP packets on port 16001.
Illustration
52: Switching on the esound daemon
This tab presents Copyright information for the Connection Manager, the Setup Manager and free software included with the WML Linux Thin Client.
Illustration
53: Copyright information
page
Copyright © 2006 William Matthew Limited. All rights reserved