Wclinux

Lotus Mobility Client for Linux
Version 6.1.1
Users Guide
Lotus Mobility Client for Linux
Version 6.1.1
Users Guide
Note: Before using this information and the product it supports, read the information in Notices on page 37.
This edition applies to version 6, release 1, modification 1 of IBM Lotus Mobile Connect (product number 5724-R20) and to all subsequent releases and modifications until otherwise indicated in new editions. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation and others 1994, 2007. All rights reserved. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
About the Mobility Client guide for Linux v
Whats new in this release . . . . . . . . . . v Configure trace properties . . . . . . Roaming between networks . . . . . . Specifying the network adapter to use . Viewing connection status . . . . . . Manually suspending and resuming communications . . . . . . . . . . Viewing connection properties . . . . . Deleting a connection . . . . . . . . Disconnecting from the Connection Manager Changing font size and style . . . . . . . . . . . . . . . . . . . . . . . . 9 . 10 . 11 . 11 . . . . . 12 12 13 13 13
Chapter 1. Getting started . . . . . . . 1

Software and hardware requirements Installing the Mobility Client . . . Applying maintenance . . . . . Starting the Mobility Client . . . Removing the Mobility Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 2 2 3
Chapter 2. Using the Mobility Client . . . 5

Creating a Mobility Client connection . . . . . Connecting to the Connection Manager . . . . Changing your password . . . . . . . . . Checking that applications are running before connecting . . . . . . . . . . . . . . Starting a connection when the operating system starts . . . . . . . . . . . . . . . . Automatically starting applications after connecting Exporting and importing configuration files . . . Using the command line to import and export configuration files . . . . . . . . . . Using trace . . . . . . . . . . . . . . Using the trace viewer . . . . . . . . . . 5 . 5 . 5 . 5 . 6 . 6 . 7 . 8 . 8 . 8
Chapter 3. Configuring clients with configuration files . . . . . . . . . . 15 Chapter 4. Getting online help . . . . . 35
Accessibility . . . . . . . . Navigating with the keyboard . . . . . . . . . . . . 35 . 35
Notices . . . . . . . . . . . . . . 37
Trademarks . . . . . . . . . . . . . . 39
Index . . . . . . . . . . . . . . . 41
iii
iv
IBM Lotus Mobility Client for Linux: Users Guide
About the Mobility Client guide for Linux

This document describes how to install, configure, and use the Mobility Client, a component of the IBM Lotus Mobile Connect, from now on referred to as the Connection Manager. This document describes the Mobility Client for use on Linux x86 systems.
Whats new in this release

New in Version 6.1.1 of the Mobility Client: No changes for Version 6.1.1.
vi
Chapter 1. Getting started

To get started using the Mobility Client, refer to these sections to complete the following tasks: v Software and hardware requirements v Installing the Mobility Client v Starting the Mobility Client on page 2
Software and hardware requirements

The Mobility Client requires: v The Connection Manager successfully configured to use mobile access services v A mobile computer with sufficient resources (processor speed, hard drive, and memory) to run the operating system, manage modem communications, and run your other applications. v A modem or interface adapter for your network provider. The list of detailed system requirements is available online. See: v Detailed system requirements v Hardware requirements v Supported operating system requirements v List of supported software The following Linux distributions are supported: v Red Hat Enterprise Linux 4.0 workstation v SuSE Linux Enterprise Desktop 9 v SuSE Linux Enterprise Desktop 10
Installing the Mobility Client

This procedure assumes you are downloading the code from the product support web site. The code can also be obtained on CD 2. When you install components, some operating systems provide a method for you to log the installation activities and results with appropriate time stamps. As an additional parameter to the install_wc script, attach 2>&1| tee myfile.log, where myfile.log is a path and file that you choose to log the installation. To install the Mobility Client on a Linux x86 system: 1. If you have previously installed the Mobility Client, make sure the Connections window is closed. 2. Download the Mobility Client for Linux from the product Support web page, All Software Downloads. The file downloaded is named linux-x86.tar.gz. 3. Uncompress and tar the downloaded file. From a command line, enter tar -xzvf linux-x86.tar.gz. This command places the code and installation scripts in a directory labelled linux. 4. Make sure that you are logged in as root and change the current directory to the linux directory created in the previous step.
5. Enter ./install_wc to start the installation.
Applying maintenance
Links to code fixes are available from the Connection Manager Product Support web site at www.ibm.com/software/lotus/mobileconnect/support/ for entitled customers who have a download key. Customers can register at the web site, provide the download key given to them, then download the code fixes. Download keys are available from the Level 2 Connection Manager IBM Software Support Center in the U.S.A. at 800-IBM-SERV (800-426-7378). Outside the United States, use the web site at http://www.ibm.com/planetwide to find the IBM Support Guide Software Support Global Contact List. The x86 version is approximately 10 MB and the file name is wc<version>linuxx86.tar.gz. After downloading the file, untar it with the command tar -xzvf wc<version>linux- filename.tar.gz, then use the ./install_wc script to install it.
Starting the Mobility Client

On some Linux distributions, such as RedHat and SuSE using Gnome or KDE environments, an icon is added to the Internet folder to open the Mobility Client. From a command line, enter wcguicfg To start the Mobility Client from a command line, use the wclient command. Command line flags include: -a [address][:port] Instead of using a configuration file, use the gateway address and (optional) the port specified. This parameter requires a prompt for user ID and password. This parameter cannot be used with the -l or -f options. -b Use this parameter to place the login attempt into the background and have the wclient return immediately. This option is only valid with the -l option.
-c [device configuration file] Generate a default device connection configuration to standard out that uses the specified device library for the transport. For example, for a connection named violet, enter
wclient -c violet_device.conf>/home/userID/.wclient/violet.conf.
-d [device library] Generate the default device interface configuration to standard out that uses the device library specified. For example, enter
wclient -d libiplan.so>/home/userID/.wclient/violet_device.conf
-D [device library] Use this parameter with the -d option for PPPLAN devices to specify which device to connect over. The default is libiplan.so. This option is only valid with the -d option. -f [configuration file] Load configuration settings from [configuration file] instead of from /opt/ibm/MobilityClient/wclient.conf. The configuration file must be fully qualified. If you do not specify the -f flag when specifying other flags on the command, the default configuration file is used. -h Displays the usage statement.
-i [device index] Generate a default device configuration to standard out based on the device index specified. If the value is 0 then its IP LAN. If the value is 1, its IP LAN over a point-to-point protocol daemon (PPPD). -I [device index] Use this parameter with the -i option for PPPLAN devices to specify which device to connect over. The default value is 0, the default IP LAN. This option is only valid with the -i option. -l Log in silently to Connection Manager and exit. To use this flag, you must have previously connected using the user account and selected the Save password check box on the Connect window. This parameter can be used along with the -f parameter. For IP LAN connections, if no IP adapters are available, wclient returns 1 and waits in the background for an IP adapter to become available. Use the -t parameter to specify how long to wait for an IP adapter to become available. Use the -b parameter to put the login attempt into the background and have the wclient command return immediately. This command line flag does not permit secondary authentication. -o -t If there is an active interface, silently log it out and close the active interface. Time in seconds to wait for IP adapters to become available before exiting. Use this with the -l parameter. Values <= 0 indicate an infinite timeout. The default value is 90. Show version information.
-v
Removing the Mobility Client

1. Make sure the Mobility Client Connections window is closed. 2. Make sure that you are logged in as root. 3. From a command line, enter rpm -qa | grep IBMwc | xargs rpm -e.
Chapter 1. Getting started
Chapter 2. Using the Mobility Client

This section describes the use of the Mobility Client on Linux.
Creating a Mobility Client connection

To define a new connection, click Connections -> Create . . . in the Connections window to start the Create Connection wizard. Follow the wizard prompts to define information for your new connection, including: v Connection name: the unique name to assign to the specific client configuration. v Network type: depending on the types of network adapters you have installed, select the fastest available (default) IP network, or choose from the prioritized list of connection types. v Connection Manager address: the IP address or host name of the Connection Manager. An icon for each connection you create is added to the Connections window.
Connecting to the Connection Manager

To establish a connection to the Connection Manager: 1. In the Connections window, double-click the connection that you want to start. 2. Enter the requested information in the Connect window. 3. Click Connect to start a connection.
Changing your password

To change the password that you use to connect to the Connection Manager: 1. Make sure the connection is active. 2. Right click the active connection. 3. Select Change Password . . . on the menu. 4. Enter all three values: Old password, New password, and Confirm new password. 5. Click OK.
Checking that applications are running before connecting

The Mobility Client can check that certain programs are running, like antivirus or personal firewall software, before allowing the connection to start. You can modify the configuration file to add parameters that let the Mobility Client check for up to 16 applications before starting a connection. If the applications listed are not running, the Mobility Client prompts you to manually start them. To configure these settings, manually edit the configuration file. Note: You will not be able to log on until all necessary applications are running.
Application configuration parameters are stored in the Connection setting file. To create new configuration or change existing application check parameters, enter them in the <connection_name>.conf file: PrereqAppName1 ... PrereqAppName16 One PrereqAppName for each application that must be executing before a connection attempt can proceed. The application name is a descriptive name that is displayed to the user in informational and error messages. PrereqAppProcess1 ... PrereqAppProcess16 Where PrereqAppProcess1 is the name of the first process that must be running before the Mobility Client attempts to connect, and PrereqAppProcessn is the last process that must be running before the Mobility Client attempts to connect. When a process is running, t values are found by typing ps -e from a shell prompt. PrerequisiteDisabled If PrerequisiteDisabled is set to 1, then the applications are ignored and no checking is done.
Starting a connection when the operating system starts

