by Jeff Stern

(Note: There is also an alternative method of installing UCI VPN support without using the Cisco client, but using the built-in Debian/Ubuntu openconnect and openvpn drivers, should you find the below method does not work for you, or if you prefer to use open-source non-proprietary software.)

Introduction

Connect To VPN Server with Cisco AnyConnect from Linux Terminal. Follow the procedure to Connect, Disconnect and Automate VPN Connection from CLI on Ubuntu. Linux cisco VPN client ubuntu: The greatest for many people 2020 group A Linux cisco VPN client ubuntu is created away. A device that operates inside the provider's core fabric and does not directly interface to some customer endpoint. It power, for example, provide routing for many provider-operated tunnels that belong to different customers. The Cisco Meraki Client VPN option provides a L2TP/IPsec based VPN using either its own internal user store, an LDAP Directory, Microsoft Active Directory, or a Radius server to authenticate users. Cisco Meraki provide great instructions for Windows, Mac and mobile devices, but really old instructions for Linux.

OIT has a good general VPN-Linux page with instructions on setting up the Cisco AnyConnect VPN client software for Linux, but I got tripped up in a couple of places and thought I'd pass on some heads-ups for other Debian and Ubuntu users.

I originally wrote this 'How-To' for Ubuntu v10, and have updated it through v17.04. It should work for most or all Debian-derived distributions through 9.0 ('Stretch').

Please do write me to let me know how it went for you, and/or with any suggestions. I'd love to hear that it helped someone and/or any improvements that could be added.

Thanks to several for the help getting here.

Summary

In the instructions below, I'll walk you through installing the Cisco VPN client on a Debian or Ubuntu system. When you're done, you'll have two commands available at the command-prompt, which you can run to connect to the campus VPN: 'vpn' (text mode) and 'vpnui' (graphical/windowing).

I used to also include instructions for getting VPN support to show up in the NetworkManager icon/applet in the system tray, for those who used a Gnome based desktop. I no longer do this, as it is too complicated these days to keep up with documenting the various desktop environments, and the changes (and unreliability) of NetworkManager. And it's not really necessary anyway. If you get it going for yourself, though, Kudos to You! :-)

Installing the Cisco AnyConnect client

1. First, make sure you have the necessary Debian/Ubuntu support packages installed:
2. Go to the UCI OIT Cisco Anyconnect/Linux instruction page.
3. Download the 32 or 64 bit client as a .gz file.
• If you are usure whether you should use the 32 or 64 bit client: Most people are on 64-bit machines now. But if you are unsure, just run the uname command like this:As you can see from the above example, my machine has a 64-bit Intel (x86_64) based processor. If you see a '386' somewhere, then you are on a 32-bit machine.
4. From the command prompt, go to the directory you saved the file to, and unpack it and run, just like the OIT instructions. Note you might have to put in some back-slashes because the download file apparently comes with spaces in the file name these days:
5. If you get the following message at the end instead: it most likely means you did not install the two Ubuntu packages up in step 1, above.
   • However, if you have installed those two packages, and are still getting this error, then user Steve Murphy wrote me (2015-12-7) with the tip that running the following did install enough dependent packages as to make it work for him:However, while this may help some users, this normally should not be necessary, and was not in my testing.
     
