We just set up a VPN between two Pro3060s between our HQ and a remote office. Both sites are behind a Powerlink WAN aggregator which is recognized as a NAT/NAPT device by both devices (noted in the log). When we first set it up, everything worked fine but about 30 minutes later we couldn't communicate over the VPN. The lines were fine and both devices showed that the link was still up, but we could not communicate from HQ to the remote. If, however, we pinged HQ from the remote site over the VPN, it came up and worked fine for a while. What I've noticed today is that if the link sits idle for about 30 minutes, we can no longer use it from HQ to remote. Trying to connect from remote to HQ always works, though, and allows connections to go the other way again.
Does anyone have any idea what is going on here? The VPNs are defined with an IP address, not a domain name, on both ends. Our subnets do not overlap, but one is CIDR/24 (remote) and the other is CIDR/22 (HQ). Let me know if you need more info.
Does anyone have any idea what is going on here? The VPNs are defined with an IP address, not a domain name, on both ends. Our subnets do not overlap, but one is CIDR/24 (remote) and the other is CIDR/22 (HQ). Let me know if you need more info.
