I've found a workaround for this issue.
Seems that crucial is line
"2018-08-24 14:07:38 bfd1: Session to 172.30.2.1 added"
I'm assuming what's happening here is that Bird selects another interface
as source which doesn't have connectivity and never goes back to proper
interface after it comes bac
Hi,
I have multihop BGP peering with BFD setup on it. One of the peers is a
switch that runs Linux. I've run into situation where after link flap on
interface that switch connects to BFD protocol after successfully detecting
that flap BFD session cannot reestablich because switch side stops sendin
