> On 14. Jan 2021, at 03:51, Ondrej Zajicek wrote:
>
> On Fri, Apr 10, 2020 at 11:13:40AM +0200, Sebastian Hahn wrote:
>>> Thanks for the bugreport. You are right, BFD sessions are dispatched just
>>> based
>>> on source address regardless of interface, so it is confused by conflicting
>>> li
On Fri, Apr 10, 2020 at 11:13:40AM +0200, Sebastian Hahn wrote:
> > Thanks for the bugreport. You are right, BFD sessions are dispatched just
> > based
> > on source address regardless of interface, so it is confused by conflicting
> > link-local addresses. We will fix that, i would expect the sam
Hi there,
> On 7. Mar 2018, at 15:42, Ondrej Zajicek wrote:
> On Sun, Mar 04, 2018 at 07:50:13PM +0100, Julian Brost wrote:
>> I just tried to enable BFD for some OSPF and BGP connections and ran
>> into an issue which BFD sessions flapping up and down and Bird logging
>> many messages like these
On Sun, Mar 04, 2018 at 07:50:13PM +0100, Julian Brost wrote:
> Hi,
>
> I just tried to enable BFD for some OSPF and BGP connections and ran
> into an issue which BFD sessions flapping up and down and Bird logging
> many messages like these:
>
> bfd1: Bad packet from fe80::2 - unknown session i
On 04.03.2018 19:50, Julian Brost wrote:
> Hi,
>
> I just tried to enable BFD for some OSPF and BGP connections and ran
> into an issue which BFD sessions flapping up and down and Bird logging
> many messages like these:
>
> bfd1: Bad packet from fe80::2 - unknown session id (130079069)
> bfd
