Cisco Anyconnect Vpn Client For Mac Os



Setting up the Cisco VPN client. Download the Cicso VPN client for macOS from our Self Registration page. Launch the downloaded installer file and click through the screens to complete the installation. Go to your Applications folder and open the Cisco folder. Double-click on the Cisco AnyConnect Secure Mobility Client. The Cisco AnyConnect program will now be visible in FinderApplicationsCisco. If needed, the supporting files for the package will be located in Macintosh HDoptciscovpnprofile. Information on advanced instructions for Cisco AnyConnect VPN troubleshooting can be found in the Advanced Instructions for AnyConnect for VPN for Mac OS X.

Yosemite 10.10 & Cisco AnyConnect Secure Mobility Client version 3.1.07021 System Prompt whenever AnyConnect launches to connect to vpn: 'OS X wants to make changes. Type an administrator's name and password to allow this. OS X wants to use the 'System' keychain.' If I enter credentials and pre.

Confirmed working on OS X High Sierra

The proprietary CiscoVPN Mac client is somewhat buggy. It is possible to use the IPSec VPN software included with Mac OS X instead. This tutorial shows you how to migrate from CiscoVPNto the native OS X IPSec VPN by decrypting passwords saved in CiscoVPN PCF files.

Please visit these guys if their offer interests you - they make this site possible.

Open up your System Prefrences and select 'Network'. Click on the little + button at the bottom of the window to create a new connection.

Pick 'VPN' for the Interface and set its type to 'Cisco IPSec'. It doesn't matter what you set as the service name.

Copy the 'Host' setting from CiscoVPN...

to the 'Server Address' setting in your System Prefrences' and enter your username under 'Account Name'. You probably don't want to enter your passwordunless you are OK with the system saving it.

On Mac OS X, PCF files are usually found in /private/etc/CiscoSystemsVPNClient/Profiles. Open up /Applications/Terminal and type the following:

You should get something like this:

Find that long list of letters and numbers after enc_GroupPwd= and copy it. Also make note of the GroupName - you'll need that in a bit as well.

Paste that sequence of characters into the fancy schmancy decoder ring below and click 'Decode'. (pops up a new window)

Fancy Schmancy Decoder Ring

As an example, this should return 'letmein' as the password:

Thanks to HAL-9000 at evilscientists.de and Massar's work on cisco-decrypt.c for the magic here. A JavaScript implementation also exists here: https://github.com/artemkin/cisco-password-decoder.

Click 'Authentication Settings' back in the Network Prefrences screen. Enter the resulting decoded password into the 'Shared Secret' section of the new VPN connection and set the GroupName from above as well.

Click 'OK', make sure 'Show VPN status in menu bar' is checked and click 'Apply'.

At the top of your screen you should have a little VPN icon. Try connecting to your new VPN.

If everything goes as planned, you should see your connection time counting up at the top of your screen.

How to get your VPN settings out of the built-in mac VPN client.

You don't need the Fancy Schmancy Decoder Ring to get your settings back out of the built-inMac VPN client. Just head over to the Keychain Access application (under Applications -> Utilities) and search for 'VPN'. Double-click your IPSec Shared Secret to open up the window. Clicking 'Show Password' will reveal the secret sauce after you authenticate.


If things seem to get hung-up and you are unable to reconnect your VPN without a reboot, Rick R mentions that you might try killing the 'racoon' process.

Racoon is an IPsec key management daemon and is part of the KAME IPsec tools. Kill it by running 'Activity Monitor' in the 'Utilities' folder, finding it in the process list and clicking 'Quit Process' at the upper left of the Activity Monitor window.

Look in your system.log by running the Console app for hints at what might be going wrong. Here's the system.log from aworking VPN setup / take down.

Disconnects

