Hello,
I have several customers with RV series routers having a hard time establishing a gateway to gateway VPN to a central location. The problem I am having is with routing. So the logical setup looks like this.
Customer network <--> Local encryption domain <-> remote encryption domain <-> remote network
The customers network is 192.168.1.0/24
The customers encryption domain in 172.16.32.228/30
The remote encryption domain is 66.68.163.160/27
The remote network is 10.1.1.0/24
The tunnel is up (p1 and p2 complete) and the remote network is seeing encaps, but no decaps.
The local network (which has the RV325) appears to be configured correctly, however, the traffic destined for the remote network is leaving the WAN destined for 66.68.163.160/27 instead of being encapsulated and sent to the remote peer.
I thought this was a routing issue, and within the 'advanced routing' section of the RV325, I am having a hard time getting the traffic routed through the tunnel.
The advanced routing section calls for a destination IP, subnet mask, hop count, gateway, and interface.
I currently have the it set for 66.68.163.160, 255.255.255.224, 15, <remote peer>, and LAN, respectively.
With most other routers I would just make a policy based route, but I can not in this case.
How can I ensure that VPN traffic is going through the tunnel when the remote encryption domain is in public address space?
