Open DrDeke opened 1 year ago
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.
This issue will be automatically closed in the specified period unless there is further activity.
@eqvinox Any ideas on this?
This issue will no longer be automatically closed.
Describe the bug
When a route learned through OSPF has a next-hop IP address that is reachable through a static route that overlaps a connected route, frr marks the route as 'inactive' and does not include it in the RIB.
(The reason I have static routes overlapping a connected route is that I want to advertise only a subset of the IP network reachable on the connected route to some BGP peers.)
To Reproduce
Expected behavior
I would expect to see a route to
10.1.8.1/32 via 1.2.3.203
in the output ofshow ip route
and added to the host's routing table (RIB). Instead, the route to 10.1.8.1/32 does not appear in the host's routing table, and appears asinactive
in the output ofshow ip route
orshow ip route ospf
as follows:O 10.1.8.1/32 [110/4] via 1.2.3.203, eth0.2 inactive, weight 1, 00:15:20
When bringing up the OSPF neighbor with
debug zebra rib detail
turned on on frr, you get the following output which seems relevant to the 10.1.8.1/32 route:Screenshots
Versions
Additional context
I am not sure whether this is a bug or whether I am misunderstanding how this should work. Any insight will be appreciated, and please let me know if any additional debugging output would be helpful.
Note: The IP network 1.2.3.0/24 is not the actual IPv4 network in the configuration; I have replaced the first three octets with '1.2.3' for privacy reasons in all parts of this report.