Cannot get the cisco anyconnect to work with SUSE

 
Thread Tools Search this Thread
Operating Systems Linux SuSE Cannot get the cisco anyconnect to work with SUSE
# 1  
Old 07-29-2009
Cannot get the cisco anyconnect to work with SUSE

I am getting the following error when i try to connect to the vpn

Warning: The following Certificate received from the Server could not be verified:
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. IP Networking

How to stack Cisco 2960-S and Cisco 2960X?

Is there an easy way to stack Cisco 2960-S and Cisco 2960X switches? If you have no idea, follow this: 1. Stacking is not supported on switches running the LAN Lite image. All switches in the stack must be running the LAN Base image. 2. In a mixed stack of Catalyst 2960-X and Catalyst 2960-S... (0 Replies)
Discussion started by: Ayaerlee
0 Replies

2. Shell Programming and Scripting

Perl variables inside Net::Telnet::Cisco Module doesn't work

I am writing perl script to configure Cisco device but Variables inside Net::Telnet::Cisco Module doesn't work and passed to device without resolving. Please advise. here is a sample of script: use Net::Telnet::Cisco; $device = "10.14.199.1"; ($o1, $o2, $o3, $o4) = split(/\./,$device);... (5 Replies)
Discussion started by: ahmed_zaher
5 Replies

3. Red Hat

cisco anyconnect VPN client installation??

Anyone had installed Cisco AnyConnect VPN client on RedHat5.3 EL or CentOS 5.3? I tried on CentOS 5.3 but always getting host unreachable error. Same for windows xp works fine. The error log reports: Sep 1 19:14:03 localhost vpnagent: Function: tableCallbackHandler File: RouteMgr.cpp Line:... (3 Replies)
Discussion started by: zing_foru
3 Replies
Login or Register to Ask a Question
GNUNET-VPN(1)						      General Commands Manual						     GNUNET-VPN(1)

NAME
gnunet-vpn - manually setup a GNUnet VPN tunnel SYNOPSIS
gnunet-vpn [options] DESCRIPTION
gnunet-vpn can be used to manually setup a VPN tunnel via the GNUnet network. There are two main types of tunnels. Tunnels to an exit node which routes the traffic to the global Internet, and tunnels to a node that runs a service only within GNUnet. Depending on the type of tunnel, gnunet-vpn takes different options. The "-i" option is required for tunnels to an exit node, whereas the "-p" and "-s" options in conjunction with either "-u" or "-t" are required for tunnels to services. For exit tunnels, both UDP and TCP traffic will be redi- rected. For service tunnels, either UDP ("-u") or TCP ("-t") traffic will be redirected. The tool will display the IP address for this end of the tunnel. The address can be displayed as soon as it has been allocated, or only after ("-a") the tunnel has been created. OPTIONS
-4, --ipv4 Desired IP address on this end of the tunnel should be an IPv4 address. -6, --ipv6 Desired IP address on this end of the tunnel should be an IPv6 address. -a, --after-connect Display IP address only after the tunnel is fully connected. -c FILENAME, --config=FILENAME Use the configuration file FILENAME. -d SEC, --duration SEC The mapping should be established for SEC seconds. Default is 5 minutes. -h, --help Print short help on options. -i IP, --ip IP Tunnel should be to an exit node and connect to the given IPv4 or IPv6 IP address. Note that you can specify an IPv6 address as the target here, even in combination with "-4" (4to6) and similarly you can specify an IPv4 address in combination with "-6" (6to4). -L LOGLEVEL, --loglevel=LOGLEVEL Use LOGLEVEL for logging. Valid values are DEBUG, INFO, WARNING and ERROR. -p PEERID, --peer=PEERID Name of the peer offering the service to connect to. Cannot be used in conjunction with "-i", requires "-s". -s NAME, --service=NAME Name of the service running on the target peer. Cannot be used in conjunction with "-i", requires "-p". -t, --tcp Service runs TCP. Either "-t" or "-u" must be specified when using "-s". -u, --udp Service runs UDP. Either "-t" or "-u" must be specified when using "-s". -V, --verbose Be verbose. -v, --version Print GNUnet version number. BUGS
Report bugs by using Mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet-developers@gnu.org> SEE ALSO
gnunet-setup(1) GNUnet 25 Feb 2012 GNUNET-VPN(1)