You can configure a specific connection to start automatically when the operating system starts. Log in as root and use the properties notebook to configure the service. Only one connection can be configured to start when operating system starts. If the connection is lost, the Mobility Client attempts to restart the connection until it is reestablished. Any applications listed on the Autostart tab of the Connection properties, Applications to start after connecting , will not start up until the Connection window (using the command: wcguicfg) is opened. To start a connection automatically when the operating system starts: 1. The account you want to have started automatically must have been previously connected to the Connection Manager and saved the account password. If you have not done this, select the Save password check box on the Connect window and click Connect. 2. Select the connection, then click Connection > Properties. The properties notebook is displayed. 3. On the Attributes tab, check the Start connection when the operating system starts check box, then click OK.
Automatically starting applications after connecting

You can configure the Mobility Client to launch applications automatically after a connection has been established. The number of applications which you can autostart is restricted to 16. In addition to specifying the application name, you can also configure any parameters with which you want the application started. To view or modify which applications are automatically started: v Right-click the connection in the Connection window, then click Properties. v Click the Autostart tab. v To add an application to the list, click Add. To modify an application in the list, click Change. v In the Application field, specify the full path and name of the application or click Browse to search your hard drives for the application.
v In the Parameters field, type the parameters that you want used when the application starts. For example, if you wanted to specify that a browser starts and automatically connects to a URL other than your home page, specify that URL in this field. v Click OK. After a successful logon, the applications are started in the order in which they are listed on the Autostart tab.
Exporting and importing configuration files

You can export and import configuration files as directed by an administrator to set or change Mobility Client options, then distribute the new configuration to many clients. To import a configuration file: 1. Click the connection in the Connections window. Click Tools --> Import Configuration.... 2. Enter the full path and name of the configuration file to be imported, or click Browse to find the file. By default, exported configurations have an extension of *.pdb. 3. Select the file you want to import, then click Ok. The Import Configuration window acts as a confirmation dialog. You are prompted if the imported connections will override an existing connection. Your existing configuration is saved in a *.lmc file, which can be restored. To export a configuration file: 1. Click the connection in the Connections window. Click Tools --> Export Configuration.... 2. Enter the full path and name of the configuration file to be exported, or click Browse to find the file. By default, exported configurations have an extension of *.pdb. 3. Select the file you want to export, then click Ok. In the Export configuration window, determine if you want to export the file as a platform-independent configuration or whether you want to export the complete configuration. Select this check box when you want to export a configuration that can be used by any installed Mobility Clients. Not all configuration can be exported as platform-independent. For example, configurations specifying a specific modem cannot be exported as platform-independent. You will be prompted if you attempt to export a configuration that cannot be exported as platform-independent. Clear this check box when the desired configuration involves platform or machine-specific information, such as specific modem or adapter name. The exported configuration will need to be imported on a machine with an identical configuration; one on which the installed modem names and/or network adapter names match exactly. The operating system version does not matter. If the systems are not identical, the imported configuration may not successfully connect to the Connection Manager.
The Export Configuration window lets you determine the name of file that is exported. After you have successfully identified the desired file, click OK.
Using the command line to import and export configuration files

Because some installations may not have the configuration user interface present, the import/export utility is available using the command line. wccfgupd [-i | e] [-f file] [-r] [-p] [-q] [-b file] [-d] -v -i -e -f file -r -p Show version of information Import a configuration file Export a configuration file file from which to import or from which to export. This flag is optional unless -q is specified. Delete the current configuration and replace it with the imported one. This flag is only valid when -i is specified. Make the exported configuration platform-independent. Use this to create a configuration valid for any hardware setup instead of only a hardware setup matching the exporting machines. This flag is valid only for export operations and the default is platform-dependent. Run quietly with no user interaction. file from which to back up and save the existing configuration.
-q -b file
Using trace
Setting up a trace from the Connections window lets you set up a trace either before starting a connection to the Connection Manager or after the connection is already active. The location of the trace file is /var/log/wc.log. To set up a trace: 1. In the Connections window, click the Tools menu and select Configure Trace. 2. Enter the properties in the trace tabs. 3. Click OK to close the trace window and begin tracing, or click Apply to begin tracing without closing the trace window.
Using the trace viewer

The Mobility Client Trace Viewer is a free-standing window that displays trace messages. The trace viewer only displays what is currently being logged. If the log levels and subsystems are set up so that nothing is being logged, then nothing appears in the trace viewer window. The viewer lets you save the contents of the window to a location of your choice, rather than just to the trace file: /var/log/wc.log. To turn on the trace facility, open the Trace Viewer by clicking Tools--> View Trace.... The messages displayed in the viewer are the same messages written to the trace file.
Configure trace properties

You can set up a trace to record diagnostic information for the Mobility Client. Your Connection Manager administrator might request a trace file from you to help diagnose a problem. After the initial Mobility Client installation, by default trace is turned on during the connection attempt. To turn tracing on, either open the Trace Viewer by clicking Tools--> View Trace...., or select a trace level other than Off using the trace configuration utility invoked by clicking Tools--> Configure Trace. The trace configuration tools utility also includes the following settings:
Trace levels
The controls on the level tab are: None Turns all logging off
Errors Messages about unexpected events on which you need to take action Warning Messages about events on which you may or may not need to take action Debug Data used for problem analysis Log All General information messages All messages and statements are logged
Subsystems
The controls on the Subsystems tab are: None Main Turns all logging off Messages logged in the main client code
IP stack Messages logged in libipstack.so Timers Messages logged by timers subsystem Link Protocol Messages logged by the Link Control Protocol Header reduction Messages logged in libipreduct.so API socket Messages logged by the TCP sockets used by the application programming interface Common Messages logged in libwgcmn.so that do not have a specific category Compression Messages logged in libwgcompress.so Port Device Messages logged in the process of sending and receiving data from the Connection Manager API Messages logged by the application programming interface
Messages logged by the port subsystem (for example, UDP or TCP)
Adapter monitor Messages logged when the IP interfaces change states User All Messages logged by a particular user ID All subsystems are logged
File
The controls on the File tab are: Flush log file When the box is selected, messages are flushed to the log file as they are written rather than being buffered. This option slows performance and is generally useful only for debugging. The default value is that the Flush log file box is cleared. Maximum file size Use the Maximum File Size Field to set the maximum size of your trace file. Trace messages are stored in a file named /var/log/wc.log. When the file reaches its maximum size, it is renamed to wc.bak and a new wc.log file is created for active trace data. Only two trace files are kept, the active trace file and the most recent previous file. v Default: 1400000 bytes v Range of values: 0 to 2147483647 inclusive
Viewer
The controls on the Viewer tab are: Display when connecting Select this check box to display the trace viewer during a connection attempt. Clear the check box to prevent the trace viewer from displaying during a connection attempt. Default: Display when connecting is not enabled. Close after connecting Select this check box to close the trace viewer after a connection attempt completes. Clear the check box to keep the trace viewer displaying after the connection attempt completes. Default: Trace when connecting is enabled. Trace when connecting Select this check box to enable the trace facility during a connection attempt. The trace information is saved to the file arttrace.txt. Clear the check box to disable the trace facility during a connection attempt. Default: Trace when connecting is enabled.
Roaming between networks

In IP-based networks, the Mobility Client can dynamically switch the secure connection to the Connection Manager from one physical network adapter to another with little or no user intervention and usually with no interruption to applications. When multiple interface adapters are available, the client allows the user to easily switch between them. On a device that cannot support multiple adapters, a user can remove one adapter and replace it with another. The Mobility Client will detect the change and automatically switch the connection to the new adapter with no user intervention.
10
To make sure that an adapter has successfully linked to the network, from the command line enter /sbin/mii-tool. The response should look like eth0: negotiated 100baseTx-FD flow-control, link ok. If the link is okay, then the Mobility Client can get the status from the adapter and automatically roam to that interface adapter.
Specifying the network adapter to use

Use this procedure to set the priority of available network adapters to use when you leave the range of your current network adapter access point. Right-click the connection name, then click Properties on the pop-up menu. Select the Networks tab to see the list of configured network adapters. You can change the priority of network adapters to be used when roaming or add or delete such adapters.
Viewing connection status

