Cisco IOS policy route for router originated VPN traffic

Posted by Paul on Server Fault See other posts from Server Fault or by Paul
Published on 2013-10-21T06:02:42Z Indexed on 2013/10/30 3:58 UTC
Read the original article Hit count: 386

Filed under:
|

We have a Cisco IOS router with two DSL connections. One of them is intended for general traffic (ADSL), the other for VPN links (BDSL) and various other traffic.

So the default route is the ADSL link, and we have a combination of static routes for the VPN traffic, and policy routes for other traffic types that should go out the BDSL link.

For site to site traffic, this is fine, we just static route the public IPs and remote networks out of the BDSL line.

The policy based routing works fine for any internal traffic that matches an ACL.

The problem is now that there are remote VPN sites originating from dynamic addresses, so we cannot use static routes. The replies to incoming ISAKMP requests are following the default route out of the ADSL (despite there being no crypto map on that interface).

I want to route the outgoing VPN traffic out of the BDSL. I have tried adding udp/500 and esp to and from the route-map acl that pushes traffic out of the BDSL line, but it doesn't match, presumably because the route-map happen earlier than the IPSec stuff.

Any ideas how I can do this?

IOS ver: 12.4.13T.

© Server Fault or respective owner

Related posts about cisco

Related posts about policy-routing