ERROR Installing Cisco AnyConnect On CentOS 6x

Home » CentOS » ERROR Installing Cisco AnyConnect On CentOS 6x
CentOS 5 Comments

Hi All;

I’ve downloaded the Cisco AnyConnect tar.gz file for one of our clients, when I untar it and then run the vpn_install script in the vpnclient directory I get the below error.

Thanks in advance for any help…

/
//# ./vpn_install//
//Cisco Systems VPN Client Version 4.8.02 (0030) Linux Installer//
//Copyright (C) 1998-2006 Cisco Systems, Inc. All Rights Reserved.//
//
//By installing this product you agree that you have read the//
//license.txt file (The VPN Client license) and will comply with//
//its terms.//
//
//
//Directory where binaries will be installed [/usr/local/bin]//
//
//Automatically start the VPN service at boot time [yes]//
//
//In order to build the VPN kernel module, you must have the//
//kernel headers for the version of the kernel you are running.//
//
//
//Directory containing linux kernel source code
[/lib/modules/2.6.32-573.7.1.el6.x86_64/build]//
//
//* Binaries will be installed in “/usr/local/bin”.//
//* Modules will be installed in
“/lib/modules/2.6.32-573.7.1.el6.x86_64/CiscoVPN”.//
//* The VPN service will be started AUTOMATICALLY at boot time.//
//* Kernel source from “/lib/modules/2.6.32-573.7.1.el6.x86_64/build”
will be used to build the module.//
//
//Is the above correct [y]//
//
//Making module//
//make -C /lib/modules/2.6.32-573.7.1.el6.x86_64/build SUBDIRS=/root/vpnclient modules//
//make[1]: Entering directory `/usr/src/kernels/2.6.32-573.7.1.el6.x86_64’//
//scripts/Makefile.build:49: *** CFLAGS was changed in
“/root/vpnclient/Makefile”. Fix it to use EXTRA_CFLAGS. Stop.//
//make[1]: *** [_module_/root/vpnclient] Error 2//
//make[1]: Leaving directory `/usr/src/kernels/2.6.32-573.7.1.el6.x86_64’//
//make: *** [default] Error 2//
//Failed to make module “cisco_ipsec.ko”.//
/

5 thoughts on - ERROR Installing Cisco AnyConnect On CentOS 6x

  • CS DBA wrote:
    So, there’s a bug in their makefiles. Cisco should be informed, if they don’t already know.

    And you can manually fix it….

    mark “yes, I do know C and make….”

  • You shouldn’t need to build Cisco’s client. Just install openconnect on your syustem and configure it for the https sites you want to connect to.

    You should need:
    NetworkManager-openconnect.x86_64
    openconnect.x86_64

    install those, right-click on the network manager icon in the upper panel, choose edit then choose add then choose “Cisco AnyConnect Compatible”
    fill in the necessary fields, and voila.

    to use it, just left-click the NM applet in the upper panel, choose
    “VPN Connections” then click the one you just configured. I use it for multiple sites and it works just fine.

  • I ended up getting the clients from the Nux repository instead of Epel. At the time, it provided the NetworkManager tools which EPEL didn’t have. It’s easy enough to run from the command line but NetworkManager integration is nice to have.

  • yeah, I actually got the NM part from nux, once I discovered he had it, after discovering that EPEL didn’t. I had already installed the client itself from EPEL, and the nux NM integration worked fine, so I just left it alone.

    But I think epel has since added the NM bit.

LEAVE A COMMENT