To view connection status, right-click the active connection, then click Status... on the menu. The Status window displays information about your connection to the Connection Manager, under these tabs: Status Provides information about the status of the network connection and the virtual connection of your device with the Connection Manager. Virtual connection Displays the connection status with the Connection Manager, shown as either "Logged on" or "Logged off". Also displays the local IP address used by the network to access your mobile computer as well as the IP address of the Connection Manager. The connection time is also shown here. Network connection Displays the status of your current network connection and the connection protocol it uses. Also displays the name and IP address of the network connection and, in some cases, additional information, including the connection name, description of the interface, or hardware description. Statistics Gives an indication of the number of bytes and packets transmitted and received. These statistics are for the current connection only and are not cumulative across multiple connections. Roaming This tab appears only when you are connected using an advanced roaming connection and have more than one interface definition for a connection. The Roaming tab displays information about the status of interfaces defined for the Mobility Client and also lets you control the roaming characteristics of your network interfaces. You can enable or disable automatic roaming, designate a specific network connection as the active connection, and suspend or resume the Mobility Client connection. Two other boxes may be displayed near the bottom of the Status tab. These boxes show the status of a connection in progress and the advanced settings for an active connection.
11
Logon status While a connection is in progress, the Logon status box appears near the bottom of the Status tab. This box contains a status bar that shows the progress of the Mobility Client connection to the Connection Manager and a Cancel button that allows you to cancel the connection in progress. Advanced Click the Advanced button to show advanced settings for the connection, including whether the connection traffic is encrypted, compressed, and whether header reduction is applied. Note that compression and header reduction values may change depending on the network to which you are connected. For example, as you roam between different networks, the values may change dynamically.
Manually suspending and resuming communications

If your Mobility Client uses a dial connection capable of entering short-hold mode, you can force it into short-hold mode. You might use this function if you have ended a communication and do not want to wait for the timer to expire. The timer equates to the amount of time specified in the Wait field on the Redial properties of the PPP tab. Right-click the connection or the antenna icon and select Suspend from the pop-up menu. When you suspend communication, the Mobility Client enters short-hold mode. Incoming traffic causes it to reconnect. When you suspend communications, the menu item changes to Resume. If you select Resume, the Mobility Client reconnects even if no traffic is flowing, and the timer begins.
Viewing connection properties

To view connection status, right-click the connection, then click Properties... on the menu to view the following properties tabs: Attributes Check boxes on this tab allow you to: v have the connection prompt for a user ID and password v start the connection automatically whenever the operating system starts v create a default route through the Mobility Client connection for all traffic bound for hosts in non-adjacent networks Security Allows you to set the key exchange and encryption methods for the connection. Networks Allows you to: v Add a network connection to the list of networks configured for the connection v Delete a network from the list of networks configured for the connection v Change the priority of selected networks when using automatic roaming v View or modify the properties of a configured network To view or modify the properties, including Roaming, for the Mobile Network Interface (MNI), select a configured network and click Change .... The following configuration tabs appear:
12
Gateway View or change the settings for Connection Manager address, supported protocols, ports and, for HTTP and HTTPS only, the authentication proxy server address and port. Alternate address Enables you to specify a different address to be used to communicate with the Connection Manager. For example, if you use one IP address when you are connected at work and another when you are connected at home, you can specify the Connection Manager address for each location. PPP Select the type of PPP connection and the connection timeout. This tab also contains the Redial properties for dial connections capable of short-hold mode.
Roaming The fields on this tab allow you to: v Set the number of seconds for the Mobility Client to wait before it roams to the next available network. v Set the threshold time for the Mobility Client to wait before it roams from this connection to a lower priority network. Autostart Select one or more applications to be started automatically after successfully logging on to the Connection Manager.
Deleting a connection
To delete an existing connection: 1. Right-click the connection in the Connections window that you want to delete. 2. Select Delete on the pop-up menu. 3. In the confirmation window, click Yes to delete the connection and remove the connection icon from the Connections window. Click No to cancel the deletion.
Disconnecting from the Connection Manager

To 1. 2. 3. disconnect the active connection with the Connection Manager: Click the connection, then click the Connection menu. Click Disconnect. In the confirmation window, click Yes to end the active connection. Click No to cancel the disconnect.
Changing font size and style

You can change the font size and font family if the default settings are not adequate. When you change the fonts for the Mobility Client, it will also affect any application on your system that uses the Qt application framework. If you have version 4 or higher of the Qt application, make sure that you are not logged in using root administrator ID, then: 1. Type qtconfig from a command prompt. 2. Click the Fonts tab. Change the family or point size as desired. 3. Click File > Save, then click File > Exit.
13
If your version of the Qt application is lower than version 4, you must edit the <home directory>/.config/Trolltech.conf file if you want to change the font. Note: To determine which version of the Qt application you have, type qtconfig from a command prompt, then click Help -> About Qt from the Qt Configuration window.
14
Chapter 3. Configuring clients with configuration files