Dave Ma's VPN would disconnect after 45 minutes of uptime. Fotos Georgiadis on an Apple forum threadsuggested changing the IPSec proposal lifetime within racoon to 24 hours instead of 3600 seconds.(3600 seconds is 1 hour - who knows why people are seeing drops at 45 minutes)Here's how that is done.

  1. Connect to the VPN (so OSX dynamically generates a racoon configuration file)

  2. Open Terminal on Mac (Applications --> Utilities--> Terminal)

  3. Copy the generated configuration file to /etc/racoon:

    sudo cp /var/run/racoon/XXXXXX.conf /etc/racoon

    **where: XXXXXX is the name or ip address of your VPN server**

  4. Edit the racoon configuration file with your favorite editor (pico):

    sudo pico /etc/racoon/racoon.conf

  5. At the bottom of the racoon.conf file, comment out the line:

    # include '/var/run/racoon/*.conf';

    (by added the '#' to the beginning of the line)

  6. And instead include the copied file (which we will edit):

    include '/etc/racoon/XXXXXX.conf';

    (don't forget to replace XXXXXX with the actual name of your file)

  7. Edit the generated configuration file with your favorite editor (pico):

    sudo pico /etc/racoon/XXXXXX.conf

  8. Disable dead peer detection:

    dpd_delay 0;

  9. Change proposal check to claim from obey:

    proposal_check claim;

  10. Change the proposed lifetime in each proposal (24 hours instead of 3600 seconds):

    lifetime time 24 hours;

    *note: make sure you change all the 'proposed lifetime' sections and not just one.

  11. Disconnect and reconnect (this time racoon will use your custom configuration).

Now try using your VPN for more than 45 minutes and it shouldn't drop.

So does all your traffic flow through the VPN when you are connected or just traffic to the protected networks? Cisco VPN servers normally send out a list of routes to private networks so you don't end up sending all of your traffic through the VPN server. The reasoning behind this is why protect it if the traffic is destined for an insecure network anyway? The native OS X Cisco VPN adds these routes automatically and removes them when you disconnect. That's one of the things that differentiates the Cisco VPN client from the standard IPSec client. Let's take a look at what gateway is used when sending traffic to apple.com from within the Terminal application:

Notice the 'gateway' line there? Traffic to apple.com is going out 192.168.1.1 which is my normal Internet gatewayso it is skipping the VPN entirely.

Let's try an IP on a protected private network: (10.1.2.3)

In this case, the gateway is 172.131.25.12 which is a fake IP on the far end of the VPN which will eventually route traffic to 10.1.2.3. So when sending data to 10.1.2.3, I am going through the VPN and that traffic is encrypted.

So how does it know what gateway to use for different IPs? Let's take a look at the routing table:

I've lopped off a bunch of irrelevant lines but as you can see we have two 'default' routes. If a destination isn'texplicitly matched below, the traffic will flow through the first default route from the top. So in this case, ifthe destination isn't within 10.1/16 (which means 10.1.*.*) we will go through our default route of 192.168.1.1. Ifit is, we would go through 172.131.25.12 which is our VPN.

But what if you just wanted to send everything through your VPN connection? We could just delete the first default route and let everything go over the VPN, but this is presumably dangerous because the encrypted traffic probably uses the default route to get to the VPN server in the first place. Let's see:

Yep, it does. So if we are going to remove the default route to 192.168.1.1, we have to make sure we have an explicitroute below to the VPN server. (1.2.3.4) You will notice above that my Cisco VPN server adds this route automatically, but if yours isn't configured that way you can add it like this:

It is safe to try this if you already have the route because the command will just fail.

The next thing we are going to do is a little dangerous and remove all your network access. A reboot should be your weapon of last resort to get your networking back but you might also want to print these instructions out so you havethem. You have been warned!

Now let's do the dangerous bit and rip the first default route away:

Now let's check to see if we can still get to our VPN server:

Yep, looks good.

Now let's look at the wider Internet by seeing how we get to apple.com: (17.172.224.47 - we aren't using apple.com here because we don't want to depend on DNS working)

Whoops, something is wrong! That's because that first route there is a little deceptive. It isn't aroute to the IP of the gateway, just a route to the VPN tunnel device utun0. We'll need to say what IPto go to. Let's add a default route to the VPN's fakenet gateway address: (which we already have as the gateway in most other routes)

OK, let's see which way packets go to get to apple.com: (17.172.224.47)

Yep, looks like the right way.

Now let's try pinging google.com: (apple.com doesn't respond to pings)

Looks like it works. If it doesn't work, your VPN server likely doesn't allow general Internet access throughVPN connections. If this is the case, you are out of luck. Hopefully you know someone influential in the ITdepartment that can change this for you.

Because we removed the normal default route, when we shut down our VPN we'll be stuck without a default route.To add that back in after the VPN goes down, do this:

And we should be back to normal.

