No way to use ipv4 address x.x.x.x as next-hop in the route-map
[email protected]# set policy route-map foo rule 10 match ip nexthop Possible completions: access-list IP access-list to match prefix-list IP prefix-list to match
What I expect, x.x.x.x as next hop
[email protected]# set policy route-map foo rule 10 match ip nexthop Possible completions: <x.x.x.x> next-hop ip address access-list IP access-list to match prefix-list IP prefix-list to match
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | FEATURE REQUEST | None | T2425 Rewrite all policy zebra filters to XML/Python style | ||
| Wontfix | BUG | Viacheslav | T3304 No way to use ipv4 address as next-hop in route-map |
Frr doesn't provide such option for ipv4, only for ipv6
r-roll01(config-route-map)# match ip next-hop (1-199) IP access-list number (1300-2699) IP access-list number (expanded range) WORD IP Access-list name prefix-len Match prefixlen of given nexthop prefix-list Match entries of prefix-lists type Match entries by type
ipv6
r-roll01(config-route-map)# match ipv next-hop X:X::X:X IPv6 address of next hop type Match entries by type