]> git.puffer.fish Git - mirror/frr.git/commit
lib: fix on-match when added to existing route-map entry 13993/head
authorAlexander Chernavin <achernavin@netgate.com>
Fri, 14 Oct 2022 09:02:06 +0000 (09:02 +0000)
committerAlexander Chernavin <achernavin@netgate.com>
Thu, 13 Jul 2023 08:40:36 +0000 (08:40 +0000)
commit633eb6ee7742449d0644dda7fd83865e3c01f937
tree33b7f74e8a9d8ea485c8edf315054620edadab5e
parent6934a1d31d832e423376c49a10646dd9f4336cd3
lib: fix on-match when added to existing route-map entry

Currently, "on-match (next|goto)" only works if already present in a
route-map entry when the route-map is applied to the routes. However, if
the command is added to an existing route-map entry, the route-map is
not reapplied to the routes in order to accommodate the changes. And
service restart is needed. The problem is that setting the command
doesn't signal about the change to the listener (i.e. to a routing
daemon).

With this fix, signal to the listener about addition of "on-match
(next|goto)" to a route-map entry.

Signed-off-by: Alexander Chernavin <achernavin@netgate.com>
lib/routemap_northbound.c
tests/topotests/bgp_route_map_on_match_next/__init__.py [new file with mode: 0644]
tests/topotests/bgp_route_map_on_match_next/r1/bgpd.conf [new file with mode: 0644]
tests/topotests/bgp_route_map_on_match_next/r1/zebra.conf [new file with mode: 0644]
tests/topotests/bgp_route_map_on_match_next/r2/bgpd.conf [new file with mode: 0644]
tests/topotests/bgp_route_map_on_match_next/r2/zebra.conf [new file with mode: 0644]
tests/topotests/bgp_route_map_on_match_next/test_bgp_route_map_on_match_next.py [new file with mode: 0644]