Confirming that this bug is still present on 1.4-rolling-20210505111.

@c-po Sorry for the late notice on this -- One of the 2020 releases sort-of fixed the issue in my environment. I'm not seeing crashes on the OSPF daemon but I have seen it on occasion with OSPF6 like @maznu mentioned.

Confirming that I also report this on 1.3-rolling-202001240217. Just upgraded this morning and I see the same unknown layer 3 protocol error as reported.

@runar If I could offer an alternative, why not require set interfaces bonding bond0 hash-policy to always be specified? The hash policy is not something optional like a tunnel key for GRE, so I feel that this option should be required.

@syncer Which version of frrouting is VyOS currently built against?

@syncer Sorry for the delay.. life got a bit hectic the last few months.

Update for everyone - I built out an exact replica of my lab on a single Hyper-V host with a single internal vSwitch connecting all interfaces (similar, in principle at least).

@kroy - I tried doing an upgrade to match all routers to the same version and it ended quite badly.. all four had their OSPF instance die.

I managed to get some reproducible captures today. Life took me for a bit of a ride so I didn't have free time until just now.

Sure I can get you tcpdumps. Do you want to see the ospf packets specifically?

I did a bit of digging on my R1 after reboot and I am seeing the following logs in Zebra, so it looks like it's completely unrelated to the neighbor deletion: