I'm trying to route traffic to a router that is not directly connected using pbr. Here is my config:
Extended IP access list dsl-inet
deny ip any 192.168.0.0 0.0.255.255
deny ip any 10.50.0.0 0.0.255.255
deny ip any 10.51.0.0 0.0.255.255
permit ip 192.168.8.0 0.0.0.255 any
route-map dsl-inet, permit, sequence 10
ip address (access-lists): dsl-inet
ip next-hop 10.51.10.2
Policy routing matches: 0 packets, 0 bytes
I know that that the acl rule is working because i use it on some other switches. 10.51.10.2 is a router that is not directly connected to this switch but it can ping it. I have used this scenario with other setups but the next-hop has always been directly connected. Its seems i'm missing something here.
Re: pbr set next-hop to router not directly connected
If you next hop is not directly connected route then you need to have a route for your next hop ip address.
As you have defined 10.51.10.2 as your next hop does your router has a route to 10.51.10.2, you can check via "sh ip route 10.51.10.2" and if you do not have a route for that then you need to have a route to reach your next hop ip address so you can configure a static route where destination as 10.51.10.2 and next hop as directly connected route.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...