19.03.2024 09:22, Ilham Maulana пишет:

Hello,

In my case, I change routing protocol from OSPF to RIP.

While waiting for the fix.

ECMP is broken too using OSPF Bird 2.15.

Thank you! As I remember now there was discussion in this list about ospfv3 and ecmp off as workaround. I'll try in night time :-)

Thanks.

...

On 19/03/2024 11:54:58, Dmitry Melekhov <dm@belkam.com> wrote:

Hello!

Just upgraded and got:

Mar 19 08:07:46 hohr-vpn-1 bird[1523831]: Started Mar 19 08:07:54 hohr-vpn-1 bird[1523831]: MyOSPF: Unexpected case in next hop calculation Mar 19 08:07:54 hohr-vpn-1 bird[1523831]: MyOSPF: Cannot find next hop for LSA (Type: 2002, Id: 192.168.222.221, Rt: 192.168.22.178) Mar 19 08:07:54 hohr-vpn-1 bird[1523831]: MyOSPF: Unexpected case in next hop calculation

etc.

on all hosts I upgraded.

All of them is alma 9.

Downgrade to 2.14 solved problem.

Is there fix for this or workaround?

Thank you!

82f83837-9af9-46ad-ab8b-2a8debdb590f

19.03.2024 13:15, Soha Jin пишет:

Hi All,

I have found the problem (inherit next hop from a pointopoint router) and already drafted a patch. I will post the patch to the list once I have tested it.

Problem is caused by some change , may be it is possible just revert it? Thank you!

19.03.2024 12:57, Maria Matejka via Bird-users пишет:

Hello,

please tell us more about your setup, config and topology. With this, we can't even start looking for the possible problem.

Here is config from one of servers, which is affected. Really any host with bird2.15 is affected, but we run it only on alma 9. router id 192.168.110.2;         route 192.168.204.1/32 via "wg0";         route X/28 via Z;         route Y/28 via Z;         route 192.168.200.34/32  via Z;         route 192.168.201.66/32  via "gre2";         route 192.168.200.38/32  via "gre1"; protocol ospf MyOSPF {         area 0 {                 networks {                          192.168.110.0/24;                          192.168.201.64/30;                          192.168.200.36/30;                         };                 interface "gre1" {                 #                         cost 2;                         type  ptp;                         password "111" {                               id 10;                         algorithm keyed md5;                         };                         authentication cryptographic;                 };                 interface "gre2" {                 #                         cost 1111;                         type  ptp;                         password "111" {                               id 10;                         algorithm keyed md5;                         };                         authentication cryptographic; #                       bfd yes;                 };                 interface "br0" {                 #LAN                         cost 1;                         password "111" {                               id 10;                         algorithm keyed md5;                         };                         authentication cryptographic;                         #check link yes;                 };         }; } As you can see it's just to gre uplinks and br0 to LAN. We also have area 1 in our ospf, but I don't think it is related. From log: Mar 19 08:07:41 ast-zab bird[1164676]: Started Mar 19 08:07:49 ast-zab bird[1164676]: MyOSPF: Unexpected case in next hop calculation Mar 19 08:07:49 ast-zab bird[1164676]: MyOSPF: Cannot find next hop for LSA (Type: 2002, Id: 192.168.22.253, Rt: 192.168.22.253) Mar 19 08:07:49 ast-zab bird[1164676]: MyOSPF: Unexpected case in next hop calculation Mar 19 08:07:49 ast-zab bird[1164676]: MyOSPF: Cannot find next hop for LSA (Type: 2001, Id: 10.1.1.10, Rt: 10.1.1.10) Mar 19 08:07:49 ast-zab bird[1164676]: MyOSPF: Unexpected case in next hop calculation Please, tell me what other information you need. Thank you!

Thanks, Maria

On 2024-03-19 05:50, Dmitry Melekhov wrote:

...

Hello!

Just upgraded and got:

Mar 19 08:07:46 hohr-vpn-1 bird[1523831]: Started Mar 19 08:07:54 hohr-vpn-1 bird[1523831]: MyOSPF: Unexpected case in next hop calculation Mar 19 08:07:54 hohr-vpn-1 bird[1523831]: MyOSPF: Cannot find next hop for LSA (Type: 2002, Id: 192.168.222.221, Rt: 192.168.22.178) Mar 19 08:07:54 hohr-vpn-1 bird[1523831]: MyOSPF: Unexpected case in next hop calculation

etc.

on all hosts I upgraded.

All of them is alma 9.

Downgrade to 2.14 solved problem.

Is there fix for this or workaround?

Thank you!

-- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

19.03.2024 18:07, Ondrej Zajicek пишет:

Both issues are restricted to physical PtP links (including L3 tunnels like GRE). The first issue is limited to ECMP IPv6 and can be workarounded by disabling ECMP, the second one has wider impact.

Problem here is that 2.15 is already in epel. Many systems will be broken soon if not already...

24.03.2024 21:33, Robert Scheck пишет:

On Wed, 20 Mar 2024, Dmitry Melekhov wrote:

...

Problem here is that 2.15 is already in epel.

Many systems will be broken soon if not already... Given BIRD 2.15.1 has been released, EPEL users could run:

dnf update --enablerepo=epel-testing "bird*"

Just installed rpm from repo manually on two hosts. It works :-)

Unfortunately, only very less people add positive/negative karma to Fedora/EPEL updates using Bodhi (https://bodhi.fedoraproject.org/).

Frankly, I didn't ever heard about this before...