There are several configuration files that provide the parameters used by the Mobility Client program to establish a connection with a Connection Manager. After a connection is established, values are saved at logoff to client configuration files. Rewriting the files is desirable because it often shortens the negotiation process on subsequent connection attempts. The PreserveConfigFile parameter overrides this behavior. The files consist of lines of the form: parameter-name = parameter-value. Parameter names are alphanumeric strings. Parameter values can be textual or numerical. Note that parameters that take Boolean values use 1 for true and 0 for false. An effort has been made to find sensible default values for most of the available parameters, and it is rarely necessary to manually edit this file. If no value is specified for a parameter, the Mobility Client will either use a default value, attempt to negotiate a value for the parameter at connect time, or prompt the user. There is one configuration for global parameters called client services and two or more files for each connection icon that is created. The one file, wclientd.conf, that affects client services is located in the installation directory. The installation directory is /opt/ibm/MobilityClient/. There are two or more files for each connection, depending on how many interfaces are defined for the connection. Connection definitions created with the Mobility Client are located in the user's home directory in the .wclient subdirectory. There are two file types for each connection: the main connection file containing settings that affect all interfaces and also one or more interface definition files. The naming convention is: v conn<connection_number>.conf for the main connection file v conn<connection_number>_<interface_number>_device.conf for interface definition files The connection number is unique among all the connections for the user and the interface number is unique for the particular connection. In previous versions the connection name that appeared in the Mobility Client interface was used to name the connection file. The naming convention was <connection_name>.conf for the main connection file and <connection name>_device.conf for the interface definition. Connections migrated from previous versions will keep the previous naming convention. But if new interface definitions are added for a migrated connection, they will be created as <connection_name>_<interface_number>_device.conf. For a description of these parameters, see: v Table 1 on page 16 for parameters that affect client services v Table 2 on page 19 for parameters that affect each connection v Table 3 on page 23 for parameters that affect only IP-LAN interfaces v Table 4 on page 28 for parameters that affect only PPP/RAS interfaces
15
Table 1. Parameters that affect client services Parameter name Description
Note: When you change the value of any of these parameters, the two services, wclientd and wcstatusd, must be stopped, then started for the change to take effect. Make sure you are logged in as root. To stop the services: enter /etc/init.d/ibm-wclient stop. To start the services: /etc/init.d/ibm-wclient start. APITcpListenPort AutoRefreshDHCP Specifies the TCP port on which the wclientd service listens. The default value is 10555. If either of the following conditions are detected: v Wireless Access Point hardware address change v Ethernet cable is newly plugged in then the status daemon requests a new DHCP address from the network servers (not the Connection Manager server address, but public network address). Note: If installed adapters are configured for static IP addresses, then you should turn this feature off. Leaving it on overwrites the static IP configuration if one of the above conditions are detected.Switching this value to off requires the user to manually renew addresses for adapters configured for DHCP if the system roams out of the configured subnet. The default value is 1 (on). Note: If the ifplugd or netplugd services are running, this feature is automatically disabled. CloseTraceMsgsOnConnect EnableAccountId EnableChangePassword Closes the trace viewer after a connection attempt completes. To enable this function, set this parameter to 1. By default, this parameter is 1. When this boolean option is set to 1, the User ID input field displays on the Connect panel. By default, this boolean option is 1. When this boolean option is set to 1, a change password entry displays in the Mobility Client context menu of the currently connected connection. By default, this boolean option is 1. When this boolean option is set to 1, the Organizational unit input field displays on the Connect panel. By default, this boolean option is 1. When this boolean option is set to 1, the Password input field displays on the Connect panel. By default, this boolean option is 1. When this boolean option is set to 1, the Save password check box displays on the Connect panel. By default, this boolean option is 1. When this string is null, any system group can access the API. If this string matches a system group name, then only users that are members of that group can access the API. The default value is null. Specifies a space-delimited or comma-delimited list of adapters to ignore when querying the system for installed adapters. The default value is lo, sit0, wc0, usbd0, vmnet1, mn0, mn1, mn2, mn3. To list all interfaces, from the /sbin directory, enter ifconfig -a. Evaluate the list of interfaces to determine if the installed adapter should be ignore and if so, add it to this parameter. LogFile LogFlush The name of the file used by the Mobility Client for writing log messages. The default value is /var/log/wc.log. If this boolean parameter is set to 1, messages are flushed to the log file as they are written rather than being buffered. This option slows performance and is generally only useful for debugging. The default value is 0.
EnableDomain EnablePassword EnableSavePassword Group
HiddenAdapters
16
Table 1. Parameters that affect client services (continued) Parameter name LogGroup Description When this string is null, any system group can access the trace settings. If this string matches a system group name, then only users that are members of that group can access the trace settings. The default value is null. This text parameter determines the verbosity of the Mobility Clients logging. The higher logging levels can cause a dramatic decrease in performance and are only useful for debugging purposes. Most users should use the default level of error. Multiple values can be specified separated by commas. Allowable values are: error warn log debug all none LogMaxSize Messages about unexpected events on which you need to take action Messages about events on which you may or may not need to take action General information messages Data used for problem analysis All statements and messages Turns all logging off.
LogLevel
Specifies the maximum size, in bytes, of the trace file stored in /var/log/wc.log. The default value is 1,400,000 bytes. The range of values is 0 to 2147483647 inclusive. If this boolean parameter is set to 1, only the root user ID can change the trace log settings. A value of 0 indicates that any user can access the trace settings, depending on the value of the LogGroup parameter. The default value is 0.
LogRootOnly
17
Table 1. Parameters that affect client services (continued) Parameter name LogSubSystems Description This text parameter is used to suppress messages from some Mobility Client subsystems. Generally, the default value of all should be used. Multiple values can be specified separated by commas. Allowable values are: main common Messages logged in libwgcmn.so and do not have a specific category ip_stack Messages logged in libipstack.so compress Messages logged in libwgcompress.so hdr_reduct Messages logged in libipreduct.so port device timer alp API Messages logged by the port subsystem (for example, UDP or TCP) Messages logged in the process of sending and receiving data from the Connection Manager Messages logged from the timer subsystem. Messages logged by the Link Control Protocol. Messages logged by the application programming interface. Messages logged in the main client code
socket_api Messages logged by the TCP sockets used by the API. adapter_monitor Messages logged when IP interfaces change state. api_user Messages logged through the Mobility Client API. all none RootOnly Everything Turns all logging off.
If this boolean parameter is set to 1, only the root user ID can access the API. A value of 0 indicates that any user can access the API, depending on the value of the Group parameter. The default value is 0. Displays the trace viewer during a connection attempt. To enable this function, set this parameter to 1. By default, this parameter is 0. When this boolean option is set to 1, the Mobility Client saves the value entered for User ID in the connection file. By default, this boolean option is 1. The default location of the log file: /var/log/wcstatus.log. If this boolean parameter is set to 1, messages for wcstatusd are flushed to the log file as they are written rather than being buffered. This option slows performance and is generally only useful for debugging. The default value is 0.
ShowTraceMsgsWindow SaveAccountId
StatusLogFile StatusLogFlush
18
Table 1. Parameters that affect client services (continued) Parameter name StatusLogLevel Description Allowable values are: all debug none StatusLogMaxSize All statements and messages Data used for problem analysis Turns all logging off.
Specifies the maximum size of the trace file stored in /var/log/wcstatus.log. The default value for x86 systems is 1400 KB. The range of values is 0 to 2147483647 inclusive. Allowable values are: device main port Logs adapter status changes Messages logged in the main client code Messages logged by the port subsystem (for example, UDP or TCP)
StatusLogSubSystems
The default value is device. StatusPollInterval The system is periodically queried for network hardware adapter changes. This value controls the query period. The default value is 2 seconds. UDP port that the client core uses to contact the status daemon. The default value is 8979. Enables the trace facility during a connection attempt. The trace information is saved to the file /var/log/wc.log. Set this parameter to 0 to disable tracing. By default, this parameter is 1. Sets the minimum signal strength that is required for an 802.11b adapter to show up in the list of adapters. The link quality varies between 0 and 92, with higher being better. This value sets a minimum cutoff value below which the adapter is removed from the adapter list. To disable the link quality check, set the value to -1. The default value is 0.
StatusServerPort TraceWhileConnecting
WirelessLinkQualityCutOff
Table 2. Parameters that affect each connection Parameter name AccountId AuthMethod Description The login accounts name to use when establishing the connection. This parameter does not include the accounts organizational unit. Method that the Connection Manager uses to validate the Mobility Client. Do not change this value from the default value of 1 unless instructed by your administrator. Allowable values are: 0 1 2 Autostart1...Autostartn The Connection Manager does not require any authentication. The Connection Manager requires user ID and password authentication. The Connection Manager requires Diffie-Hellman authentication.
One Autostart for each application to be automatically started after a successful logon to the Connection Manager. The application name includes the complete path, without parameters. The order of which application is started first is determined by its numeric order in the configuration file. If AutostartDisabled is set to 1, then the applications are ignored and no checking is done.
AutostartDisabled
19
Table 2. Parameters that affect each connection (continued) Parameter name AutostartParams1 ... AutostartParamsn Description One AutostartParams for each parameter required for the corresponding Autostartn application. Must be present, but blank, if no parameters are required for a given application. The order of which parameters are checked first is determined by the numeric order in the configuration file. The value used to decrement padded configure requests when performing black hole detection. The default value is 100 bytes. Name of the broadcast program to start at completion of logon. This programs receives broadcast messages from the Connection Manager. The default value is null. The UDP port number on which the Mobility Client broadcast program listens for broadcast messages from the Connection Manager. The default port is 9999. Stores the last fully qualified PKCS 12 filename when certificate-based authentication is required by the Connection Manager. This filename is the default the next time certificate-based authentication is requested. Password for the PKCS 12 file specified under CertAuthP12File. Otherwise, the user is always prompted for the password. Specifies the amount of time in seconds from when the Mobility Client starts attempting to connect to the Connection Manager until a message displays indicating that the connection is still being attempted. The default value is 60. Setting this value to zero (0) disables the timer. 1= an advertised speed of network connection is 10 Mbps or greater, client will pad configuration requests sent to the gateway to the maximum network MTU size in an effort to detect black holes. If the configuration request times out, then the retry will be decremented using BlackHoleDecrement before being retransmitted. This should be set to 0 in the case where the client is using a high speed adapter, but there is a very slow or inefficient intermediate link between the client and the gateway. The default value is 1. DisableRoaming 1= prevents the automatic cross-network roaming from occurring for use of custom applications that are using the Mobility Client Toolkit. The default value is 0. The DNS domain name supplied by the Connection Manager for the current connection. It is not necessary to supply a value for this parameter, as it is set by the Connection Manager at the time the connection is established. Specifies the number of consecutive echo timeouts processed before the Mobility Client displays an error to indicate that the Connection Manager is not responding. The default value is 3. This parameter determines the type of encryption that the Mobility Client attempts to negotiate with the Connection Manager. The value should be one of the Connection Manager encryption minor type numbers. The available type numbers are: 14 12 10 1 AES 256-bit CBC (cipher block chaining) mode AES 192-bit CBC mode AES 128-bit CBC mode DES CBC
BlackHoleDecrement BroadcastPgmName
BroadcastPort
CertAuthP12File
CertAuthP12PW ConnectionTimeout
DetectBlackHoles
DNSDomainName
EchoTimeoutThreshold
Encryption
0 No encryption The default value is 14.
20
Table 2. Parameters that affect each connection (continued) Parameter name GatewaySuppliesDNS Description When this boolean option is set to 1, DNS information negotiated with the Connection Manager is set in the system environment at connect time. The DNS information typically includes primary and secondary DNS servers and the local domain name. This results in the /etc/resolv.conf file being backed up and edited. When the Mobility Client is not shut down cleanly, /etc/resolv.conf may not be restored properly. If this happens, the original DNS configuration can be restored by entering the /etc directory and renaming resolv.conf.ibmwc<pid> backup to resolv.conf. The default value is 1. The Connection Managers address on the private network. This parameter is negotiated with the Connection Manager at connect time. Mobility Client retry value for connections 10Mbps or faster. This parameter is used only when UseSpeedForWLPSettings=1 and UDP is the protocol used to connect to the Connection Manager. The default value is 4. Mobility Client timeout value used for connections 10 Mbps or faster. This parameter is used only when UseSpeedForWLPSettings=1 and UDP is the protocol used to connect to the Connection Manager. The default value is 4. A list of interfaces that are associated with a connection. The maximum transmission unit for the IP stack interface. The default value is 1400 bytes. When RequestTransportProfile=1, this entry is ignored. LowSpeedWLPRetryCount Mobility Client retry value used for connections 57600 bps or slower. This parameter is used only when UseSpeedForWLPSettings=1 and UDP is the protocol used to connect to the Connection Manager. Mobility Client timeout value used for connection 57600 bps or slower. This parameter is used only when UseSpeedForWLPSettings=1 and UDP is the protocol used to connect to the Connection Manager. Mobility Client retry value used for connections greater than 57600 and slower than 10Mbps. This parameter is used only when UseSpeedForWLPSettings=1 and UDP is the protocol used to connect to the Connection Manager. Mobility Client timeout value used for connections greater than 57600 bps and slower than 10 Mbps. This parameter is used only when UseSpeedForWLPSettings=1 and UDP is the protocol used to connect to the Connection Manager. The address assigned to the client interface by the Connection Manager. It is negotiated at logon time and should not need to be manually configured. Modification level number of the configuration file. When this boolean option is set to 1, the Connect panel is bypassed and instead the connection progress indicator is displayed only if accountID (UserID), Domain (Organizational unit), and Password were previously saved in the configuration file. The LDAP organizational unit corresponding to the Connection Manager user ID specified by the AccountId parameter. The password for the current account. It is best to leave this blank and let the Mobility Client prompt for it, if needed. If the SavePassword parameter is set to 1, the Mobility Client uses an exclusive OR (XOR) algorithm to alter the password and save it to the configuration file. For security reasons, this method is preferable to entering in plain text form. If the password is entered in plain text in the configuration file and the PreserveConfigFile is set to 0, the Mobility Client saves the password using the XOR algorithm form on exit.
GWMNIAddress HiSpeedWLPRetryCount
HiSpeedWLPTimeout
InterfaceList IPStackMTU
LowSpeedWLPTimeout
MedSpeedWLPRetryCount
MedSpeedWLPTimeout
MobileAddress Mod OneButtonConnect
OrgUnit Password
21
Table 2. Parameters that affect each connection (continued) Parameter name PasswordPort PreferredInterface PrereqAppName1 ... PrereqApplicationName16 Description The Connection Manager port that the Mobility Client connects to for password changes. The default value is 8888. The default interface to start for this connection. Where PrereqAppName1 is the name of the first process that must be running before the Mobility Client attempts to connect, and PrereqAppProcessn is the last process that must be running before the Mobility Client attempts to connect. The application name includes the complete path. The order of which application is checked first is determined by the numeric order in the configuration file. One PrereqAppProcess for the process name of each application to check before logon. When a process is running, t values are found by typing ps -e from a shell prompt. The order of which process is checked first is determined by the numeric order in the configuration file. If PrerequisiteDisabled is set to 1, then the applications are ignored and no checking is done. The primary DNS server as supplied by the Connection Manager at connect time. This parameter indicates how many times the client retries RADIUS authentication attempts after timeout failures. Default value is 2. This parameter indicates the time in seconds that the client waits for a response from a radius authentication request. Default value is 15. Release number of the configuration file. 1= The Mobility Client sends the name and the speed of the adapter when it logs in and roams from one network to another. 0= The transport profile is not requested. The default value is 1. The set of routes to be configured which were sent to the Mobility Client from the Connection Manager the last time a connection was established. When this boolean option is set to 1, the Mobility Client stores the password using an XOR algorithm. The default value is 1. The secondary DNS server as supplied by the Connection Manager at connect time. When this boolean option is set to 1, the Mobility Client sets the default route for IP traffic to flow through the Mobility Client with the exception of any individual routes that are previously set in the routing table. The default value is 0. The subnet mask to use for the Mobility Client network interface. This parameter is supplied by the Connection Manager at connect time.
PrereqAppProcess1 ... PrereqAppProcess16
PrerequisiteDisabled PrimaryDNS RadiusRetryAttempts RadiusTimeout Release RequestTransportProfile
Routes SavePassword SecondaryDNS SetDefaultRoute
SubnetMask
22
Table 2. Parameters that affect each connection (continued) Parameter name UseSpeedForWLPSettings Description Sets the speed to use to determine Mobility Client retry count and timeout. If this value is set to 0 or if UDP is not the protocol used to connect to the Connection Manager, ALPRetries and ALPTimeout are used. If this value is set to 1 and UDP is the protocol used to connect to the Connection Manager, the value used depends on the network speed detected. One of the following sets of parameters is used for the retry count and timeout: network detected speed is <57600 bps LowSpeedWLPTimeout LowSpeedWLPRetryCount network detected speed is >=57600 bps and <10,000,000 bps MedSpeedWLPTimeout MedSpeedWLPRetryCount network detected speed is >= 10,000,000 bps HiSpeedWLPTimeout HiSpeedWLPRetryCount Version Version number of the configuration file.
Table 3. Parameters that affect only IP-LAN interfaces Parameter name AdapterNameOverrideString Description Allows for the adapter name string sent to the Connection Manager for transport profile selection to be overridden. The default value is null, and the parameter is not used. Allows for the connection speed sent to the Connection Manager for transport profile selection to be overridden. The default value is null, and the parameter is not used. The number of times to reattempt a failed logon negotiation with the Connection Manager. The default value is 3. Used if UseSpeedForWLPSettings is set to 0 or when the UDP protocol is not used to connect to the Connection Manager. The number of seconds to wait for a logon attempt to complete before timing out and closing the connection. The default value is 10. Used if UseSpeedForWLPSettings is set to 0 or when the UDP protocol is not used to connect to the Connection Manager. The list of alternate gateway addresses used by the Mobility Client when roaming. The list is saved in the following format: AlternateGatewayAddress=9.27.0.0 255.255.0.0 9.27.27.136,9.47.0.0 255.255.0.0 9.27.27.136 Each alternate gateway entry consists of three values. The first is the local IP address. The second is the mask. The third is the alternate IP address for the Connection Manager. The three values for an alternate gateway entry are separated by a space. Each alternate gateway definition is separated by a comma. BindPort Specifies the port number on which the Mobility Client listens for data sent from the Connection Manager. This parameter is used only for UDP connections.
AdapterSpeedOverride
ALPRetries
ALPTimeout
AlternateGatewayAddress
23
Table 3. Parameters that affect only IP-LAN interfaces (continued) Parameter name Compression Description When this boolean parameter is set to 1, the Mobility Client attempts to negotiate a compressed connection with the Connection Manager. The only form of compression that is currently supported is BSD LZW compression as provided by the zlib library. This parameter is useful for low-bandwidth connections, but is not recommended in cases where the transmission speed is largely CPU bound (for example, an encrypted broadband connection). The default value is 0. When RequestTransportProfile=1, this entry is ignored. DeviceLib A library containing functionality and options specific to the type of network device used to make the connection. Device libraries are installed in the /opt/ibm/MobilityClient/lib/devices directory. When this boolean option is set to 1, the Mobility Client attempts to combine small packets in order to deliver larger packets to the Connection Manager. The maximum size for joined packets is determined by the NetworkMTU option. This option is only recommended for low-bandwidth connections. The default value is 0. When RequestTransportProfile=1, this entry is ignored. EncryptedProxyPassword When a connection is established using a proxy server the Mobility Client must supply credentials for the proxy server to authenticate. This field is the password. When this boolean option is set to 1, then outbound packets whose source address does not match the address of the Mobility Client as assigned by the Connection Manager are discarded. The default value is 0. When RequestTransportProfile=1, this entry is ignored. GatewayAddress GatewayAddressDec HeaderReduction The physical IP address of the Connection Manager. The IP address of the Connection Manager in dotted-decimal format. This entry is for internal use and any value entered is ignored. When this boolean parameter is set to 1, the Mobility Client attempts to negotiate IP header reduction with the Connection Manager. IP header reduction can reduce the amount of traffic sent over the network interface, but is generally useful only for low-bandwidth connections. The default value is 0. When RequestTransportProfile=1, this entry is ignored. HttpProxyAddr Specifies either the IP address or the host name of the proxy server. This parameter is used only if you have enabled proxy authentication on the Connection Manager. Specifies the port number used to communicate with the proxy server. This parameter is used only if you have enabled proxy authentication on the Connection Manager. Specifies the port number used to send data to the Connection Manager for an HTTP connection. The default value is 80. Specifies the port number used to send data to the Connection Manager for a secure HTTP connection. The default value is 443. This option is used only when HTTPS is a supported protocol. It specifies the file used to store the certificates used when the client connects to the Connection Manager using HTTPS, if the user chooses to store the certificates. The default value is <user's_home_directory>/.wclient/ wc.kdb.
EnablePktJoining
FilterOtherSourceAddresses
HttpProxyPort
HttpSendPort HttpsSendPort HttpsSSLKeyRingFile
24
Table 3. Parameters that affect only IP-LAN interfaces (continued) Parameter name HttpsSSLTimeout Description This option is used only when HTTPS is a supported protocol. It sets the time in seconds to wait for the secure socket layer (SSL) packets when connecting to the Connection Manager. Specifies the time in seconds for the Mobility Client to wait while roaming and unable to connect to a network that is in range. The default is 120. The time in seconds to wait before sending a keepalive packet to the Connection Manager. If this parameter is set to a nonzero value, the Mobility Client sends an LCP echo packet to the Connection Manager at this interval. This parameter is useful for preventing the Connection Manager from dropping a connection due to excessive idle time. The amount of idle time before a client connection is dropped differs between Connection Managers, but 600 to 1200 seconds is a reasonable setting in most cases. The default value is 10. When RequestTransportProfile=1, this entry is ignored. Mod NetworkAverageBPS Modification level number of the configuration file. Connection throughput in bits per second. If greater than 33600, header reduction and other TCP optimizations are disabled. The default value is 10000000. The maximum transmission unit specified in bytes for the network used to connect to the Connection Manager. The valid range is 128-4092. The default value is 1500. When RequestTransportProfile=1, this entry is ignored. PktCompressThreshold When compression is enabled and this parameter is nonzero, the Mobility Client uses this value to determine the size of the smallest packet (in bytes) that it should attempt to compress. Very small packets often cannot be compressed. This parameter can be used to prevent wasting valuable CPU cycles attempting it. The default value is 50. The time specified in seconds used by the link layer to terminate a connection if the Connection Manager does not respond to a request sent by the Mobility Client. The default value is 20. When RequestTransportProfile=1, this entry is ignored. PreferredAdapter ProxyUsername Specifies the network adapter that is used for roaming, if it is available. There is no default value. When a connection is established using a proxy server the Mobility Client must supply credentials for the proxy server to authenticate. This field is the user name. Release number of the configuration file.
InRangeConnFailedRetryTimeout
KeepAliveInterval
NetworkMTU
PktTimeout
Release
25
Table 3. Parameters that affect only IP-LAN interfaces (continued) Parameter name RoamFromThreshold Description Specifies the number of seconds that the Mobility Client connection to a network has been in Active status and acts as a threshold value for determining which Wait interval to use when roaming from this connection to a lower priority network, if the status changes to Out of range or Unavailable. This setting helps determine if you are moving into or out of the coverage area of a network. If you are moving into coverage area, you may want to delay roaming from the network quickly because there could be a period of time when the status flips back and forth between active and inactive. This delay gives the network a chance to stabilize and establish the actual status. However, if you are moving out of a coverage area, as indicated that the network status has been active for a given period of time and then becomes inactive, then you may want to roam from that network more quickly. The default value is 0. RoamFromWaitOverThreshold Specifies the number of seconds that the Mobility Client waits before roaming from this connection to another Available network of a lower priority. When the network status has been Active for less than the amount of time specified in the RoamFromThreshold setting, then the connection may be in the periphery of a network coverage area and may need additional time to establish its actual status. This setting determines the number of seconds the Mobility Client waits until it will roam from this network to another of lower priority. The value of this setting should be more than the value of the RoamFromWaitUnderThreshold setting. The default value is 0. RoamFromWaitUnderThreshold Specifies the number of seconds that the Mobility Client waits before roaming from this connection to another Available network of a lower priority. When the network status has been Active for more than the amount of time specified in the RoamFromThreshold setting and then becomes Unavailable, this setting determines the number of seconds the Mobility Client waits until it will roam from this network to another of lower priority. The value of this setting should be less than the value of the RoamFromWaitOverThreshold setting. The default value is 0. RoamToWait Specifies the number of seconds that the Mobility Client waits after the network is available before the Mobility Client will roam to it and make it the Active connection. If the connection is being established on the periphery of a network coverage area, this setting allows a period of time for the Mobility Client to make sure that the connection status does not go Out of Range or Unavailable before it attempts to roam to it. The default value is 0. When a connection is established using a proxy server the Mobility Client must supply credentials for the proxy server to authenticate. When this boolean option is set to 1, the Mobility Client stores the password. The port used to send data to the Connection Manager. This parameter is used only for UDP connections. The default value is 8889.
SaveProxyPassword
SendPort
26
Table 3. Parameters that affect only IP-LAN interfaces (continued) Parameter name SocketConnectionTimeout Description Specifies the timeout used when establishing a UDP, HTTP, or HTTPS connection with the Connection Manager. This is the number of seconds to wait before the Mobility Client attempts to connect using another protocol. Specifies the protocols that can be supported on the Mobility Client. The value for this parameter can be one or more of the following, in a comma-separated list: Connectionless Use UDP as a protocol to connect to the Connection Manager. ConnectionOriented Use HTTP as a protocol to connect to the Connection Manager. ConnectionOrientedSecure Use HTTPS as a protocol to connect to the Connection Manager. TCPIP_Ports2Filter This entry can exist for a connection or for an interface. The interface section is checked first, and if no entry is found, then the connection section is used. List of TCP ports, separated by spaces, from which to filter packets. When RequestTransportProfile=1, this entry is ignored. TcpOptEnable When this boolean option is set to 1, TCP optimization is enabled. The default value is 0. When RequestTransportProfile=1, this entry is ignored. TcpOptMaxBurst Maximum number of unacknowledged TCP packets transmitted. The optimization engine withholds packets to keep from overloading a directional channel of a wireless network. The range of values is 516, inclusive. The default value is 8. When RequestTransportProfile=1, this entry is ignored. TcpOptMaxWindowSize Maximum size of the TCP sliding window in bytes. The optimization engine adjusts the TCP window on-the-fly as a means of performing network latency-specific flow control. The range of values is 204865535, inclusive. A value of zero disables this function. The default value is 0. When RequestTransportProfile=1, this entry is ignored. TcpOptRetransmitTTL Length of time in milliseconds to suppress TCP retransmit packets. A value of 0 disables TCP retransmit suppression. The default value is 1000. When RequestTransportProfile=1, this entry is ignored. TrayUpdateInterval Minimum time in seconds that the client will wait between sending eMsg_PacketReceived events or eMsg_PacketTransmitted events. A value less than or equal to 0 disables sending these events. The default value is 2. This entry can exist for a connection or for an interface. The interface section is checked first, and if no entry is found, then the connection section is used. List of UDP ports, separated by spaces, from which to filter packets. When RequestTransportProfile=1, this entry is ignored.
SupportedProtocols
UDPIP_Ports2Filter
27
Table 3. Parameters that affect only IP-LAN interfaces (continued) Parameter name UseBindPort Description Specifies whether the Mobility Client listens on a specific port number for data sent from the Connection Manager. This parameter is used only for UDP connections. This parameter is used to enable or disable the use of a proxy for the Mobility Client to connect to the Connection Manager for connection-oriented (HTTP or HTTPS) connections. The default value of 0 disables proxy authentication. If you enter 1 to enable proxy authentication, you must also provide the proxy server address and port number. Use the HttpProxyAddr parameter to specify the address and HttpProxyPort for the port number, as provided by the system administrator. This boolean parameter determines whether the UDP echo function for the Mobility Client and Connection Manager is used during the logon sequence when connecting over UDP. If UseUDPEcho=1, the UDP echo function uses a test packet to check whether the Mobility Client can reach the gateway and what the Maximum Transmission Unit (MTU) should be. If UseUDPEcho=0, then the UDP echo function is not used. This parameter is updated after each logon, based on whether the Connection Manager to which the Mobility Client is connected supports the function. For migrated connections, the default value is 0. For new connections, the default value is 0 if only the UDP protocol is enabled or 1 if http, https, or both are selected in addition to the UDP protocol. Version Version number of the configuration file.
UseHttpProxy
UseUDPEcho
Table 4. Parameters that affect only RAS/PPP interfaces Parameter name AdapterNameOverrideString Description Allows for the adapter name string sent to the Connection Manager for transport profile selection to be overridden. The default value is null, and the parameter is not used. Allows for the connection speed sent to the Connection Manager for transport profile selection to be overridden. The default value is null, and the parameter is not used. The number of times to reattempt a failed logon negotiation with the Connection Manager. The default value is 3. Used only if UseSpeedForWLPSettings is set to 0 or when the UDP protocol is not used to connect to the Connection Manager. The number of seconds to wait for a logon attempt to complete before timing out and closing the connection. The default value is 10. Used only if UseSpeedForWLPSettings is set to 0 or when the UDP protocol is not used to connect to the Connection Manager. The list of alternate gateway addresses used by the Mobility Client when roaming. The list is saved in the following format: AlternateGatewayAddress=9.27.0.0 255.255.0.0 9.27.27.136,9.47.0.0 255.255.0.0 9.27.27.136 Each alternate gateway entry consists of three values. The first is the local IP address. The second is the mask. The third is the alternate IP address for the Connection Manager. The three values for an alternate gateway entry are separated by a space. Each alternate gateway definition is separated by a comma.
AdapterSpeedOverride
ALPRetries
ALPTimeout
AlternateGatewayAddress
28
Table 4. Parameters that affect only RAS/PPP interfaces (continued) Parameter name auto-reconnect Description When this boolean option is set to 1, the Mobility Client should attempt to reconnect to the PPP server on connection failure, even though the Mobility Client has no data to send. This is useful if you want to maintain a continuous connection. When the option equals 0, the Mobility Client enters short-hold mode on connection failure. Specifies the port number on which the Mobility Client listens for data sent from the Connection Manager. This parameter is used only for UDP connections. When this boolean parameter is set to 1, the Mobility Client attempts to negotiate a compressed connection with the Connection Manager. The only form of compression that is currently supported is BSD LZW compression as provided by the zlib library. This parameter is useful for low-bandwidth connections, but is not recommended in cases where the transmission speed is largely CPU bound (for example, an encrypted broadband connection). The default value is 0. When RequestTransportProfile=1, this entry is ignored. connect-retries Specifies the number of times the Mobility Client attempts to reconnect to the PPP server after the initial connect attempt fails. Connection retries also occur when the Mobility Client comes out of short-hold mode and the initial dial attempt fails to connect to the PPP server. The default value is 0. Specifies the amount of time, in seconds, the Mobility Client waits after an unsuccessful attempt to connect to the PPP server before attempting to reconnect. The default value is 60. The amount of time, in seconds, the Mobility Client waits to connect to the PPP server before timing out. A library containing functionality and options specific to the type of network device used to make the connection. Devices libraries are installed in /opt/ibm/MobilityClient/lib/devices/. Contains driver-specific information that should not be edited. When this boolean option is set to 1, the Mobility Client attempts to combine small packets in order to deliver larger packets to the Connection Manager. The maximum size for joined packets is determined by the NetworkMTU option. This option is only recommended for low-bandwidth connections. The default value is 0. When RequestTransportProfile=1, this entry is ignored. EncryptedProxyPassword When a connection is established using a proxy server the Mobility Client must supply credentials for the proxy server to authenticate. This field is the password. When this boolean option is set to 1, then outbound packets whose source address does not match the address of the Mobility Client as assigned by the Connection Manager are discarded. The default value is 0. When RequestTransportProfile=1, this entry is ignored. GatewayAddress GatewayAddressDec The physical IP address of the Connection Manager. The IP address of the Connection Manager in dotted-decimal format. This entry is for internal use and any value entered is ignored.
BindPort
Compression
connect-retry-interval
connection-timeout DeviceLib
DriverSpecificData EnablePktJoining
FilterOtherSourceAddresses
29
Table 4. Parameters that affect only RAS/PPP interfaces (continued) Parameter name HeaderReduction Description When this boolean parameter is set to 1, the Mobility Client attempts to negotiate IP header reduction with the Connection Manager. IP header reduction can reduce the amount of traffic sent over the network interface, but is generally only really useful for low-bandwidth connections. The default value is 0. When RequestTransportProfile=1, this entry is ignored. HttpProxyAddr Specifies either the IP address or the host name of the authentication proxy server. This parameter is used only if you have enabled proxy authentication on the Connection Manager. Specifies the port number used to communicate with the authentication proxy server. This parameter is used only if you have enabled proxy authentication on the Connection Manager. Specifies the port number used to send data to the Connection Manager for an HTTP connection. The default value is 80. Specifies the port number used to send data to the Connection Manager for a secure HTTP connection. The default value is 443. This option is used only when HTTPS is a supported protocol. It specifies the file used to store the certificates used when the client connects to the Connection Manager using HTTPS, if the user chooses to store the certificates. The default value is <user's_home_directory>/.wclient/ wc.kdb. This option is used only when HTTPS is a supported protocol. It sets the time in seconds to wait for the secure socket layer (SSL) packets when connecting to the Connection Manager. Specifies the time in seconds for the Mobility Client to wait while roaming and unable to connect to a network that is in range. The default is 120. The time in seconds to wait before sending a keepalive packet to the Connection Manager. If this parameter is set to a nonzero value, the Mobility Client sends an LCP echo packet to the Connection Manager at this interval. This parameter is useful for preventing the Connection Manager from dropping a connection due to excessive idle time. The amount of idle time before a client connection is dropped differs between Connection Managers, but 600 to 1200 seconds is a reasonable setting in most cases. The default value is 10. When RequestTransportProfile=1, this entry is ignored. manage-card-modem When this boolean option is set to 1, the Mobility Client turns on the modem before attempting to establish a PPP connection when you are using a PCMCIA or CF modem. By default the modem is turned off by the operating system. The default value is 1. Modification level number of the configuration file. Connection throughput in bits per second. If greater than 33600, header reduction and other TCP optimizations are disabled. The default value is 10000000. The maximum transmission unit specified in bytes for the network used to connect to the Connection Manager. The valid range is 128-4092. The default value is 1500. When RequestTransportProfile=1, this entry is ignored.
HttpProxyPort
HttpSendPort HttpsSendPort HttpsSSLKeyRingFile
HttpsSSLTimeout
InRangeConnFailedRetryTimeout
KeepAliveInterval
Mod NetworkAverageBPS
NetworkMTU
30
Table 4. Parameters that affect only RAS/PPP interfaces (continued) Parameter name PktCompressThreshold Description When compression is enabled and this parameter is nonzero, the Mobility Client uses this value to determine the size of the smallest packet (in bytes) that it should attempt to compress. Very small packets often cannot be compressed. This parameter can be used to prevent wasting valuable CPU cycles attempting it. The default value is 50. The time specified in seconds used by the link layer to terminate a connection if the Connection Manager does not respond to a request sent by the Mobility Client. The default value is 20. When RequestTransportProfile=1, this entry is ignored. PreferredAdapter RasPhoneBookEntry ProxyUsername Specifies the network adapter that is used for roaming, if it is available. There is no default value. Specifies the name of the PPP daemon script to use to connect to the PPP server. PPP daemon scripts reside in /etc/ppp/peers. When a connection is established using a proxy server the Mobility Client must supply credentials for the proxy server to authenticate. This field is the user name. Release number of the configuration file. Specifies the number of seconds that the Mobility Client connection to a network has been in Active status and acts as a threshold value for determining which Wait interval to use when roaming from this connection to a lower priority network, if the status changes to Out of range or Unavailable. This setting helps determine if you are moving into or out of the coverage area of a network. If you are moving into coverage area, you may want to delay roaming from the network quickly because there could be a period of time when the status flips back and forth between active and inactive. This delay gives the network a chance to stabilize and establish the actual status. However, if you are moving out of a coverage area, as indicated that the network status has been active for a given period of time and then becomes inactive, then you may want to roam from that network more quickly. The default value is 0. RoamFromWaitOverThreshold Specifies the number of seconds that the Mobility Client waits before roaming from this connection to another Available network of a lower priority. When the network status has been Active for less than the amount of time specified in the RoamFromThreshold setting, then the connection may be in the periphery of a network coverage area and may need additional time to establish its actual status. This setting determines the number of seconds the Mobility Client waits until it will roam from this network to another of lower priority. The value of this setting should be more than the value of the RoamFromWaitUnderThreshold setting. The default value is 0.
PktTimeout
Release RoamFromThreshold
31
Table 4. Parameters that affect only RAS/PPP interfaces (continued) Parameter name RoamFromWaitUnderThreshold Description Specifies the number of seconds that the Mobility Client waits before roaming from this connection to another Available network of a lower priority. When the network status has been Active for more than the amount of time specified in the RoamFromThreshold setting and then becomes Unavailable, this setting determines the number of seconds the Mobility Client waits until it will roam from this network to another of lower priority. The value of this setting should be less than the value of the RoamFromWaitOverThreshold setting. The default value is 0. RoamSuspendInactive When an interface supports suspend/resume (short-hold mode), this value determines whether or not to suspend the connection when it is not the active interface. A value of 0 = do not suspend, and a value of 1 = suspend. The default value is 1. Specifies the number of seconds that the Mobility Client waits after the network is available before the Mobility Client will roam to it and make it the Active connection. If the connection is being established on the periphery of a network coverage area, this setting allows a period of time for the Mobility Client to make sure that the connection status does not go Out of Range or Unavailable before it attempts to roam to it. The default value is 0. When a connection is established using a proxy server the Mobility Client must supply credentials for the proxy server to authenticate. When this boolean option is set to 1, the Mobility Client stores the password. The port used to send data to the Connection Manager. This parameter is used only for UDP connections. The default value is 8889. The amount of time, in seconds, that the connection should wait before entering short-hold mode. If there is no network traffic over the connection after the specified number of seconds has elapsed, the connection is placed in short-hold mode. A setting of 0 disables short-hold mode. Specifies the timeout used when establishing a UDP, HTTP, or HTTPS connection with the Connection Manager. This is the number of seconds to wait before the Mobility Client attempts to connect using another protocol. Specifies the protocols that can be supported on the Mobility Client. The value for this parameter can be one or more of the following, in a comma-separated list: Connectionless Use UDP as a protocol to connect to the Connection Manager. ConnectionOriented Use HTTP as a protocol to connect to the Connection Manager. ConnectionOrientedSecure Use HTTPS as a protocol to connect to the Connection Manager. TCPIP_Ports2Filter This entry can exist for a connection or for an interface. The interface section is checked first, and if no entry is found, then the connection section is used. List of TCP ports, separated by spaces, from which to filter packets. When RequestTransportProfile=1, this entry is ignored.
RoamToWait
SaveProxyPassword
SendPort short-hold-timeout
SocketConnectionTimeout
SupportedProtocols
32
Table 4. Parameters that affect only RAS/PPP interfaces (continued) Parameter name TcpOptEnable Description When this boolean option is set to 1, TCP optimization is enabled. The default value is 0. When RequestTransportProfile=1, this entry is ignored. TcpOptMaxBurst Maximum number of unacknowledged TCP packets transmitted. The optimization engine withholds packets to keep from overloading a directional channel of a wireless network. The range of values is 516, inclusive. The default value is 8. When RequestTransportProfile=1, this entry is ignored. TcpOptMaxWindowSize Maximum size of the TCP sliding window in bytes. The optimization engine adjusts the TCP window on-the-fly as a means of performing network latency-specific flow control. The range of values is 204865535, inclusive. A value of zero disables this function. The default value is 0. When RequestTransportProfile=1, this entry is ignored. TcpOptRetransmitTTL Length of time in milliseconds to suppress TCP retransmit packets. A value of zero disables TCP retransmit suppression. The default value is 1000. When RequestTransportProfile=1, this entry is ignored. TrayUpdateInterval Minimum time in seconds that the client will wait between sending eMsg_PacketReceived events or eMsg_PacketTransmitted events. A value less than or equal to 0 disables sending these events. The default value is 2. This entry can exist for a connection or for an interface. The interface section is checked first, and if no entry is found, then the connection section is used. List of UDP ports, separated by spaces, from which to filter packets. When RequestTransportProfile=1, this entry is ignored. UseBindPort Specifies whether the Mobility Client listens on a specific port number for data sent from the Connection Manager. This parameter is used only for UDP connections. This parameter is used to enable or disable proxy authentication on the Mobility Client for connection-oriented (HTTP or HTTPS) connections. The default value of 0 disables proxy authentication. If you enter 1 to enable proxy authentication, you must also provide the proxy server address and port number. Use the HttpProxyAddr parameter to specify the address and HttpProxyPort for the port number, as provided by the system administrator. This boolean parameter determines whether the UDP echo function for the Mobility Client and Connection Manager is used during the logon sequence when connecting over UDP. If UseUDPEcho=1, the UDP echo function uses a test packet to check whether the Mobility Client can reach the gateway and what the Maximum Transmission Unit (MTU) should be. If UseUDPEcho=0, then the UDP echo function is not used. This parameter is updated after each logon, based on whether the Connection Manager to which the Mobility Client is connected supports the function. For migrated connections, the default value is 0. For new connections, the default value is 0 if only the UDP protocol is enabled or 1 if http, https, or both are selected in addition to the UDP protocol. Version Version number of the configuration file.
UDPIP_Ports2Filter
UseHttpProxy
UseUDPEcho
33
34
Chapter 4. Getting online help

