no soft bgp clear is triggered on modification to prefixlist / routemap
Hello, This issue has been discussed here : https://github.com/FRRouting/frr/issues/126 To sum up, when a route-map is modified (tried 2 things: adding a new entry and modifying prefix-list involved), no soft bgp clear is performed, so it looks like other peers never get new results (the "show advertised route" output is correct). Looks like "no route-map ... " and "route-map ..." again does the trick. My question is: do someone has an idea on how to fix that? I can give a shot, but I would appreciate some inputs ;) Ps: I use version 2 of FRR (because Vincent Jardin told that version 3 was not production ready at FRNog 29 ;)) Thanks! -- François
Francois - Sorry for the delay in responding. Last week was full of Turkey and I believe I ate myself into stupor a bit too much. I would start the change for this probably in bgp_route_map_process_update, which calls bgp_route_map_process_peer. donald On Wed, Nov 22, 2017 at 11:54 AM, François <francois.serman@corp.ovh.com> wrote:
Hello,
This issue has been discussed here : https://github.com/FRRouting/frr/issues/126
To sum up, when a route-map is modified (tried 2 things: adding a new entry and modifying prefix-list involved), no soft bgp clear is performed, so it looks like other peers never get new results (the "show advertised route" output is correct).
Looks like "no route-map ... " and "route-map ..." again does the trick.
My question is: do someone has an idea on how to fix that? I can give a shot, but I would appreciate some inputs ;)
Ps: I use version 2 of FRR (because Vincent Jardin told that version 3 was not production ready at FRNog 29 ;))
Thanks!
-- François
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Le 28/11/2017 à 16:20, Donald Sharp a écrit :
Ps: I use version 2 of FRR (because Vincent Jardin told that version 3 was not production ready at FRNog 29 ;))
FRR 3.0 is released now, you are welcomed to used it and to report issues like you just did. Thanks for your feedbacks,) Vincent
Hey guys, As I needed a quick fix to push to production, I tweaked the automation solution to do the soft-reconfiguration. But 10 monthes later, the question remains: was it fixed? On Tue, Nov 28, 2017 at 04:27:08PM +0100, Vincent JARDIN wrote:
FRR 3.0 is released now, you are welcomed to used it and to report issues like you just did.
I see that there has been 2 marjor versions since then, that amazing! I might give a try to the latests version, eventhough we currently use FRR as "simple" RR. -- François
François - I am not aware of this being fixed. It just has not trickled up to a developers plate yet from what I can tell. Lot's of new goodies in 4.0 and 5.0 you should check them out and see if any of the new featrues are needed. donald On Thu, Aug 2, 2018 at 6:31 AM, François <francois.serman@corp.ovh.com> wrote:
Hey guys,
As I needed a quick fix to push to production, I tweaked the automation solution to do the soft-reconfiguration.
But 10 monthes later, the question remains: was it fixed?
On Tue, Nov 28, 2017 at 04:27:08PM +0100, Vincent JARDIN wrote:
FRR 3.0 is released now, you are welcomed to used it and to report issues like you just did.
I see that there has been 2 marjor versions since then, that amazing! I might give a try to the latests version, eventhough we currently use FRR as "simple" RR.
-- François
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
On Thu, Aug 02, 2018 at 07:28:51AM -0400, Donald Sharp wrote:
François -
I am not aware of this being fixed. It just has not trickled up to a developers plate yet from what I can tell. Lot's of new goodies in 4.0 and 5.0 you should check them out and see if any of the new featrues are needed.
Thanks for your answer Donald. I don't think we *need* those features, but I was rather thinking about bugfixes, improvements, but most importantly, keeping up to date. I don't know how the "support" would work; for instance if a vuln was found, how deep [in older versions] would it be corrected? That's the main reason. Regarding the "bug", I'll try to setup a minimal environment to check that. Thanks :) François
There has been a non-trivial number of bug-fixes and improvements of FRR in the intervening year. https://github.com/FRRouting/frr/blob/master/doc/developer/workflow.rst Look at paragraph starting at line 102 for our policy. We are approaching a point where 3.0 is no longer going to be supported in general( not that there has been a bunch of support for it yet either ). donald On Thu, Aug 2, 2018 at 8:24 AM, François <francois.serman@corp.ovh.com> wrote:
On Thu, Aug 02, 2018 at 07:28:51AM -0400, Donald Sharp wrote:
François -
I am not aware of this being fixed. It just has not trickled up to a developers plate yet from what I can tell. Lot's of new goodies in 4.0 and 5.0 you should check them out and see if any of the new featrues are needed.
Thanks for your answer Donald. I don't think we *need* those features, but I was rather thinking about bugfixes, improvements, but most importantly, keeping up to date. I don't know how the "support" would work; for instance if a vuln was found, how deep [in older versions] would it be corrected? That's the main reason.
Regarding the "bug", I'll try to setup a minimal environment to check that.
Thanks :)
François
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
participants (3)
-
Donald Sharp -
François -
Vincent JARDIN