diff options
author | Donald Sharp <sharpd@cumulusnetworks.com> | 2016-10-31 00:34:26 +0100 |
---|---|---|
committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2016-12-22 02:26:12 +0100 |
commit | 7f748d958601a2270b321603a257e87aee5f34df (patch) | |
tree | 040a97d5ffd0933d4e00a8a43fd5b87c05662a19 /pimd/pim_rpf.c | |
parent | pimd: Ignore (S,G) Prunes with no current state (diff) | |
download | frr-7f748d958601a2270b321603a257e87aee5f34df.tar.xz frr-7f748d958601a2270b321603a257e87aee5f34df.zip |
pimd: When nexthop_lookup fails allow a retry.
We are seeing situations where nexthop lookups are failing
unexpectedly. Don't consider the lookup to have succeeded
in this case to allow the next lookup to work?
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'pimd/pim_rpf.c')
-rw-r--r-- | pimd/pim_rpf.c | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/pimd/pim_rpf.c b/pimd/pim_rpf.c index 2b1652962..1724185e9 100644 --- a/pimd/pim_rpf.c +++ b/pimd/pim_rpf.c @@ -172,11 +172,7 @@ int pim_nexthop_lookup(struct pim_nexthop *nexthop, struct in_addr addr, int nei return 0; } else - { - nexthop->last_lookup = addr; - nexthop->last_lookup_time = pim_time_monotonic_usec(); - return -1; - } + return -1; } static int nexthop_mismatch(const struct pim_nexthop *nh1, |