We have 2 branch offices using SOHO boxes (and will be adding more shortly) to connect to our FBII at head office. All are on ADSL connections. The BOVPN connection works fine on one of the SOHOs, but the other one does not. The problem is that these SOHOs are configured exactly the same apart from internal and external IP addresses which makes it hard to pin down what is causing the problem.
At head office, we are using a BT 5861 ADSL router which I have heard have problems passing through multiple IPSec tunnels, is this true? Could this be our problem?
The errors in the logs at the SOHO end say:
2003-10-16-12:46:56 MONITOR rekey caused by packet from 187.155.12.6 port 1065 to 187.150.10.5 port 23 (TCP)
2003-10-16-12:46:56 MONITOR remote gateway (62.49.73.82) dead - force rekey
I tried changing the networking.ipsec.deadtunnel.check value as suggested on the Watchguard forum but that made no difference. This error does vanish with a constant ping through the tunnel so the Keep Alive on the SOHO is obviously not working!
And also:
2003-10-16-12:23:02 MONITOR Quick Mode processing failed
2003-10-16-12:23:02 MONITOR get_ipsec_pref: Unable to find channel info for remote(62.49.73.82)
2003-10-16-12:23:02 MONITOR ACTION - Verify VPN IPSec Policies for 62.49.73.82
2003-10-16-12:23:02 MONITOR WARNING - No Matching IPSec Policy found for 62.49.73.82
The FBII logs say the the peer won't accept the routing policy. The tunnel seems to work but not reliably and consistantly.
Can anyone tell me how to solve this problem? I've seen similar problems posted elsewhere but not really any solutions.
Thanks for any advice.
At head office, we are using a BT 5861 ADSL router which I have heard have problems passing through multiple IPSec tunnels, is this true? Could this be our problem?
The errors in the logs at the SOHO end say:
2003-10-16-12:46:56 MONITOR rekey caused by packet from 187.155.12.6 port 1065 to 187.150.10.5 port 23 (TCP)
2003-10-16-12:46:56 MONITOR remote gateway (62.49.73.82) dead - force rekey
I tried changing the networking.ipsec.deadtunnel.check value as suggested on the Watchguard forum but that made no difference. This error does vanish with a constant ping through the tunnel so the Keep Alive on the SOHO is obviously not working!
And also:
2003-10-16-12:23:02 MONITOR Quick Mode processing failed
2003-10-16-12:23:02 MONITOR get_ipsec_pref: Unable to find channel info for remote(62.49.73.82)
2003-10-16-12:23:02 MONITOR ACTION - Verify VPN IPSec Policies for 62.49.73.82
2003-10-16-12:23:02 MONITOR WARNING - No Matching IPSec Policy found for 62.49.73.82
The FBII logs say the the peer won't accept the routing policy. The tunnel seems to work but not reliably and consistantly.
Can anyone tell me how to solve this problem? I've seen similar problems posted elsewhere but not really any solutions.
Thanks for any advice.