Hi, sorry for digging up this thread. I just wanted to let you know, that (thanks to your help) we could talk to the Cisco TAC and explain this issue and have workarounds that somehow fixed this behavior. They acknowledged that this is a bug (now listed as CSCvm39227) since it's a violation of RFC 2545. They are working on fixing it and might even provide patches (SMU) for some platforms. Cheers, Sebastian On 10.08.18 16:17, Ondrej Zajicek wrote:
On Fri, Aug 10, 2018 at 02:43:18PM +0200, Sebastian Neuner wrote:
And you can use:
bgp_next_hop = bgp_next_hop;
This actually sets the right next-hop, but for some reason it sets the route to the wrong interface (i.e. to the Cisco).
That is because import filter is processed after gateway is already computed from the original value of bgp_next_hop.