Open
Description
Description
When a BGP neighbor in the same subnet has BFD enabled, if an update-source is specified then the BFD peer will always be setup as multihop. This breaks the BFD peering and thus the BGP neighbor. Happens for both v4 and v6 neighbors.
This is working correctly with 10.1.0 but fails with 10.3.0.
Version
10.3.0
How to reproduce
Configure a BGP neighbor with BFD enabled (dynamic or static) and configure an update-source for a neighbor in the same subnet.
Expected behavior
BFD peer should not be multihop for a subnet adjacent neighbor.
Actual behavior
BFD peer is always configured a multihop. With a statically configured peer a conflicting multihop peer is created and with dynamic an incorrect multihop peer is created.
Additional context
No response
Checklist
- I have searched the open issues for this bug.
- I have not included sensitive information in this report.