summaryrefslogtreecommitdiff
path: root/pimd/pim_assert.c
diff options
context:
space:
mode:
authorplsaranya <saranya_panjarathina@dell.com>2022-03-23 19:16:46 +0530
committerplsaranya <saranya_panjarathina@dell.com>2022-03-25 19:48:54 +0530
commitdb89f2a3ebd29b53fc06e2c6735b6ff0ff9dcf8a (patch)
treed4fe7daf99d202721abdde5f86995f5f06aa269b /pimd/pim_assert.c
parent52093e0f0e5753b753ae1b048f69b979ed3c75f6 (diff)
pimd: Assert fixes
Problem: PIM assert is not triggered even after receiving WRONGVIF notification because of Could_assert flag not set. CouldAssert(S,G,I) = SPTbit(S,G)==TRUE AND (RPF_interface(S) != I) AND (I in ( ( joins(*,G) (-) prunes(S,G,rpt) ) (+) ( pim_include(*,G) (-) pim_exclude(S,G) ) (-) lost_assert(*,G) (+) joins(S,G) (+) pim_include(S,G) ) ) Once SPTbit is set, Could_assert has to be reevaluated Signed-off-by: plsaranya <Saranya_Panjarathina@dell.com>
Diffstat (limited to 'pimd/pim_assert.c')
0 files changed, 0 insertions, 0 deletions