summaryrefslogtreecommitdiff
path: root/lib/imsg-buffer.c
diff options
context:
space:
mode:
authorSarita Patra <saritap@vmware.com>2023-04-09 22:30:44 -0700
committerSarita Patra <saritap@vmware.com>2023-04-09 22:30:44 -0700
commit8b462d557905200d98c7a8965b3d223637c3c5dd (patch)
treec0d35bde6f8f7e51d9c408da70351353c4bc594e /lib/imsg-buffer.c
parent48055cc48e54a9804ab8aded3a341e3b593a7111 (diff)
pimd: Process no-forward BSM packet
Topology Used: ============= Cisco---FRR4----FRR2 Initially PIM nbr is down between FRR4----FRR2 from FRR2 side Cisco is sending BSR packet to FRR4. Problem Statement: ================= No shutdown the PIM neighbor on FRR2 towards FRR4. FRR2, receives BSR packet immediately as the new neighbor comes up. This BSR packet is having no-forward bit set. FRR2 is not able to process the BSR packet, and drop the BSR packet. Root Cause: ========== When PIMD comes up, we start BSM timer for 60 seconds. Here, the value accept_nofwd_bsm is setting to false. FRR2, when receives no-forward BSR packet, it is getting accept_nofwd_bsm value as false. So, it drops, the no-forward BSM packet. Fix: === Set accept_nofwd_bsm as false after first BSM packet received. Signed-off-by: Sarita Patra <saritap@vmware.com>
Diffstat (limited to 'lib/imsg-buffer.c')
0 files changed, 0 insertions, 0 deletions