I have setup the Anyconnect client for our wireless network. Most of the employees would also use the Anyconnect client for home or travel use as well. I would have a different profile for that connection since the VPN IP address would be different:
10.x.x.x Inside Wireless (no internal network traffic allowed without VPN)
60.x.x.x Public IP on the ASA 5515x for VPN connectivity
I am looking for a way for the client to choose the appropriate VPN profile by the ip address and network that the user is part of currently. I have looked at the autoconnect feature, but I have to do that by DNS name or ip for trusted versus untrusted. Unfortunately the DNS name/ip that we use on the wireless is openDNS. So if anyone at home used that same DNS then the profile would try to connect to the wireless side for the VPN.
Cisco Privacy Survey highlights the emergence of “Privacy Active” consumers. People care about privacy, but to what extent does it guide their consumer behavior and their actions to protect their personal information? In our new Cisco Customer Privac...
Threat Response integrates with Cisco Email Security in one of two ways: Directly from the ESA, or via an SMA. Each has its own module, but either will bring email visibility into your investigations performed in Threat Response.
Via an SMA:
Earlier this year, we released Cisco Identity Services Engine (ISE) 2.6. It delivered a broad new set of features and greater scale - a big stride for both better NAC services that ISE delivers and better Software-Defined Access. Today, we’re thril...
Integrating Cisco Identity Services Engine with Cisco Meraki Systems Manager
Technical Marketing Engineer, Cisco Systems, Inc.
Cisco Meraki Systems Manager is a cloud base endpoint management solu...
Existing customers may download the Cisco Identity Services Engine (ISE) 2.7 which was released on November 18, 2019. For 90-day evaluations of ISE, please see How to Get ISE Evaluation Software & Licenses.