6. Now reload systemd, scanning for new or changed units:
7. The vpn client should now have been installed on your system and the vpnagentd process started. You can verify this by looking at the active processes:
8. During the installation, the vpnagentd daemon should now be set up to be started each time your system is booted. To verify:or
9. Make command aliases to point to the vpn and vpnui commands:
10. Also add these aliases to the end of your ~/.bashrc or ~/.bash_aliases file:(where you don't actually type the '^D': it means you hit Ctrl-D to finish).
    If you want to edit your aliases file instead directly, you can run a simple editor, 'nano', which is usually available on Debian and Ubuntu systems:

Connecting and Disconnecting

Connecting (Graphical window)

And it should show 'vpn.uci.edu' already. Just click Connect.

If you get an error message about an untrusted server or certificate.

. Free creative writing software for mac. you can fix that following the instructions from Robert in the section NOTE 1 - Connect-error, below.

(By the way, depending on how the installation went, and whatever of the Linux desktop environments you are using (Gnome, Unity, KDE, Mate, Cinnamon, XFCE, etc.) you may also find that the vpnui graphical client now also appears somewhere in your Applications menu. But don't count on it! This is Linux, after all. :-) )

Connecting (via command-line)

1. To start the client from a command-line prompt in a terminal window, using the alias you made above:
2. At the VPN> prompt, type connect vpn.uci.edu and press Enter. (If you get an error message about an untrusted server or certificate, you can fix that following the instructions from Robert in the section NOTE 1 - Connect-error, below.) Otherwise, you should now see:If you do not see this, but get a connect error instead, please see NOTE 1 - Connect Error below.
3. Ignore the message about entering your UCInetID and password, for now.
4. Choose one of the choices by number and press return -- usually UCI or UCIFull. (See the differences in the Tunnels below.) For instance, for UCI, press 3 and hit Enter.
5. Enter your UCInetID and password in the Username and Password boxes and press return.
6. At the accept? [y/n]: prompt, type y and press Enter. You may get several notices the first time about the downloader performing update checks. At the end you should see a >> state: Connected message and a new VPN> prompt. You are now connected.
7. Either leave the VPN> prompt open or if you want your terminal back just type quit at the VPN> prompt (the connection will remain active).

Connecting automatically via Command-line (w/o typing in your Username/Password)

I never (not yet?) figured out how to get the Cisco anyconnect software to run via script with command-line parameters sufficient for its running without having to type in your username (UCINetID) and password. I looked into the vpn command / executable supplied by Cisco (in the anyconnect-predeploy package) and running -h on it does not give much help.

Therefore, if you need something command-line and automated, I suggest you use the alternative method using open-source openvpn/openconnect software which I mentioned at the very top of this document. I include a way to do that in an automated way, and I find it works just as well and just as fast, but without having to install proprietary Cisco software. (This is the age of Ed Snowden's warning to us all, after all. :-/

NOTE 1 - Connect-error

In most cases I have seen, a connection is made. I have, however, seen the below error before only once. It was when the person was installing on a netbook (running Gnome) which was on campus and usingthe campus wifi system (though I don't know if those factors were the cause). It didn't matter if they answered y or n, they continued to get the error and be denied connection.

Update 2015-12-6: 'Robert' wrote me with a solution to this:

• .the connect error.. can be resolved by sym-linking the cisco ca directory to the system ca directory as cisco only seems to include one root certificate by default. Or you can install the certificate chain from the VPN provider - sym-linking the system certs worked fine for me. Credit goes to: https://plus.google.com/+AndreasKotowicz/posts/2afhvvNZpE6

Thank you, Robert!

To disconnect (gui)

1. Just click disconnect in the window

To disconnect (command-line)

1. At the VPN> prompt, type disconnect and hit Enter.

To exit (command-line)

1. At the VPN> prompt, type quit and hit return.

De-installation / Removal

1. Run Cisco's provided un-install script
2. Optionally, also remove the cisco directory (if you don't need the .log files that were left behind):
   

Additional Hints, Tips, and Handling of Errors and Problems Contributed by Users

Several people have written in to me with some additional tips and solutions which I'll add here:

• From pierrechauffour:
• From zviad aburjania: This turned out to be a missing library fixable by:
• From zviad aburjania (2): (If that link no longer works, it is just recommended to start /opt/cisco/anyconnect/bin/vpnagentd first.)
  
• From pascal müller:

  Pascal researched and found that the error, anyconnect was not able to establish a connection to the specified secure gateway is a known problem with Cisco clients before version 4, when these earlier clients are installed on Ubuntu 16.04+. The solution is either to downgrade your Ubuntu, or upgrade your Cisco client. At my university we have upgraded to offering version 4 (anyconnect-predeploy-linux-64-4.3.05017-k9.tar.gz), and this supposedly works with the newer Ubuntus. I did not myself test the new version 4 Anyconnect client with Ubuntus 15.x and 16.x. But I have tested it today (April 27 2017) with my Ubuntu 17.04 system, and it works great.

Contact / Feedback

Please email me to let me know how this process went for you, and/or with any suggestions for improvement on this page itself. Thanks.

Acknowledgements

Thanks to:

1. Mike Iglesias and Sylvia Bass at UCI's OIT for for putting up the link to here from their VPN-Linux page.
2. a page at Georgia Tech (now defunct), from which part of this page (the old Section 2, no longer included) was originally adapted.
3. Joe Remenak for clear, concise feedback on some additional steps (1 and 11) necessary now for the newer 64-bit Ubuntus.
4. Tom Distler, for the Tux/Cisco image at the top of this page, which I mooched from his page, How to connect Linux to a Cisco VPN using a PCF file.
5. James Condie at UCI, who encountered multiple problems with the latest changes in the 4.3.05017 version of Cisco's install -- but patiently stuck with it -- thus encouraging me to update this page once again, and clarify a few additional things for newer Linux users.
6. Philippe Moisan, who caught and reported an incompatibility with the find vpnagentd command above in Installation Step 8, for some versions of Linux, and offered also a fix: to put quotes around the '*vpnagentd*' which should work with all flavors of find.

Last Updated Oct 30 2017

With my beloved, and worn, day to day laptop having to go in for repair, I had to setup a temporary laptop to work on for a few weeks.

At work we use Cisco Meraki devices in many places, including the edge of network for our various offices. Whilst their main use is to form a mesh network around our offices and server infrastructure, we also use them to enable a lightweight Client VPN solution.

The Cisco Meraki Client VPN option provides a L2TP/IPsec based VPN using either its own internal user store, an LDAP Directory, Microsoft Active Directory, or a Radius server to authenticate users.

Cisco Meraki provide great instructions for Windows, Mac and mobile devices, but really old instructions for Linux. Therefore, I am posting this as much to remind me the next time I need to set it up as to help others.

Cisco Vpn Client Ubuntu Download

By default, support for L2TP VPNs is not installed for Network Manager, so we need to install them:

Network Manager spawns and manages its own instance of xl2tpd so if there is a system instance still running it will not be able to use UDP port 1701, and will instead use an ephemeral port (i.e. random high port).

To stop this from happening, we need to stop the deamon and disabling it from starting again:

Now you are ready to add your VPN connection. Having taken the steps above, we’ve Gnome Network Manager settings panel now includes the option to add L2TP VPN connections:

The main settings we need to customise to work with Cisco Meraki Client VPN are on the Identity tab.

We can give our VPN a name, set the VPN gateway, and add our user credentials (with optional NT Domain depending whether Active Directory is used as the authentication scheme).

We now need to set our IPsec and PPP settings.

IPsec Settings

In the IPsec Settings we need to tick the Enable IPsec tunnel to L2TP host checkbox , expand the Advanced settings, and then add three things:

Cisco Vpn Client Download Windows 7

• Pre-shared Key - adding the key provided by your network administrator
• Phase1 Algorithm - use the following 3des-sha1-modp1024
• Phase2 Algorithm - use the following 3des-sha1

Click OK Diablo 3 free mac download. to set this on the connection.

PPP Settings

In the PPP Settings we need to make sure PPP is the only Authentication mechanism selected.

The other defaults should be OK, however I’ve included a screenshot to confirm against above.

Click OK to set this on the connection.

The VPN should now be available in the Gnome Settings panel:

and in the main Gnome Menu for quick connect/disconnect