There is a known bug in the Watchguard firmware and so far we have not been able to find out why VPN Tracker is triggering this bug, as the Windows client seems to not trigger it. We talked with Watchguard, but even they could not tell us what we are doing wrong. Basically the tunnel dies internally in the Watchguard (it's still shown as open and established, but traffic arriving over this tunnel is rejected as if the tunnel was closed).
If you are using a Branch Office VPN at the moment, try switching to a MUVPN if possible. MUVPN works with VPN Tracker as well and usually yields for better results.
Please refer to the following description.
Your direct line to the equinux TARMAC team
Our TARMAC team is ready and waiting:
firstname.lastname@example.org or by Telephone +49 (0)89 / 520 465-222
You're interested in equinux products and have additional questions regarding your purchase or product activation?
The equinux Sales Team is here to help: Call or chat with us,
Cisco Small Busi ...
Kame (Free BSD, ...
Palo Alto Networ ...