April 30, 2020
8:40 a.m.
On Thu, Apr 30, 2020 at 8:37 AM David Farmer <farmer@umn.edu> wrote:
I think it was more than just an invalid next-hop. If it was simply an invalid next-hop that shouldn't have created a malformed BGP update. Unless the invalid next-hop caused BIRD to send out a malformed BGP update.
The problem left here successfully.... :)