|
||||||||
From my experience the VPN is not automatically established if it hasnt been used before (ie a reboot of the mono etc). It will only re-establish itself once a VPN based subnet is required. I have watched my syslog output the IPSEC connection only just as I ping the remote subnet JK -----Original Message----- From: Roy [mailto:mobicult at gmail dot com] Sent: Thursday, 28 December 2006 12:45 AM To: m0n0wall at lists dot m0n0 dot ch Subject: [m0n0wall] m0n0wall <--> m0n0wall VPN doesn't autoconnect hope someone can help me with the following problem. I connected three sites A, B and C with an IPsec VPN. I searched the archives, but didn't find a solution. Site A (m0n0wall)and site B (d-link di-804hv) are auto-reconnected when the connection is down (option in d-link vpn router) and are working just fine. The problem is that the IPsec VPN between A (m0n0wall) and B (m0n0wall) doesn't come up automatically. After a ping from one of the m0n0wall's on the LAN interface to the other subnet(diagnostic menu; no response offcourse) the connection is up for some time and drops after a period of time (not the lifetime for phase 1/2...I think). B<--->WAN<--->A<--->WAN<--->C The subnets do not overlap! VPN settings m0n0wall: phase 1: - aggressive - blowfish - sha1 - DH-key 2 - lifetime 28800 phase 2: - ESP - blowfish - sha1 - PFS key 2 - lifetime 3600 |