FirePass controller, version 5.0 includes Network Access support for remote Macintosh® and Linux® clients, making FirePass controller a good option for secure remote access in mixed-platform environments. You do not need to preinstall or preconfigure any client software when using FirePass controller with Macintosh and Linux systems.
All the primary Network Access features are supported on Macintosh and Linux clients. For more information about Network Access and configuring Network Access features, see Chapter 3, Configuring Network Access.
Features supported on Macintosh and Linux clients include:
The FirePass controller, version 5.0 has been tested with the following Linux platforms:
The launch application feature specifies a client application that starts when the client begins a Network Access session. Use this feature when you have remote clients who will routinely use Network Access to connect to an application server like a mail server.
To configure the start of applications for Macintosh and Linux clients
Note: The group must already exist in order to configure Network Access for that group. For information on creating groups, see the online help for the Users : Group screen.
When remote users in the group make a Network Access connection, the application you configured starts automatically.
The first time a remote user starts Network Access, a client component is downloaded from the FirePass controller. This client component is designed to be self-installing and self-configuring, but the user's browser must be Java-enabled.
If the browser does not support Java, the user is asked to download an installation script from the controller.
The remote Linux user must have superuser authority, or must be able to supply an administrative password in order to successfully install the Network Access client.
Linux systems must also include PPP support (this is most often the case). When the user runs the Network Access client and makes a connection for the first time, the client detects the presence of pppd (the point-to-point daemon), and determines whether the user has the necessary permissions to run it. If pppd is not present, or if the user does not have permissions needed to run the daemon, the connection fails.