Ideally we do these things automatically when the VPN comes up. The easiest way to do this is to have yourVPN administrator set that up as a policy for you. Alternatively, you can create scripts that run on VPN startup.Create /etc/ppp/ip-up and add whatever lines you came up with above to that and mark that file as executablewith:

Similarly, /etc/ppp/ip-down will be run on VPN shutdown. Reverse your commands in that file and you shouldhave a completely automated setup.

Happy tunneling!

-Anders Brownworth

About Me:


Name:Anders Brownworth
Home: Cambridge, MA, USA
Work: Mobile application and GSM research at Bandwidth.
Play: Technology, World Traveler and Helicopter Pilot
Follow:
Cisco AnyConnect Secure Mobility Client Supported Operating Systems and Requirements

Objective

The objective of this document is to show you the details about the supported operating systems (Windows, Linux, Mac) of the Cisco AnyConnect Secure Mobility Client and their requirements.

The Cisco AnyConnect Secure Mobility Client, also known as the Cisco AnyConnect VPN Client, is a software application for connecting to a Virtual Private Network (VPN) that works on various operating systems and hardware configurations. This software application makes it possible for remote resources of another network become accessible as if the user is directly connected to the network, but in a secure way. Cisco AnyConnect Secure Mobility Client provides an innovative way to protect mobile users on computer-based or smart-phone platforms, providing a more seamless, always-protected experience for end users, and comprehensive policy enforcement for an IT administrator.

For additional information on AnyConnect licensing on the RV340 series routers, see this article

Software Version

  • AnyConnect Secure Mobility Client 4.4 | (Download latest)

AnyConnect Supported Operating Systems and Requirements

AnyConnect Support for Microsoft Windows

Windows Operating Systems

  • Windows 7 Special Pack (SP) 1
  • Windows 8
  • Windows 8.1
  • Windows 10 x86 (32-bit) and x64 (64-bit)

Windows Requirements

  • Pentium class processor or greater
  • 100 MB hard disk space
  • Microsoft Installer version 3.1
  • Upgrading to Windows 8.1 from any previous Windows release requires you to uninstall AnyConnect, and reinstall it after your Windows upgrade is complete.
  • Upgrading from Windows XP to any later Windows release requires a clean install since the Cisco AnyConnect Virtual Adapter is not preserved during the upgrade. Manually uninstall AnyConnect, upgrade Windows, and then reinstall AnyConnect manually or via WebLaunch.
  • To start AnyConnect with WebLaunch, you must use the 32-bit version of Firefox 3.0+ and enable ActiveX or install Sun JRE 1.4+.
  • ASDM version 7.02 or higher is required when using Windows 8 or 8.1

AnyConnect Support for Linux

Linux Operating Systems

  • Linux Red Hat 6
  • Linux Red Hat 7
  • Ubuntu 12.04 Long Term Support (LTS)
  • Ubuntu 14.04 (LTS)
  • Ubuntu 16.04 (LTS) (64-bit only)
  • x86 instruction set
  • 64-bit processor
  • 32 MB Random Access Memory (RAM)
  • 20 MB hard disk space
  • Superuser privileges are required for installation
  • libstdc++ users must have libstdc++.so.6 (GLIBCXX_3.4) or higher, but below version 4
  • Java 5 (1.5) or later. The only version that works for web installation is Sun Java. You must install Sun Java and configure your browser to use that instead of the default package.
  • zlib — to support SSL deflate compression
  • xterm — only required if you're doing initial deployment of AnyConnect via Weblaunch from ASA clientless portal
  • gtk 2.0.0
  • gdk 2.0.0
  • libpango 1.0
  • iptables 1.2.7a or later
  • tun module supplied with kernel 2.4.21 or 2.6

AnyConnect (Versions 4.8 and above) Support for Mac OS X (Catalina)

Mac OS X Operating Systems

  • Mac OS X 10.15 ( Details from Apple | AnyConnect 4.8 Release Notes)

AnyConnect (Versions 4.7 and below) Support for Mac OS X

For

Mac OS X Operating Systems

Anyconnect Mac Client

  • Mac OS X 10.10
  • Mac OS X 10.11
  • Mac OS X 10.12
  • Mac OS X 10.13

Cisco Anyconnect Vpn Client For Mac Os X Yosemite

Mac OS X Requirements

  • AnyConnect requires 50 MB of hard disk space.
  • To operate correctly with Mac OS X, AnyConnect requires a minimum display resolution of 1024 by 640 pixels.