Sponsored Content
Full Discussion: Openswan with Cisco ASA
Special Forums IP Networking Openswan with Cisco ASA Post 302924142 by ivancd on Thursday 6th of November 2014 01:12:35 PM
Old 11-06-2014
Openswan with Cisco ASA

Hi all,
I need this as soon as possible to solve it or at least to find out what is the problem.

I have configured IPSec tunnels with Openswan and Cisco ASA, i have established a connection and the ping was fine, but after some time there is request time out from both sites. I don't have ASA access but its default IPSec configuration,this is the openswan conf parameters.

Code:
#Define your IKE policy
            authby=secret
            keyingtries=0
            pfs=no
            ike=3des-sha1;modp1024
            ikelifetime="28800"
    
            dpddelay=0
            dpdtimeout=0
            dpdaction=clear
    
    #Define IPSec Policy
    
            phase2=esp
            phase2alg=3des-sha1
            ikev2=no
            keyexchange=ike
            rekey=no
            forceencaps=no
            keylife="28800"

I have found this in the "/var/log/seccure" logs
Code:
    received Delete SA(0x937bbc29) payload: deleting IPSEC State #5
    received and ignored informational message
    received Delete SA(0x55f62168) payload: deleting IPSEC State #8
    received and ignored informational message



Also i like to put some more logging/debuging so i can have more info but can't find any good example or doc. on how to.

And i have the following doc. on Phase 1 and 2

Code:
Encryption Algorithm     3DES
    Hash Algorithm           SHA1
    Authentication method    Preshare
    Diffie Hellman Group     Group 2
    Lifetime (Key)           28800
    Use NAT traversal        No
    Use PFS                  No
    Encapsulation            ESP
    Encryption Algorithm     3DES
    Hash Algorithm           SHA1
    Lifetime (Key)           28800


Any solution or hints or some parameters that I'm missing ?
Moderator's Comments:
Mod Comment Please use code tags next time for your code and data, not QUOTE Thanks
 

4 More Discussions You Might Find Interesting

1. IP Networking

How to establish site to site vpn - Linux machine and cisco asa?

Hi, I am trying to establish vpn between my linux server and cisco asa at client side. I installed openswan on my cent os. Linux Server eth0 - 182.2.29.10 Gateway - 182.2.29.1 eth1 - 192.9.200.75 I have simple IPtables Like WAN="eth0" LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies

2. 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

3. IP Networking

VPN IPSec Openswan

Hi all, I have installed Openswan and configured IPSec and works perfect, but for some unknown reasons it stop working. I see that the tunnels are up and established. The route to the destination are added. Everything by the book seems to be ok. But somehow when i start to ping the other side (... (4 Replies)
Discussion started by: ivancd
4 Replies

4. IP Networking

Cisco 3750 Switch ASA VPN Routing

Hi,I want connect my ASA 5510 firewall to a 3750 switch with RIP routing. Unfortunately,I am having issues passing the VPN subnet through rip to the 3750.I don't understand how the routing table is populated on the ASA. Any suggestions? (0 Replies)
Discussion started by: Ayaerlee
0 Replies
Net::CLI::Interact::Manual::Phrasebook(3pm)		User Contributed Perl Documentation	       Net::CLI::Interact::Manual::Phrasebook(3pm)

NAME
Net::CLI::Interact::Manual::Phrasebook - List of Supported CLIs INTRODUCTION
The bundled phrasebook includes support for a variety of network device CLIs. Many were contributed by users of the module. If you set up a new CLI dictionary, please consider contributing it back! The phrasebook specification is given in Net::CLI::Interact::Phrasebook. For each supported CLI, there is a name which must be passed in the "personality" option to Net::CLI::Interact's "new()" method. After that, you can call the included Macros, and the module will use the included Prompt to match the current state of the CLI. More information is available in the Tutorial and Cookbook. Below is a list of all current bundled CLI dictionaries. Each lists its name, the available Prompts, Macros and Continuations, and from which other CLI dictionaries it inherits. IOS # Cisco IOS CatOS # for older, pre-IOS Cisco devices PIXOS # for PIX OS-based devices PIXOS7 # Slightly different commands from other PIXOS versions FWSM # currently the same as 'PIXOS' FWSM3 # for FWSM Release 3.x devices (slightly different to FWSM 2.x) JunOS # Juniper JUNOS support HP # HP support Nortel # Nortel support ExtremeOS # Extreme Networks support Foundry # Foundry/Brocade device support PERSONALITIES
Cisco This personality goes by the name of "cisco" and provides a basis for many other CLI dictionaries. Prompts are "basic", "privileged", "configure", "user", and "pass". Macros are "begin_privileged", "end_privileged", "begin_configure", "end_configure", and "disconnect". CatOS This personality goes by the name of "catos" and inherits from the "cisco" dictionary. Additionally it provides the "privileged" Prompt. Additionally it also provides the "paging" Macro to set the terminal page size. ExtremeOS This personality goes by the name of "extremeos" and inherits from the "cisco" dictionary. Additional Prompts are "basic", "privileged", "configure", "user", and "pass". Additional Macros are "begin_privileged", "end_privileged", and "disconnect". Foundry / Brocade This personality goes by the name of "foundry" and inherits from the "cisco" dictionary. Before connecting to the device you probably want to set the output separator to be: $nci->transport->ors(" "); For users of Net::Appliance::Session this should be: $session_obj->nci->transport->ors(" "); IOS This personality goes by the name of "ios" and inherits from the "cisco" dictionary. Additionally it provides the "paging" Macro to set the terminal page size. HP This personality goes by the name of "hp" and inherits from the "cisco" dictionary. Additionally it provides the "basic" and "user" Prompts. JunOS This personality goes by the name of "junos" and inherits from the "cisco" dictionary. Additionally it provides the "privileged", "configure", and "user" Prompts. Additionally it also provides the "begin_configure" and "paging" Macros. Nortel This personality goes by the name of "nortel" and inherits from the "cisco" dictionary. Additionally it provides the "user" Prompt. PIXOS This personality goes by the name of "pixos" and inherits from the "cisco" dictionary. Additionally it provides the "paging" Macro to set the terminal page size. It can be used in its own right for Cisco PIX firewalls, but is also used as a base for other dictionaries. PIXOS 7 This personality goes by the name of "pixos7" and inherits from the "pixos" dictionary. Additionally it provides the "paging" Macro to set the terminal page size. FWSM This personality goes by the name of "fwsm" and inherits from the "pixos" dictionary. It provides no further functionality, as Cisco FWSM software version 1 and 2 was the same as the PIX OS. FWSM 3 This personality goes by the name of "fwsm3" and inherits from the "pixos" dictionary. Additionally it provides the "paging" Macro to set the terminal page size. perl v5.14.2 2012-06-12 Net::CLI::Interact::Manual::Phrasebook(3pm)
All times are GMT -4. The time now is 02:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy