Skip to content

Questions: Traffic From Specific Source Not Taking Expected Path

  • What does the policy-based routing configuration (route-map) look like?
  • Is the route-map applied to the correct inbound interface (where 10.100.0.0/24 traffic enters)?
  • Does the route-map match clause correctly reference the ACL or prefix-list?
  • Does the referenced ACL/prefix-list actually match 10.100.0.0/24 source traffic?
  • What does show route-map output show for match/set hit counters?
  • Is the next-hop in the set clause reachable and in the routing table?
  • On Linux: what does ip rule list and ip route show table <N> show?
  • Is the policy applied in the correct direction (inbound on the LAN interface, not outbound)?
  • Are there any ACLs that could be overriding or conflicting with the route-map?
  • Does locally generated traffic from the router itself follow policy routing?