(Ubuntu) Cisco VPN 4.8


Recommended Posts

Followed these steps,

but after rebooting and firing it up i gt the following:

Cisco Systems VPN Client Version 4.8.00 (0490)
Copyright (C) 1998-2005 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Linux
Running on: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
Config file directory: /etc/opt/cisco-vpnclient

Could not attach to driver. Is kernel module loaded?
The application was unable to communicate with the VPN sub-system.

Link to comment
https://www.neowin.net/forum/topic/567688-ubuntu-cisco-vpn-48/
Share on other sites

Followed these steps,

but after rebooting and firing it up i gt the following:

Cisco Systems VPN Client Version 4.8.00 (0490)
Copyright (C) 1998-2005 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Linux
Running on: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
Config file directory: /etc/opt/cisco-vpnclient

Could not attach to driver. Is kernel module loaded?
The application was unable to communicate with the VPN sub-system.

Did you start the vpn service first? Here is a script I wrote for myself to login to vpn. Hope this works for you.

#!/bin/sh

dummy=`sudo echo`
currdir=`pwd`
cd /etc/CiscoSystemsVPNClient/Profiles/
sudo /etc/init.d/vpnclient_init start
sudo vpnclient connect vpn_profile_without_extension
cd $currdir
exit

ripgut, just copy and paste that script into your favourite text editor and save it somewhere. (I have a directory in my home called "scripts") Then in a terminal, "cd home/ripgut/scripts" (assuming your user name is ripgut and you placed it in scripts). Once you're in that directory just "sh filename" and it will run.

ripgut, just copy and paste that script into your favourite text editor and save it somewhere. (I have a directory in my home called "scripts") Then in a terminal, "cd home/ripgut/scripts" (assuming your user name is ripgut and you placed it in scripts). Once you're in that directory just "sh filename" and it will run.

Plus, you might want to create a symbolic link to the script and place it in /usr/bin so that you can invoke it without specifying the full path for the script. Or, add the "scripts" dir to your PATH env variable.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.