The following types of help are available with the Mobility Client: Help menu: from the help menu, select the following options: v Help topics provides overview information, information about fields for which you are expected to provide input, and step-by-step instructions to complete tasks. v About identifies the product version as well as copyright and trademark information.
Accessibility
Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully. Mobility Client for Linux v You can navigate the user interface by using the keyboard.
Navigating with the keyboard

By using accelerator keys and keyboard shortcuts, you can navigate through the Mobility Client to perform operations that can also be done through mouse actions. The Tab key can also be used to move from one field or element to another.
Accelerator keys
Accelerator keys are typically identified as an underlined letter on the user interface and are used to allow you to access an element on the interface from the keyboard. To trigger an accelerator key, press and hold the Alt key while pressing the underlined letter. Accelerator keys can be included on a number of elements in the user interface, such as menu choices, push buttons, and labels for entry fields. Using accelerator keys with menus: When you open a menu using the keyboard, it is not necessary to use the Alt key to trigger accelerator keys for the menu choices. For example, if you use Alt and C to open the Connection menu in the Mobility Client, you can simply enter T to activate the accelerator key for the Trace menu choice.
Keyboard shortcuts
Keyboard shortcuts are used to trigger an action directly. Keyboard shortcuts are useful for actions that are performed frequently.
35
36
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 105041785 USA For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
37
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation P.O. Box 12195 3039 Cornwallis Road Research Triangle Park, NC 27709-2195 USA Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBMs application programming interfaces. If you are viewing this information softcopy, the photographs and color illustrations may not appear. The software included herein contains PPP Magic Number routines licensed by Carnegie Mellon University.
38
The software included herein contains derivatives of the RSA Data Security, Inc. MD5 Message-Digest Algorithm. This technology is licensed from RSA Data Security, Inc. SNMP++ Toolkit aided in the development of the Connection Manager's Network Management Support. SNMP++ Toolkit is copyright 1999 Hewlett-Packard Company.
Trademarks
The following terms are trademarks or registered trademarks of the IBM Corporation in the United States or other countries or both:
IBM Lotus
The following terms are trademarks of other companies: Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
Notices
39
40
Index A
accelerator keys 35 accessibility 35 adapters, switching 10 applications check for before connecting 5 starting after connection 6 applying maintenance 2 automatically starting applications after connecting 6
E
export configuration 7
F
fixes, applying code maintenance 2
G
getting online help 35
C
changing your password 5 checking that applications are running before connecting 5 client roaming 10 client services 15 code applying maintenance 2 commands importing configuration file using 8 starting the Mobility Client using 2 configuration importing and exporting 7 configuring using configuration files 15 connection automatically starting applications after 6 checking that applications are running before establishing 5 creating 5 defining Mobility Client 5 deleting 13 establishing to Connection Manager 5 parameters 15 starting when the operating system starts 6 suspending and resuming Mobility Client 12 switching 10 viewing properties 12 viewing status 11 Connection Manager disconnecting from 13 establishing a connection to 5 creating a connection 5
H
help, online 35
I
icon, for starting connection when the operating system starts 6 import configuration 7 installing 1 logging 1 interface using Mobility Client 5 IP-based client roaming 10
Mobility Client (continued) disconnecting from the Connection Manager 13 disk space requirements 1 getting online help 35 hardware requirements 1 installing hardware requirements for 1 software requirements for 1 logging 8 removing 3 software requirements 1 starting a trace 8 starting logging 8 starting the interface 2 suspending and resuming communication 12 tracing 8 uninstalling 3 using 5 viewing connection properties 12 viewing connection status 11
N
navigating the Mobility Client interface 2, 5 with the keyboard 35 network adapters, switching 10 networks, roaming between 10 notices 37
K
keyboard access 35
L
legal notices 37 level applying maintenance 2 Linux Mobility Client disk space requirements 1 Mobility Client hardware and software requirements 1 supported distributions 1 uninstalling the Mobility Client using the Mobility Client 5 logging 8 installation 1
O
online help 35 operating system , starting a connection at startup 6
P
3 parameters that affect client services 16 parameters that affect each connection 19 parameters that affect only IP-LAN interfaces 23 parameters that affect only RAS/PPP (remote access services/point-to-point protocol) interfaces 28 password changing Mobility Client 5 persistent client connection, configuring 6 properties Mobility Client connection, viewing 12
M D
defining a Mobility Client connection deleting a connection 13 disability 35 disconnecting from the Connection Manager 13 disk space requirements 1 distributions, supported Linux 1 5 maintenance, applying 2 mobile access services 1 Mobility Client connecting to the Connection Manager 5 connection properties 12 connection status, viewing 11 deleting a connection 13
R
removing the Mobility Client 3
41
requirements disk space 1 hardware and software resume 12 roaming 10
S
service marks 39 starting connection when the operating system starts 6 logging 8 the Mobility Client 2 tracing 8 using the command line 2 status viewing connection 11 supported Linux distributions 1 suspend 12 switching connections 10
T
tracing 8 trademarks 39
U
uninstalling the Mobility Client upgrading code and applying maintenance 2 using the Mobility Client 5 3
V
version applying maintenance 2
42
Printed in USA

