Need assistance with Cradlepoint VPN routing
Hello Experts - I'm having some trouble with a disaster recovery site that is being tested. I'm using a Cradlepoint MBR 1400 (http://www.cradlepoint.com/products/branch-office-retail-pos/arc-mbr1400-series-with-integrated-3g-4g) which is configured with a VPN to my DR site. On the DR side is a Cisco ASA 5510. In addition to the DR VPN the 5510 is configured with two additional VPNs to another company which hosts on the DR side need to reach. I've been on the phone with Cisco and the problem appears to be that requests made from a host on the DR VPN to either of the other two VPNs are not making it across the tunnel. I have the network ranges I am trying to reach setup in the Cradlepoint VPN configuration under "Remote Networks" as seen in the attached screenshot.
Could anyone point me in the right direction? I must be missing something basic but haven't been able to figure it out on my own.
Could anyone point me in the right direction? I must be missing something basic but haven't been able to figure it out on my own.
ASKER
Hi Aaron
You have it exactly right. Computers at the DR site can talk to both remote sites. Basically I'm not seeing traffic destined for the remote sites making it across the VPN. I called Cradlepoint yesterday and explained the problem. The tech showed me the IP summary screen where there was a private 10.x.x.x address showing. He seemed to think that this was what is preventing the routing from working properly but that doesn't make much sense because the tunnel itself is up and I can reach hosts there, just not to the other remote VPNs.
You have it exactly right. Computers at the DR site can talk to both remote sites. Basically I'm not seeing traffic destined for the remote sites making it across the VPN. I called Cradlepoint yesterday and explained the problem. The tech showed me the IP summary screen where there was a private 10.x.x.x address showing. He seemed to think that this was what is preventing the routing from working properly but that doesn't make much sense because the tunnel itself is up and I can reach hosts there, just not to the other remote VPNs.
I'm at a loss. Either the cradlepoint isn't sending the traffic (like its a bug), or the cisco isn't allowing the traffic through (configuration).
Since both companies blame each other...
Since both companies blame each other...
ASKER
The plot thickens! I'm finding that its only public IP addresses that aren't being routed across the tunnel. As an example, one of the addresses I need to go across the tunnel is for a company called Ensenta. They require that we come from a specific IP address when accessing their administrative portal. So to do that I need the traffic to go across the tunnel then out to the internet so that Ensenta sees us coming from the correct address. No matter what I've tried this address refuses to route across the VPN and instead the Cradlepoint seems to just drop the traffic.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So the cradlepoint has a VPN to dr. Dr has a VPN to remote1 and remote2
When you are on the cradlepoint you can reach dr but not remote1 and remote2 correct?
What about the computers at dr, can they talk to remote1 or remote2?