summaryrefslogtreecommitdiff
path: root/doc/manpages/conf.py
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2019-04-02 21:15:21 -0400
committerDonald Sharp <sharpd@cumulusnetworks.com>2019-04-05 11:12:59 -0400
commit5bd51314352b25420ef1c8df7265b95cdad88e37 (patch)
treeedb898a02a031f3cda53385358b90721df7ee489 /doc/manpages/conf.py
parent2ccc414b19c9c2115fae5b2c36c69b480b7cfcd9 (diff)
pimd: Determining if we are the RP should happen always
When creating new RP information from a `ip pim rp A.B.C.D/M A.B.C.D` we should determine if we are the RP even if we can or cannot determine if we have a path to the RP via RPF. This is because we should determine if we are the RP based upon a connected ip address match not whether or not we have a path to the RPF. We would normally think this is not important but RPF is inherently asynchronous and we can have a state where we have registered for nht but have not received the actual path back yet from zebra. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'doc/manpages/conf.py')
0 files changed, 0 insertions, 0 deletions