Wclinux

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Wclinux

Uploaded by

Copyright:

Available Formats

Lotus Mobility Client for Linux

Lotus Mobility Client for Linux

Chapter 1. Getting started . . . . . . . 1

Chapter 2. Using the Mobility Client . . . 5

IBM Lotus Mobility Client for Linux: Users Guide

About the Mobility Client guide for Linux

Whats new in this release

IBM Lotus Mobility Client for Linux: Users Guide

Chapter 1. Getting started

Software and hardware requirements

Installing the Mobility Client

5. Enter ./install_wc to start the installation.

Starting the Mobility Client

IBM Lotus Mobility Client for Linux: Users Guide

Removing the Mobility Client

Chapter 1. Getting started

IBM Lotus Mobility Client for Linux: Users Guide

Chapter 2. Using the Mobility Client

Creating a Mobility Client connection

Connecting to the Connection Manager

Changing your password

Checking that applications are running before connecting

Starting a connection when the operating system starts

Automatically starting applications after connecting

IBM Lotus Mobility Client for Linux: Users Guide

Exporting and importing configuration files

Chapter 2. Using the Mobility Client

Using the command line to import and export configuration files

Using the trace viewer

IBM Lotus Mobility Client for Linux: Users Guide

Configure trace properties

Messages logged by the port subsystem (for example, UDP or TCP)

