- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
09-04-2013 12:06 PM
Currenly all routing must take place on our core network. (due to backup ipsec tunnels and faster MPLS circuts)
Here is what we want to do but I am not sure how to accomplish this.
We have four IPsec Tunnels that we do not want to be routed to each other without touching the core network first.
Our current setup has all four IPsec tunnels terminating on different tunnel interfaces but all on the same virtual router. (vr-ipsec)
Traffic destined for the core comes over the vr-ipsec and out eth10 for the core.
However traffic for a remote site comes down the same virtual router and back up the correct tunnel interface. Skipping the core all together.
What we want to do is terminate all the tunnels onto an interface facing the core.
Each tunnel interface will have its own IP address.
The core will know how to get to each remote site via the assigned IP on each tunnel.
I can draw pictures if needed.
Thanks
09-04-2013 03:38 PM
Hello,
Can you provide some network diagram?
Regards,
Hari Yadavalli
09-05-2013 02:17 AM
Hi,
Each tunnel should have his own zone. they can be part of the VR but they have to use default route which say defualt gateway is the core.
Remote1 -> tunnel1 -> zone1 in 10.1.1.0 - default gatway => core
Remote2 -> tunnel2 -> zone1 in 10.1.2.0 - default gatway => core
Hope help.
V.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!