Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 408 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[7.009] IPSec reconnect not working

SveN_01
Hi, 
I have a IPSec Connect to a LanCom Router. The Gateway type is "Initiate Connection". But if the LanCom Router drops the connection, my Asatro does not try to bring it up again. Can I configure the reconnection timeout somewhere or do I miss something?

cu SveN


This thread was automatically locked due to age.
Parents
  • 0
    Okay, here are some logs. As you can see the connection wents down after 44 Minutes (19:44:42) and is not comming up again.... 
    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: initiating Main Mode

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [RFC 3947]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: ignoring Vendor ID payload [eeefa37809e32ad4de4f6b010c26a640]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [Dead Peer Detection]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: enabling possible NAT-traversal with method 3

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: NAT-Traversal: Result using RFC 3947: peer is NATed

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: Peer ID is ID_IPV4_ADDR: '*REMOTEIP*'

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: ISAKMP SA established

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #2: initiating Quick Mode PSK+ENCRYPT+TUNNEL+PFS+UP {using isakmp#1}

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #2: sent QI2, IPsec SA established {ESP=>0x5799f713 

    Anyone an idea?

    cu SveN
Reply
  • 0
    Okay, here are some logs. As you can see the connection wents down after 44 Minutes (19:44:42) and is not comming up again.... 
    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: initiating Main Mode

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [RFC 3947]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: ignoring Vendor ID payload [eeefa37809e32ad4de4f6b010c26a640]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: received Vendor ID payload [Dead Peer Detection]

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: enabling possible NAT-traversal with method 3

    2007:10:15-19:00:40 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: NAT-Traversal: Result using RFC 3947: peer is NATed

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: Peer ID is ID_IPV4_ADDR: '*REMOTEIP*'

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #1: ISAKMP SA established

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #2: initiating Quick Mode PSK+ENCRYPT+TUNNEL+PFS+UP {using isakmp#1}

    2007:10:15-19:00:41 (none) pluto[14166]: "S_REF_sDyFCaWtku_0" #2: sent QI2, IPsec SA established {ESP=>0x5799f713 

    Anyone an idea?

    cu SveN
Children
No Data
Cookie Information Banner