You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I have searched the open issues for this bug.
I have not included sensitive information in this report.
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: