bgpd: traffic rate value is ignored for searching bpa

There are cases where a redirect IP or redirect VRF stops the ecom
parsing, then ignores a subsequent rate value, letting passed value to
0. Consequently, a new table identifier may be elected, despite the
routing procedure is the same. This fix ignores the rate value in bpa
list.

Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>

diff --git a/bgpd/bgp_pbr.c b/bgpd/bgp_pbr.c
index 1f71d66629409344e42473a6a2fe1358bb76946e..3e3f15b989483491d1b6c22d6f067ae62ad07ce8 100644 (file)
--- a/bgpd/bgp_pbr.c
+++ b/bgpd/bgp_pbr.c
@@ -621,10 +621,8 @@ int bgp_pbr_action_hash_equal(const void *arg1, const void *arg2)
 
        /* unique value is self calculated
         * table and fwmark is self calculated
+        * rate is ignored
         */
-       if (r1->rate != r2->rate)
-               return 0;
-
        if (r1->vrf_id != r2->vrf_id)
                return 0;