On 29 Oct 2015, at 9:35, Paul Jakma wrote:
On Wed, 28 Oct 2015, J Yu wrote:
issues. The other cause is the issue we are facing today where the
route can NOT be deleted in rib now that it has a new next_hop, but
the new next_hop is unreachable such that it needed to be deleted
from the forwarding database. One can also argue this is a modify
case of the route, which is from rib perspective only.
So, should we even bother trying to match the old nexthop? Just tell
zebra to delete the prefix. Below seems to pass Martin's test.
Havn't tested IPv6 (Martin, fancy extending your tool?).
Done.
Same issue in original code and your suggested patch fixes the problem
If you want to try yourself, the feel free to checkout my test tool -
added the test cases for IPv6 (and the IPv4 ECMP)
case.
https://git-us.netdef.org/projects/NETDEF/repos/bgptool/browse?at=refs%2Fheads%2Ftest%2Finvalid-valid-invalid
- Martin Winter
[email protected]
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
