We've been running the beta for a while, and recently updated to the 1.31 release. We have two firewalls (both running 1.31 now) that have an IPSec tunnel configured.
As long as the firewalls are up and running, the tunnel stays up, it's very reliable, and there are no problems.
The problem that we're having however, is that as soon as we reboot one of them, the tunnel won't come up automatically again. In our case, we have one firewall in our head office, and one in a remote office.
Yesterday, we had to reboot the firewall in our main office, after which the tunnel was down. I tried to disable/re-enable the tunnel in our main office, but without success (I did hit apply between making changes).
Once I got to the remote office, doing the same thing (disable/enable tunnel) immediately solved the problem.
Does anybody have an idea how this can be fixed? If it's a bug, then we'd be more than happy to send logs, try out things etc.. It's just been going on for a long time, and we'd really need to figure out how to solve this.
Thanks!
Truthfully, I reboot my IPsec linked m0n0wall machines all the time and never seen any issues where they didn't reconnect right away. Both sites have static IP or DNS names?