Abstract: One embodiment provides selectively routing Domain Name System (DNS) request for sub-domains associated with a first network through a tunnel associated with the first network via the interface. DNS requests for sub-domains associated with a second network are selectively routed through a tunnel associated with the second network via the interface. Embodiments include replacing the destination address for DNS requests for sub-domains associated with the second network to match an address of a DNS server associated with the second network. Data representative of DNS requests for sub-domains associated with the second network is stored. Embodiments forward the DNS requests for sub-domains associated with the second network with the address of the DNS server associated with the second network.

Abstract: One embodiment provides selectively routing Domain Name System (DNS) request for sub-domains associated with a first network through a tunnel associated with the first network via the interface. DNS requests for sub-domains associated with a second network are selectively routed through a tunnel associated with the second network via the interface. Embodiments include replacing the destination address for DNS requests for sub-domains associated with the second network to match an address of a DNS server associated with the second network. Data representative of DNS requests for sub-domains associated with the second network is stored. Embodiments forward the DNS requests for sub-domains associated with the second network with the address of the DNS server associated with the second network.

Abstract: In an example embodiment, a method of dynamically tunneling specific, or per application, services on demand without having to build complex split tunneling policies on Virtual Private Network (VPN) terminators. In particular embodiments, the method can allow for tunneling to multiple data centers on devices with limited, e.g., single, concentrator capabilities.

Abstract: Described in an example embodiment herein is a Multiple Application Container. Various embodiments of the Multiple Application Container may include, but are not limited to: (1) managed intranet access via a dedicated Virtual Private Network (VPN) tunnel shared amongst applications within the container, (2) managed file/data encryption, (3) native look and feel applications for the base Operating System (OS), (4) isolation from any non-OS based services on the device, and/or (5) Mobile Device Management (MDM) based capabilities, such as policy enforcement.

Abstract: In an example embodiment, a method of dynamically tunneling specific, or per application, services on demand without having to build complex split tunneling policies on Virtual Private Network (VPN) terminators. In particular embodiments, the method can allow for tunneling to multiple data centers on devices with limited, e.g., single, concentrator capabilities.

Abstract: Described in an example embodiment herein is a Multiple Application Container. Various embodiments of the Multiple Application Container may include, but are not limited to: (1) managed intranet access via a dedicated Virtual Private Network (VPN) tunnel shared amongst applications within the container, (2) managed file/data encryption, (3) native look and feel applications for the base Operating System (OS), (4) isolation from any non-OS based services on the device, and/or (5) Mobile Device Management (MDM) based capabilities, such as policy enforcement.

Abstract: In a virtual private network, a plurality of concentrators form an interface to provide client/remote site access to a private network over a public network. The plurality of concentrators are grouped into a virtual cluster. Each concentrator in the virtual cluster has an IP address and the virtual cluster has a virtual IP address. In operation, one of the plurality of concentrators assumes the virtual IP address and acts as the master device in the cluster. When a client attempts a connection to the private network, the client addresses an initial request to the virtual IP address. The master device responds to the client request by transmitting to the client the IP address of a concentrator in the cluster selected to handle the connection.

Abstract: A client device establishes a virtual private network connection with a central site or network through a master concentrator. The master concentrator transmits state information, relating to the virtual private network connection, to a backup concentrator. In the event the master concentrator fails during a communications session between the client device and the network, the backup concentrator maintains the communication session between the client device and the network over the virtual private network connection using the connection state information received from the master concentrator. Such a configuration allows for failover of a virtual private network connection from the master concentrator to the backup concentrator without requiring the client device to re-establish the virtual private network connection with the central site or network. The configuration also allows the client device to maintain an existing communications session with the network.