Roaming between networks

IBM Lotus Mobility Client for Linux: Users Guide

Specifying the network adapter to use

Viewing connection status

Chapter 2. Using the Mobility Client

Manually suspending and resuming communications

Viewing connection properties

IBM Lotus Mobility Client for Linux: Users Guide

Disconnecting from the Connection Manager

Changing font size and style

Chapter 2. Using the Mobility Client

IBM Lotus Mobility Client for Linux: Users Guide

Chapter 3. Configuring clients with configuration files

Table 1. Parameters that affect client services Parameter name Description

EnableDomain EnablePassword EnableSavePassword Group

IBM Lotus Mobility Client for Linux: Users Guide

Chapter 3. Configuring clients with configuration files

IBM Lotus Mobility Client for Linux: Users Guide

Chapter 3. Configuring clients with configuration files

0 No encryption The default value is 14.

IBM Lotus Mobility Client for Linux: Users Guide

MobileAddress Mod OneButtonConnect

Chapter 3. Configuring clients with configuration files

PrereqAppProcess1 ... PrereqAppProcess16

PrerequisiteDisabled PrimaryDNS RadiusRetryAttempts RadiusTimeout Release RequestTransportProfile

Routes SavePassword SecondaryDNS SetDefaultRoute

IBM Lotus Mobility Client for Linux: Users Guide

HttpSendPort HttpsSendPort HttpsSSLKeyRingFile

IBM Lotus Mobility Client for Linux: Users Guide

Chapter 3. Configuring clients with configuration files