Applies To:
Show Versions
BIG-IP APM
- 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
Overview: Installing and using BIG-IP Edge Client for Mac
The first time a remote user starts network access, the BIG-IP Access Policy Manager (APM) downloads a client component. This client component is designed to be self-installing and self-configuring, but the user's browser must have Java enabled on Macintosh systems. If the browser does not support this requirement, the BIG-IP APM prompts the user to download the controller client component from the controller and install it manually.
The Mac system 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 (Point-to-Point Protocol 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.
After installation, the Macintosh client must restart the browser before starting network access.
Task summary
About client installation on Macintosh systems
The BIG-IP Access Policy Manager (APM ) includes network access support for remote Mac OS X clients. You can use APM for secure remote access in mixed-platform environments. You do not need to preinstall or preconfigure any client software if the client allows installation of the required browser components.
The first time a remote user starts network access, the BIG-IP APM downloads a client component. This client component is designed to be self-installing and self-configuring, but the user's browser must have Java enabled on Macintosh systems. If the browser does not support this requirement, the BIG-IP APM prompts the user to download the controller client component from the controller and install it manually.
After installation, the Macintosh client must restart the browser before starting network access.
About establishing client connections from a Mac system
You can initiate connections through network access from Macintosh OS X, by connecting to the virtual server address using a supported browser, or by starting the BIG-IP Edge Client.
Configuring applications to start on a Mac OS client
Editing the log level in the configuration file for Mac OS
Supported network access features for Mac and Linux clients
BIG-IP Access Policy Manager supports all of the primary network access features on Macintosh and Linux clients, except for Drive Mappings and some client checks.
| Feature | Notes |
|---|---|
| Secure remote access to an internal network | Includes support for IP-based applications. |
| Split tunneling | Only network traffic that you specify goes through the network access connection. |
| IP address filtering with connection-based ACL | Allows you to restrict groups of users to specific addresses, ranges of addresses, and ports. |
| DNS Servers | |
| DNS Suffixes | |
| Allow local subnets | Includes forcing all traffic through the tunnel. |
| Application launching | You must configure the starting of remote client applications based on the operating system on the remote computers. You can configure all other features independent of the remote client operating systems. |
VPN component installation and log locations on Mac OS
On Macintosh operating systems, you install the VPN components and write VPN logs to the locations listed in the table.
| VPN component | Location |
|---|---|
| Network Access plugin | /Library/Internet Plugins/ |
| Endpoint Security (client checks) | ~/Library/Internet Plugins/ |
