Non-advertised Interface Down/Up Impacts OSPF Advertised Routes

[autumn0632]

Description

We have observed an issue where a non-advertised interface (one that is not part of OSPF) experiences a down/up event, which seems to affect the routing order or priority of interfaces that are advertised in OSPF. This behavior is unexpected, as the non-advertised interface should not influence the OSPF routing table.

Version

7.5.1

How to reproduce

无

Expected behavior

无

Actual behavior

无

Additional context

The first image shows OSPF-learned routes for the network 188.106.0.224/27. These routes were learned through multiple paths: Via 172.16.2.138 on eth2. Via 172.16.2.142 on eth3. Additionally, there is a directly connected route for 188.106.0.224/27 through eth0. The router initially selects the directly connected route (marked with C>), indicating it has the highest priority.

when eth0 down and up： （blue）

Checklist

• [X] I have searched the open issues for this bug.
• [X] I have not included sensitive information in this report.

[donaldsharp]

Please try with latest code. It is unlikely that anyone will ever fix this in the 7.5.X releases

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

[frrbot[bot]]

This issue will be automatically closed in the specified period unless there is further activity.