If Pulse detects that it is connected to the corporate LAN and it already has a VPN connection, it disconnects that VPN connection. The second connection is a Pulse Connect Secure connection that resolves to TRUE when the endpoint is located in a remote location. The first connection is a Pulse Policy Secure connection that resolves to TRUE when the endpoint is connected to the corporate LAN. Each connection is configured to connect to only one target server. The following location awareness example includes two connections. Each location awareness rule is based on the endpoint’s ability to reach an IP address or resolve a DNS name over a specified network interface.
To set up the location awareness rules that select among many connections, you must define location awareness rules for each connection. If the conditions specified in the rules do not resolve to TRUE, Pulse tries the next connection. If the conditions specified in the rules resolve to TRUE, Pulse attempts to make the connection. Location awareness relies on rules you define for each Pulse connection. If Pulse detects that it is connected to the corporate LAN and it already has a VPN connection (for example, the VPN connection was suspended when the computer was put into hibernation), it first discovers that the VPN location awareness rules are no longer true, disconnects that VPN connection, and then evaluates the location awareness rules for the other configured connections. For example, you can define rules so that a Pulse client that is started in a remote location automatically establishes a VPN connection to Pulse Connect Secure, and then that same client automatically connects to Pulse Policy Secure when it is started in the corporate office. The location awareness feature enables a Pulse Secure client to recognize its location and then make the correct connection. You are here: Configuring Location Awareness Rules for Pulse Secure Client
0 kommentar(er)
