Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fiffens]

I see the same as dbonetti.


LOG:

2010-05-31
19:04:53    Info    IPSEC
1800317          
   
   
   peer_is_dead
IPsec_tunnel_disabled
peer=192.168.1.3
2010-05-31
19:04:53    Info    IPSEC
1802708          
   
   
   ike_sa_destroyed
ike_sa_killed
ike_sa=" Initiator SPI ESP=0xd0ea4930, AH=0xb7a0dabd Responder SPI "
2010-05-31
19:04:53    Warning    IPSEC
1802022          
   
   
   ike_sa_failed
no_ike_sa
statusmsg="Timeout" local_peer="127.0.0.1 ID No Id" remote_peer="192.168.1.3 ID No Id" initiator_spi="ESP=0xd0ea4930, AH=0xb7a0dabd"
2010-05-31
19:04:53    Warning    IPSEC
1802715          
   
   
   event_on_ike_sa
side=Initiator msg="failed" int_severity=6

[fiffens]

Looks like I found a solution to my problem. Instead of having the dns address of the remote endpoint in the address book, I entered the dns address directly in the config of the IPSec tunnel. Seems like a bug to me.